> Since my experience with the Solo driver (it's still not quite done)
> bounty,
> I will put up a page where folks offering "driver bounties" can make
> their offers
> known. Such sites exist for software in general, but I will make one
> just for
> FreeBSD drivers.
This should probably be integ
On Sat, 5 Aug 2000, Nick Sayer wrote:
> Alan Clegg wrote:
> >
> > Out of the ether, Andrzej Bialecki spewed forth the following bitstream:
> >
> > > On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly
> > > willing to pay twice as much ($200) for working sound in most of l
hi,
In an ealier mail some one has sent a list of suggested reading for
device drivers(none of them are specific to FreeBSD).
i found unix device drivers by george pajari very useful. the methodology
i followed is to read a chapter from that book and read the FreeBSD
sources for simillar device
-piet
Re: Drivers collection (was:Arlan 655 driver for FreeBSD)
To: Boris Popov <[EMAIL PROTECTED]>
Subject: Re: Drivers collection (was:Arlan 655 driver for
FreeBSD)
From: Warner Losh <[E
Mike Smith wrote:
>
> > Hello.
> >
> > If we have a character device driver with and more than one
> > open handles for it, can read() and ioctl() choose which one
> > is used?
>
> No. This is not how the BSD driver model works; you should create
> multiple instances of the driver if you need m
> Hello.
>
> If we have a character device driver with and more than one
> open handles for it, can read() and ioctl() choose which one
> is used?
No. This is not how the BSD driver model works; you should create
multiple instances of the driver if you need multiple discrete opens.
--
\\ Giv
6 matches
Mail list logo
