[openbeos] Re: driver interface question
- From: Jérôme Duval <korli@xxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 24 Jun 2003 13:55:15 +0200 (CEST)
En réponse à Bruno van Dooren <bruno_van_dooren@xxxxxxxxxxx>:
> for some time now i have been wondering why the declaration of the
> driver
> interface posix calls (open, close, ioctl, ...) are split over 3 header
>
> files? (i don't know by heart which 3, and i don't have a BeOS system
> nearby
> at this moment)
are you talking about this one header file :
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/open-beos/current/headers/os/drivers/Drivers.h?rev=1.3
?
>
> wouldn't it make much more sense to have all those calls combined in 1
>
> header file?
> not to mention the fact that the BeBook does not contain information on
> how
> to actually call and use device drivers.
>
> i learned it by going through the examples a year ago, but still...
>
> of course i don't know very much about posix, so my question could be a
>
> little silly, but does anyone know the 'why' of this?
>
sorry but i don't understand. Are you talking about the OpenBeOS kernel driver
interface ?
Jérôme
- References:
- [openbeos] driver interface question
- From: Bruno van Dooren
Other related posts:
- » [openbeos] driver interface question
- » [openbeos] Re: driver interface question
- » [openbeos] Re: driver interface question
- » [openbeos] Re: driver interface question
- » [openbeos] Re: driver interface question
- [openbeos] driver interface question
- From: Bruno van Dooren