From: Andrew Morton <akpm@osdl.org>
To: "S. Anderson" <sa@xmission.com>
Cc: sa@xmission.com, pavel@xal.co.uk, linux-kernel@vger.kernel.org,
adaplas@pol.net
Subject: Re: OOPS 2.6.0-test2, modprobe i810fb
Date: Mon, 28 Jul 2003 22:32:29 -0700 [thread overview]
Message-ID: <20030728223229.528ddad1.akpm@osdl.org> (raw)
In-Reply-To: <20030728231812.A20738@xmission.xmission.com>
"S. Anderson" <sa@xmission.com> wrote:
>
> when that driver is
> "i810fb, i810_audio or intel-agp" (and i810fb, i810_audio or intel-agp
> is allready loaded) the id_table is at an address that cant be handled,
> thus cauing the oops. I am having trouble figuring out why
> pci_drv->id_table isnt valid in this case.
Does this fix? I'm not sure whether that "{ }" in there will generate
another table entry...
diff -puN drivers/char/agp/intel-agp.c~intel-agp-oops-fix drivers/char/agp/intel-agp.c
--- 25/drivers/char/agp/intel-agp.c~intel-agp-oops-fix 2003-07-28 22:30:30.000000000 -0700
+++ 25-akpm/drivers/char/agp/intel-agp.c 2003-07-28 22:30:53.000000000 -0700
@@ -1426,7 +1426,7 @@ static struct pci_device_id agp_intel_pc
.subvendor = PCI_ANY_ID,
.subdevice = PCI_ANY_ID,
},
- { }
+ { 0, },
};
MODULE_DEVICE_TABLE(pci, agp_intel_pci_table);
_
next prev parent reply other threads:[~2003-07-29 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 17:18 OOPS 2.6.0-test2, modprobe i810fb Pavel Rabel
2003-07-29 2:19 ` S. Anderson
2003-07-29 3:26 ` Andrew Morton
2003-07-29 5:18 ` S. Anderson
2003-07-29 5:32 ` Andrew Morton [this message]
2003-07-30 2:56 ` Bill Davidsen
2003-07-30 20:56 ` Michael Driscoll
2003-07-29 5:59 ` Andrew Morton
2003-07-29 7:24 ` S. Anderson
2003-07-29 7:54 ` Andrew Morton
2003-07-29 8:18 ` S. Anderson
2003-07-29 12:00 ` Alan Cox
2003-07-29 19:59 ` Andrew Morton
2003-07-29 23:04 ` S. Anderson
2003-07-29 9:34 ` Pavel Rabel
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=20030728223229.528ddad1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@pol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@xal.co.uk \
--cc=sa@xmission.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.