Jan Engelhardt writes:
> >> The driver (yet unwritten) does approximately the same as the qotd sample
> >> driver from the "Device Driver Tutorial" book - giving data stored in
> >> kernel memory to userspace and nothing more.
> >
> > If it's a simple driver not related to terminal/serial subsystem
Right, but
I answered your initial question. This one:
what is the advantage of STREAMS (besides the modularity and
stackability)? The BSDs and Linux seem to be happy enough
has more to do with the history of unix, System V vs BSD, etc. My
colleagues with air conditioners in their homes m
>> The driver (yet unwritten) does approximately the same as the qotd sample
>> driver from the "Device Driver Tutorial" book - giving data stored in
>> kernel memory to userspace and nothing more.
>
> If it's a simple driver not related to terminal/serial subsystem, you most
> likely want a charac
The driver (yet unwritten) does approximately the same as the qotd sample
driver from the "Device Driver Tutorial" book - giving data stored in
kernel memory to userspace and nothing more.
If it's a simple driver not related to terminal/serial subsystem, you
most likely want a character driv
Ok, sorry for my english, you are misunderstand me.
My question is very simple:
Whether is at Solaris what or a free-of-charge opportunity to receive updating?
(may be latter then Sun Service Plan-owners)
This message posted from opensolaris.org
___
o
Hello,
while writing a pseudo device driver, eventually the question came up on
myself whether it would be meaningful or necessary to make it a streams
driver or just simply a character-based one.
The driver (yet unwritten) does approximately the same as the qotd sample
driver from the "Device
