Thats scsi_generic which thankfully puts most of the logic in user space.
> > Those devices aren't SCSI controllers, and they don't want to appear as one.
>
> Don't think "SCSI" as in SCSI controllers. Think SCSI as in "fairly
> generic packet protocol that somehow infiltrated most things".
The scsi controller is akin to a network driver. The stuff that matters is
stuff like the scsi disk, scsi cd and scsi tape drivers. Scsi disk and CD
need to do a lot of error recovery (especially CD-ROM). Disk too has to
because older scsi devices don't have the same kind of "the host is clueless
crap I'll have to try error recovery myself before reporting" mentality.
It would be nice if a lot of the CD error/recovery logic could be in the
cdrom libraries because the logic (close the door, lock the door, try
half speed, ..) is the same in scsi and ide.
> It's called "struct block_device" and "struct genhd". The pointers will
> have as many bits as pointers have on the architecture. Low-level drivers
> will not even see anything else eventually, there will be no "numbers".
For those of us who want to run a standards based operating system can
you do the 32bit dev_t. Otherwise some slightly fundamental things don't
work. You know boring stuff like ls, find, df, and other standard unix
commands. Those export a dev_t cookie.
If you don't want to be able to run stuff like ls, just let me know and
I'll start another kernel tree 8)
Alan
-
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/