Re: [PATCH] ata_piix: fix pio/mwdma programming (for testing, don't apply)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alan wrote:
>>> Yep and if the BIOS programmed the slave into DMA that might not be ideal.
>> How so?  The bit will be programmed by set_dmamode() right after
>> set_piomode() is complete.
> 
> IFF we also put the device into a DMA mode. A blacklisted device would be
> wrong.

Hmmm... I might be misunderstanding, but if libata is going to put the
device into PIO mode, why does it matter what BIOS configured slave to?
 The slave is going to be put into PIO mode libata selected so the
control bits should match, no?

[--snip--]
>>>> * MWDMA mode programming cleared udma_mask even when the controller
>>>>   doesn't support UDMA.  This doesn't matter for your case.
>>> Or on the actual hardware.
>> I was trying to make it more consistent with pio counterpart.  We can
>> remove if() from set_piomode too.  Let's just keep things in sync
>> between stuff including ide piix driver.
> 
> The one you must not touch is the UDMA register rather than added UDMA
> bits in older registers.

OIC.  I was confused there.

Thanks.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux