Re: VIA Serial ATA chipset

From: Daniela Engert
Date: Wed Aug 13 2003 - 03:00:07 EST


On Tue, 12 Aug 2003 23:49:23 -0700, Misha Nasledov wrote:

>Thanks a lot, this patch works for me. I have the following in my dmesg:
>
>VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0
>PCI: Found IRQ 3 for device 0000:00:0f.0
>IRQ routing conflict for 0000:00:0f.0, have irq 11, want irq 3
>PCI: Sharing IRQ 3 with 0000:00:0f.1
>IRQ routing conflict for 0000:00:10.0, have irq 11, want irq 3
>IRQ routing conflict for 0000:00:10.1, have irq 11, want irq 3
>VIA8237SATA: chipset revision 128
>VIA8237SATA: 100% native mode on irq 11
> ide4: BM-DMA at 0x8400-0x8407, BIOS settings: hdi:pio, hdj:pio
> ide5: BM-DMA at 0x8408-0x840f, BIOS settings: hdk:pio, hdl:pio
>
>The IRQ routing conflict lines have always existed, and there are more
>similar lines in other parts of the dmesg. I'm not sure if they are
>pertinent at all. Unfortunately, the drive does not seem to perform as
>well as a SATA drive should; my UDMA/133 drive currently outperforms
>this. However, it seems to significantly faster than the UDMA/66 drive
>I run Linux on, so I am glad that it works as fast it does because now
>I can perhaps use this as my new system drive.

Well, the patch was meant to be a quick shot from the hips only, just
to get your system going and to check if my assumptions about the
structure of the VIA SATA host controller implementation wer correct.
It looks like they are, this controller seems to follow the T13 ATA
host controller model.

>Are there any plans on the horizon for a more complete driver for this
>chipset?

Jeff Garzik is working on a SATA driver. My conclusions from the
results of the feasability test above are that adding the VIA SATA
controller to the already existing libata source should boil down to
pretty simple programming excercise.

Ciao,
Dani


>On Tue, Aug 12, 2003 at 01:13:59PM +0200, Daniela Engert wrote:
>> Looking at the sources of /drivers/ide/pci/generic.* shows that the
>> "generic" driver is much less generic than its name might suggest. The
>> following patch should help.
>>
>> Ciao,
>> Dani
>>
>> --- generic.c Tue Aug 12 07:58:08 2003
>> +++ generic.c Tue Aug 12 12:59:02 2003
>> @@ -140,6 +140,7 @@
>> { PCI_VENDOR_ID_HINT, PCI_DEVICE_ID_HINT_VXPROII_IDE,
>> PCI_ANY_ID, PCI_ANY_ID, 0, 0, 6},
>> { PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C561,
>> PCI_ANY_ID, PCI_ANY_ID, 0, 0, 7},
>> { PCI_VENDOR_ID_OPTI, PCI_DEVICE_ID_OPTI_82C558,
>> PCI_ANY_ID, PCI_ANY_ID, 0, 0, 8},
>> + { PCI_VENDOR_ID_VIA,
>> PCI_DEVICE_ID_VIA_8237_SATA, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
>> 9},
>> { 0, },
>> };
>>
>> --- generic.h Mon Jul 14 03:30:48 2003
>> +++ generic.h Tue Aug 12 13:02:08 2003
>> @@ -127,7 +127,20 @@
>> .enablebits = {{0x00,0x00,0x00},
>> {0x00,0x00,0x00}},
>> .bootable = ON_BOARD,
>> .extra = 0,
>> - },{
>> + },{ /* 9 */
>> + .vendor = PCI_VENDOR_ID_VIA,
>> + .device = PCI_DEVICE_ID_VIA_8237_SATA,
>> + .name = "VIA8237SATA",
>> + .init_chipset = init_chipset_generic,
>> + .init_iops = NULL,
>> + .init_hwif = init_hwif_generic,
>> + .init_dma = init_dma_generic,
>> + .channels = 2,
>> + .autodma = AUTODMA,
>> + .enablebits = {{0x00,0x00,0x00},
>> {0x00,0x00,0x00}},
>> + .bootable = OFF_BOARD,
>> + .extra = 0,
>> + },{
>> .vendor = 0,
>> .device = 0,
>> .channels = 0,
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Daniela Engert, systems engineer at MEDAV GmbH
>> Gr?fenberger Str. 32-34, 91080 Uttenreuth, Germany
>> Phone ++49-9131-583-348, Fax ++49-9131-583-11
>>
>>
>
>--
>Misha Nasledov
>misha@xxxxxxxxxxxx
>http://nasledov.com/misha/
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniela Engert, systems engineer at MEDAV GmbH
Gräfenberger Str. 32-34, 91080 Uttenreuth, Germany
Phone ++49-9131-583-348, Fax ++49-9131-583-11


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/