In hannet.ml.linux.rutgers.linux-kernel, you wrote:
>
>> What Al is saying, and what makes perfect sense is that you generate a
>> separate fd for each "pipe". It's even more obvious in the case of USB,
>> because, by golly, the things are actually _called_ "pipes" in the USB
>> documentation, which should have made people make the immediate
>> association. Instead of doing
>
>Graphics cards are the same way. Especially high end ones. They have pipes
>as well. For low end cards you can think of them as single pipeline cards
>with one pipe.
>
>> See?
>>
>> Don't get boxed in by thinking that you only have one fd. Even if you have
>> only one _device_node_, you can have multiple fd's. In fact, you can, with
>> the Linux VFS layer, fairly easily do things like
>>
>> mknod /dev/fd0 c X Y
>>
>> and then use
>>
>> fd = open("/dev/fd0/colourspace", O_RDWR);
>
>Yipes!! I have to say UNIX has a tendency to teach you ioctl is the only
>way. I have never thought outside of the box nor see anyone else in this
>manner. This is absolutely brillant!!! I can see alot of possibilties with
>this.
Actually that sounds pretty much like multiplexed character special
devices that were available in earlier Unix versions and are still
available under AIX. And they are used for these kind of things, the
device driver gets the rest of the unparsed path name and reacts
accordingly. See:
http://www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/libs/ktechrf1/ddmpx.htm
-- Jens-Uwe Mager <pgp-mailto:62CFDB25> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 15 2001 - 21:00:44 EST