Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: IDE/ATAPI in 2.5 | From | (Eric W. Biederman) | Date | 15 Jul 2002 04:24:54 -0600 |
| |
"H. Peter Anvin" <hpa@zytor.com> writes:
> Andre Hedrick wrote: > > Nice, so you still have to strip and export to the transport layer. > > Please expand on what you are going to talk to packetized and the associated > > transport protocol restricted to the scope of storage. > > Next count all the different personalitys associated with the discrete > > transport layer. > > If you are referring to Jens' pktcdvd interface out of block, it is no > > more than a bypass of dealing with scsi. It would allow direct access to > > the physical transport without portions of OS mucking up things as it does > > now. > > > > I'm talking specifically about ATAPI devices here. As we have already covered, > not all ATA devices are ATAPI, but unless I'm completely off the wall, ATAPI is > SCSI over IDE, and should be able to be driven as such. The lack of access to > that interface using the established interface mechanisms just bites.
ATAPI is SCSI like C is C++. There are strong similarities but they are regulated by different groups, and have slightly different semantics. Last I checked cdrecord already compensates for those differences but they are there.
Eric
- 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/
| ![\](/images/icornerr.gif) |