From: Jeff Garzik <jgarzik@pobox.com>
To: Wes Newell <w.newell@verizon.net>
Cc: Uwe Koziolek <uwe.koziolek@gmx.net>,
"linux.ide" <linux-ide@vger.kernel.org>
Subject: Re: Pata support for SIS180
Date: Sun, 12 Jun 2005 23:34:37 -0400 [thread overview]
Message-ID: <42ACFECD.7060909@pobox.com> (raw)
In-Reply-To: <42ACAE15.4030001@verizon.net>
Wes Newell wrote:
> Uwe Koziolek wrote:
>
>> Wes Newell schrieb:
>>
>>
>>
>>> Can anyone tell me if/how one could add device support for the sis180
>>> chipset pata ports to the sis5513 module? I've tried adding this as
>>> others have said it works for the 965 southbridge,
>>>
>>> if ((trueid == 0x5518) || (trueid == 0x0180)) {
>>>
>>> but it stll doesn't see a real sis180 on a Jetway S755MAX MB.
>>>
>>
>>
>>
>> you must include the chip into the pci_device_id table
>>
>> static *struct* pci_device_id sis5513_pci_tbl[] = {
>> { PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5513, PCI_ANY_ID, PCI_ANY_ID,
>> 0, 0, 0},
>> { PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5518, PCI_ANY_ID, PCI_ANY_ID,
>> 0, 0, 0},
>> + { PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_180, PCI_ANY_ID, PCI_ANY_ID,
>> 0, 0, 0},
>> { 0, },
>> };
>>
>>
>> regards
>> Uwe Koziolek
>>
>>
>>
> Won't compile. I copied the sis180 line above into the code (- the +
> sign of course). I tried both 0x180 and 0x0180 as a trueid. Didn't
> matter. Keep in mind I'm not a C programmer.:-)
>
> This is the error I get;
>
> CC drivers/ide/pci/sis5513.o
> drivers/ide/pci/sis5513.c:955: error: `PCI_DEVICE_ID_SI_180' undeclared
> here (not in a function)
You need to add this #define to include/linux/pci_ids.h.
Jeff
next prev parent reply other threads:[~2005-06-13 3:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 13:35 Pata support for SIS180 Wes Newell
2005-06-12 20:31 ` Uwe Koziolek
2005-06-12 21:50 ` Wes Newell
2005-06-13 3:34 ` Jeff Garzik [this message]
2005-06-13 6:34 ` Wes Newell
2005-06-13 17:19 ` Wes Newell
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=42ACFECD.7060909@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=uwe.koziolek@gmx.net \
--cc=w.newell@verizon.net \
/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).