From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: info@a-wing.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: sis5513.c patch
Date: Wed, 8 Jun 2005 10:58:09 +0200 [thread overview]
Message-ID: <58cb370e05060801585b49020e@mail.gmail.com> (raw)
In-Reply-To: <42A6AB1B.8000800@a-wing.co.uk>
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.
>
> Unless I am reading the following wrong 5513 is the PCI ID:
It is PCI ID of the IDE interface but you need PCI ID of the North Bridge.
The thing is that SiS is using the same PCI ID for all IDE controllers and
driver shouldn't be unconditionally programming all unknown/future SiS
IDE controllers as they may differ from the current ones.
> 00:02.5 Class 0101: 1039:5513 (rev 01) (prog-if 80 [Master])
> Subsystem: 1043:8139
> Flags: bus master, medium devsel, latency 128
> I/O ports at <unassigned>
> I/O ports at <unassigned>
> I/O ports at <unassigned>
> I/O ports at <unassigned>
> I/O ports at ffa0 [size=16]
> Capabilities: [58] Power Management version 2
Could you please send full lspci -vvv output?
> >
> > Thanks,
> > Bartlomiej
>
> Regards
> Andrew
> --
> 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 424: operation failed because: there is no message for this
> error (#1014)
>
next prev parent reply other threads:[~2005-06-08 8:58 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 [this message]
2005-06-08 9:14 ` Bartlomiej Zolnierkiewicz
2005-06-08 9:28 ` Andrew Hutchings
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=58cb370e05060801585b49020e@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=info@a-wing.co.uk \
--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