* Add IDE_HFLAG_ABUSE_SET_DMA_MODE host flag and use it to decide
what to do with transfer modes < XFER_PIO_0 in ide_set_xfer_rate().
* Set IDE_HFLAG_ABUSE_SET_DMA_MODE in host drivers that need it
(aec62xx, amd74xx, cs5520, cs5535, hpt34x, hpt366, pdc202xx_old,
serverworks, tc86c001 and vi
Bartlomiej Zolnierkiewicz wrote:
* Add IDE_HFLAG_ABUSE_SET_DMA_MODE host flag and use it to decide
what to do with transfer modes < XFER_PIO_0 in ide_set_xfer_rate().
* Set IDE_HFLAG_ABUSE_SET_DMA_MODE in host drivers that need it
(aec62xx, amd74xx, cs5520, cs5535, hpt34x, hpt366, pdc202x
Hello, I wrote:
It's tome that I go and make a patch which deals with 0x00 (default
s/tome/time/
PIO mode)...
But I'm unsure how this value could reach us form userspace because of the
argument check present everywhere that filters out 0 value form being passed
-- look at set_xf
Hi,
On Thursday 15 November 2007, Sergei Shtylyov wrote:
> Hello, I wrote:
>
> >It's tome that I go and make a patch which deals with 0x00 (default
>
> s/tome/time/
>
> > PIO mode)...
>
> But I'm unsure how this value could reach us form userspace because of
> the
> argument ch
