public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Buggy PCI drivers - do not mark pci_device_id as discardable data
Date: Tue, 9 Sep 2003 22:04:52 +0100	[thread overview]
Message-ID: <20030909220452.S4216@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0309091559110.14426@montezuma.fsmlabs.com>; from zwane@linuxpower.ca on Tue, Sep 09, 2003 at 04:02:58PM -0400

On Tue, Sep 09, 2003 at 04:02:58PM -0400, Zwane Mwaikambo wrote:
> On Tue, 9 Sep 2003, Russell King wrote:
> 
> > --- orig/drivers/char/watchdog/amd7xx_tco.c	Sat Jun 14 22:33:48 2003
> > +++ linux/drivers/char/watchdog/amd7xx_tco.c	Tue Sep  9 20:45:16 2003
> > @@ -294,7 +294,7 @@
> >  	.fops	= &amdtco_fops
> >  };
> >  
> > -static struct pci_device_id amdtco_pci_tbl[] __initdata = {
> > +static struct pci_device_id amdtco_pci_tbl[] = {
> >  	/* AMD 766 PCI_IDs here */
> >  	{ PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_OPUS_7443, PCI_ANY_ID, PCI_ANY_ID, },
> >  	{ 0, }
> 
> That's not a bug.
>
> > --- orig/drivers/char/watchdog/i810-tco.c	Sun Aug  3 11:21:11 2003
> > +++ linux/drivers/char/watchdog/i810-tco.c	Tue Sep  9 20:45:16 2003
> > @@ -301,7 +301,7 @@
> >   * register a pci_driver, because someone else might one day
> >   * want to register another driver on the same PCI id.
> >   */
> > -static struct pci_device_id i810tco_pci_tbl[] __initdata = {
> > +static struct pci_device_id i810tco_pci_tbl[] = {
> >  	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801AA_0,	PCI_ANY_ID, PCI_ANY_ID, },
> >  	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801AB_0,	PCI_ANY_ID, PCI_ANY_ID, },
> >  	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801BA_0,	PCI_ANY_ID, PCI_ANY_ID, },
> 
> Neither is that.
> 
> > --- orig/drivers/char/hw_random.c	Sat Jun 14 22:33:46 2003
> > +++ linux/drivers/char/hw_random.c	Tue Sep  9 20:45:16 2003
> > @@ -149,7 +149,7 @@
> >   * register a pci_driver, because someone else might one day
> >   * want to register another driver on the same PCI id.
> >   */
> > -static struct pci_device_id rng_pci_tbl[] __initdata = {
> > +static struct pci_device_id rng_pci_tbl[] = {
> >  	{ 0x1022, 0x7443, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_amd },
> >  	{ 0x1022, 0x746b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_amd },
> 
> This too

Ok, I'm happy that this aren't (after reading someone elses explaination).

Having these different makes it hard to ensure that no further bad cases
exist in the tree though.

I want this to be foolproof, because its me people bug when their cardbus
cards oops when they insert the damned things.  If people are happy to
ignore this issue, I'm happy to ignore the bug reports.

It basically isn't something I want to deal with, and we need to find a
way to stop these stupidities appearing in the first place.

Any ideas?

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core

  parent reply	other threads:[~2003-09-09 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 19:48 Buggy PCI drivers - do not mark pci_device_id as discardable data Russell King
2003-09-09 20:02 ` Zwane Mwaikambo
2003-09-09 20:59   ` Russell King
2003-09-09 21:04   ` Russell King [this message]
2003-09-09 21:22     ` Alan Cox
2003-09-09 21:28       ` Zwane Mwaikambo
2003-09-09 21:33       ` Russell King
2003-09-09 20:14 ` Dave Jones
2003-09-09 20:57   ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2003-09-10  3:35 agpgart support for intel SHG2 motherboard, serverworks chipset Greg KH
2003-09-09 23:12 ` Buggy PCI drivers - do not mark pci_device_id as discardable data Matt Domsch
2003-09-10  4:24   ` Greg KH
2003-09-10  9:31     ` Matt Domsch
2003-09-10 17:17       ` Matt Domsch
2003-09-11 21:20         ` Greg KH

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=20030909220452.S4216@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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