linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniela Engert" <dani@ngrt.de>
To: "Misha Nasledov" <misha@nasledov.com>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: VIA Serial ATA chipset
Date: Wed, 13 Aug 2003 09:46:03 +0200 (CDT)	[thread overview]
Message-ID: <20030813074535.C3AB427AC8@mail.medav.de> (raw)
In-Reply-To: <20030813064923.GA27610@nasledov.com>

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@nasledov.com
>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



  reply	other threads:[~2003-08-13  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11  2:17 VIA Serial ATA chipset Misha Nasledov
     [not found] ` <20030811055522.31F6427A21@mail.medav.de>
2003-08-11  6:06   ` Misha Nasledov
     [not found]     ` <20030811062839.76F9216F24@mail.medav.de>
2003-08-11  6:34       ` Misha Nasledov
     [not found]         ` <20030811064757.7B1CF1C92C@mail.medav.de>
2003-08-11 22:34           ` Misha Nasledov
     [not found]             ` <20030812111332.351001ACFB@mail.medav.de>
2003-08-13  6:49               ` Misha Nasledov
2003-08-13  7:46                 ` Daniela Engert [this message]
2003-08-29 14:51                   ` libata update posted (was Re: VIA Serial ATA chipset) Jeff Garzik
2003-08-29 17:21                     ` Samuel Flory
2003-08-29 17:59                       ` Jeff Garzik
2003-08-29 18:09                         ` Samuel Flory

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030813074535.C3AB427AC8@mail.medav.de \
    --to=dani@ngrt.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=misha@nasledov.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).