From: Andrew Hutchings <info@a-wing.co.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sis5513.c patch
Date: Wed, 08 Jun 2005 10:28:57 +0100 [thread overview]
Message-ID: <42A6BA59.3010207@a-wing.co.uk> (raw)
In-Reply-To: <58cb370e05060802149b2f530@mail.gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> [ Andrew, please remove this patch from -mm queue. ]
>
> On 6/8/05, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
>>On 6/8/05, Andrew Hutchings <info@a-wing.co.uk> wrote:
>>
>>>Bartlomiej Zolnierkiewicz wrote:
>>>
>>>>On 6/8/05, Andrew Hutchings <info@a-wing.co.uk> wrote:
>>>>
>>>>
>>>>>Hi,
>>>>
>>>>
>>>>Hi,
>>>>
>>>
>>>Hi again,
>>>
>>>
>>>>>I'm not sure if a similar patch has been submitted or not, but here is a
>>>>>patch to get DMA working on ASUS K8S-MX with a SiS 760GX/SiS 965L
>>>>>chipset combo.
>>>>
>>>>
>>>>This patch is incorrect, it adds PCI ID of SiS IDE controller (this ID
>>>>is common for almost all SiS IDE controllers and is already present in
>>>>sis5513_pci_tbl[]) to the table of SiS Host PCI IDs. As a result driver
>>>>will try to use ATA_133 on all _unknown_ IDE controllers. You need
>>>>to add PCI ID of the Host chipset (lspci should reveal it) instead.
>
>
> Second look into sis5513.c and another problem turns out - patch breaks
> support for IDE controllers integrated into 961 and 961B South Bridges
> (ATA_133 is used instead of ATA_100 and ATA133a).
>
> For unknown Host Bridges driver checks for presence of 961/961B/962/963
> South Bridges by checking true device ID (please see sis5513.c for details)
> and assigns 'chipset_family' accordingly (ATA_100/ATA_133a or ATA_133).
>
> You have 965L South Bridge so probably it has newer true device ID
> and may also require different programming sequence.
>
Ah, you see this is what happens when I enter the scary world of driver
patching, I'll will stick to patching/developing apps in future I think ;)
>
>>Could you please send full lspci -vvv output?
>
>
> and lspci -xxx
>
> Bartlomiej
>
I'm just installing another one of those boards now ready to go into our
racks later today, I'll give you the output from that shortly.
--
Andrew Hutchings (A-Wing)
Linux Guru - Netserve Consultants Ltd. - http://www.domaincity.co.uk/
Admin - North Wales Linux User Group - http://www.nwlug.org.uk/
BOFH excuse 24: network packets travelling uphill (use a carrier pigeon)
next prev parent reply other threads:[~2005-06-08 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 22:37 sis5513.c patch Andrew Hutchings
2005-06-07 22:57 ` Francois Romieu
2005-06-07 23:20 ` Andrew Hutchings
2005-06-08 22:51 ` sis190 (was: Re: sis5513.c patch) Francois Romieu
2005-06-09 4:54 ` sis190 Andrew Hutchings
2005-06-09 12:02 ` sis190 Andrew Hutchings
2005-06-09 21:18 ` sis190 Francois Romieu
2005-06-10 13:55 ` sis190 Andrew Hutchings
2005-06-10 23:41 ` sis190 Francois Romieu
2005-06-09 15:17 ` sis5513.c patch Vojtech Pavlik
2005-06-08 7:27 ` Bartlomiej Zolnierkiewicz
2005-06-08 8:23 ` Andrew Hutchings
2005-06-08 8:58 ` Bartlomiej Zolnierkiewicz
2005-06-08 9:14 ` Bartlomiej Zolnierkiewicz
2005-06-08 9:28 ` Andrew Hutchings [this message]
2005-06-08 10:28 ` Andrew Hutchings
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=42A6BA59.3010207@a-wing.co.uk \
--to=info@a-wing.co.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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