From: Matthew Wilcox <matthew@wil.cx>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Joel Soete <soete.joel@tiscali.be>,
linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: a fix for NS87415 on C3K broken
Date: Wed, 22 Sep 2004 17:53:41 +0100 [thread overview]
Message-ID: <20040922165341.GN16153@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040922163708.GD4766@colo.lackof.org>
On Wed, Sep 22, 2004 at 10:37:08AM -0600, Grant Grundler wrote:
> On Wed, Sep 22, 2004 at 12:41:21PM +0200, Joel Soete wrote:
> > --- arch/parisc/kernel/pci.c.Orig 2004-09-22 09:47:02.000000000 +0200
> > +++ arch/parisc/kernel/pci.c 2004-09-22 11:26:02.104187784 +0200
> > +/* Used in drivers/pci/quirks.c */
> > +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_NS, PCI_DEVICE_ID_NS_87415, superio_fixup_pci);
>
> Uhm...any clue why this works?
> The same entry in drivers/parisc/superio.c should work too but it doesn't.
> I'd rather fix that than just blindly moving it.
I think I know. The define is:
#define DECLARE_PCI_FIXUP_HEADER(vendor, device, hook) \
static struct pci_fixup __pci_fixup_##vendor##device##hook __attribute_u
sed__ \
__attribute__((__section__(".pci_fixup_header"))) = { \
vendor, device, hook };
Now, that's dealt with by include/asm-generic/vmlinux.lds.h:
#define RODATA \
[...]
/* PCI quirks */ \
.pci_fixup : AT(ADDR(.pci_fixup) - LOAD_OFFSET) { \
VMLINUX_SYMBOL(__start_pci_fixups_header) = .; \
*(.pci_fixup_header) \
VMLINUX_SYMBOL(__end_pci_fixups_header) = .; \
VMLINUX_SYMBOL(__start_pci_fixups_final) = .; \
*(.pci_fixup_final) \
VMLINUX_SYMBOL(__end_pci_fixups_final) = .; \
} \
which links them all together. *However* ... maybe order is important.
There's a grotty-looking:
c03f347c d __pci_fixup_PCI_ANY_IDPCI_ANY_IDquirk_ide_bases
which may need to come after our superio quirk? I'm just testing this theory now ...
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-09-22 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 16:17 NS87415 on C3K broken Grant Grundler
2004-09-16 22:50 ` Bartlomiej Zolnierkiewicz
2004-09-16 23:25 ` Grant Grundler
2004-09-17 0:43 ` Bartlomiej Zolnierkiewicz
2004-09-22 10:41 ` a fix for " Joel Soete
2004-09-22 16:37 ` Grant Grundler
2004-09-22 16:53 ` Matthew Wilcox [this message]
2004-09-22 17:21 ` Joel Soete
2004-09-22 17:41 ` [parisc-linux] " Matthew Wilcox
2004-09-23 16:21 ` Joel Soete
2004-09-23 16:27 ` Randolph Chung
2004-09-24 7:04 ` Joel Soete
2004-09-24 16:17 ` Joel Soete
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=20040922165341.GN16153@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=bzolnier@elka.pw.edu.pl \
--cc=grundler@parisc-linux.org \
--cc=linux-ide@vger.kernel.org \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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