> demonstrated by (a) Alan's patch did not change DMA lbam/lbah > programming and (b) Daniel's report of the message "ata2.00: 66 bytes (a) did. Well the original did, dunno about your version. > I am not drawing any conclusions yet, but I'm thinking that blimit=8k > may be a better choice for SATA ATAPI. Only if your transfer is actually 8K or more. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Jeff Garzik <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- References:
- "Fix ATAPI transfer lengths" causes CD writing regression
- From: Daniel Drake <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Alan Cox <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Daniel Drake <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Alan Cox <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Daniel Drake <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Alan Cox <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Jens Axboe <[email protected]>
- Re: "Fix ATAPI transfer lengths" causes CD writing regression
- From: Jeff Garzik <[email protected]>
- "Fix ATAPI transfer lengths" causes CD writing regression
- Prev by Date: Re: "Fix ATAPI transfer lengths" causes CD writing regression
- Next by Date: Re: 2.4.24-rc1-git: crash on shutdown/unmount?
- Previous by thread: Re: "Fix ATAPI transfer lengths" causes CD writing regression
- Next by thread: Re: "Fix ATAPI transfer lengths" causes CD writing regression
- Index(es):
 |