"seekable" device

[Fernando RUIZ CASAS]

You don't need a seek for the device.
When the device read/write the parameters gives you a offset to do the real
devive seek.

In my /dev/flash device I could make the seek with this.

Fernando RUIZ CASAS
home: correo at fernando-ruiz.com
work: fernando.ruiz at ctv.es




> -----Mensaje original-----
> De: Pattara Kiatisevi [mailto:pkiatisevi at student.ei.uni-stuttgart.de]
> Enviado el: jueves, 21 de marzo de 2002 17:18
> Para: 'RTEMS Users'
> CC: oggonachip at yahoogroups.com
> Asunto: "seekable" device
>
>
> Hi all,
>
> I have a hopefully simple question about this "fseek" function. What will
> happen if an application calls "fseek" to a device? I mean, how can I
> adjust my device driver (I wrote a /dev/soundinput to simulate a song
> file) to support this seek function? Now I have only
> soundinput_initialize(), open(), close(), read(), write() and ioctl().
>
> Thank you very much,
> Pattara
> --
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
> ----------------------------------------------------------------------
> Ott Pattara Kiatisevi 				   T L W G
> M.Sc. INFOTECH Student, Stuttgart, Germany	http://linux.thai.net/
> ----------------------------------------------------------------------
>
>