Tejun Heo wrote:
sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
missing udma timing value for UDMA100. According to sis5513, this
should be 0x8000. This caused UDMA100 device to fail on pata_sis till
it downgrades to UDMA66 while it works fine on sis5513 at UDMA100.
Reporte
On 09/21/2007 03:29 AM, Tejun Heo wrote:
> sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
> missing udma timing value for UDMA100. According to sis5513, this
> should be 0x8000. This caused UDMA100 device to fail on pata_sis till
> it downgrades to UDMA66 while it works fine o
Alan Cox wrote:
> On Fri, 21 Sep 2007 16:29:05 +0900
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
>> missing udma timing value for UDMA100. According to sis5513, this
>> should be 0x8000. This caused UDMA100 device to fail on pata
On Fri, 21 Sep 2007 16:29:05 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
> missing udma timing value for UDMA100. According to sis5513, this
> should be 0x8000. This caused UDMA100 device to fail on pata_sis till
> it downgrades
sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
missing udma timing value for UDMA100. According to sis5513, this
should be 0x8000. This caused UDMA100 device to fail on pata_sis till
it downgrades to UDMA66 while it works fine on sis5513 at UDMA100.
Reported by Adam Blech.
S