> > Ick. Polling == bad. Interrupts == good. This isn't a single-
> > tasking OS ala Win9x. This goes double for SCSI drivers, which are
> > inherently async and overlapped.
>
> I never said polling was good. Nick just asked about polling, and I
> commented on how it could be done. I ha
Randell Jesup wrote...
> This discussion should probably move to the freebsd-scsi list...
>
> "Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
> >Nick Hibma wrote...
> >> Especially some help on the topic of polling would be appreciated.
> >> Otherwise I'll have to resort to figuring out how
This discussion should probably move to the freebsd-scsi list...
"Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
>Nick Hibma wrote...
>> Especially some help on the topic of polling would be appreciated.
>> Otherwise I'll have to resort to figuring out how to do things in
>> interrupt cont
[ reply moved the bottom... ]
Nick Hibma wrote...
> > Warner Losh wrote...
> > > In message <[EMAIL PROTECTED]> Wilko Bulte writes:
> > > : How difficult would CAMifying a driver be?
> > >
> > > Speaking of which, has a "How to CAMify a driver" doc been written?
> >
> > Nope. You've CAM
There's a CAM ANSI spec at http://www.t10.org. But the lack of
implementatio for FreeBSD docs is probably the biggest missing piece for
FreeBSD's implementation.
On Fri, 8 Oct 1999, Nick Hibma wrote:
>
> While on the topic: What documentation is there for CAM? I've found the
> following, but
While on the topic: What documentation is there for CAM? I've found the
following, but would like to know whether there is more
- CAM specification (at Digital?)
- justin's docu on freefall.
Especially some help on the topic of polling would be appreciated.
Otherwise I'll have to resort to fig
6 matches
Mail list logo
