From: Ed Tomlinson <tomlins@cam.org>
To: Rusty Russell <rusty@rustcorp.com.au>, Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [drm:drm_init] *ERROR* Cannot initialize the agpgart module.
Date: Wed, 18 Dec 2002 07:57:53 -0500 [thread overview]
Message-ID: <200212180757.53583.tomlins@cam.org> (raw)
In-Reply-To: <20021218094714.43C712C076@lists.samba.org>
On December 18, 2002 04:46 am, Rusty Russell wrote:
> In message <20021218102004.A4947@suse.de> you write:
> > On Wed, Dec 18, 2002 at 06:07:48PM +1100, Rusty Russell wrote:
> > > Dave, it's true that it's my fault, but I'm afraid it looks like your
> > > bug 8). This is most likely karma for not reporting bugs in the
> > > module code when you had problems 8)
> >
> > Bah, my bad. 8)
>
> That's OK, you're in good company as the first I heard from Alan was
> that he gave up kernel work because "modules was so broken". 8(
>
> > > static int __init agp_backend_initialize(struct pci_dev *dev)
> > >
> > > ....
> > > int agp_register_driver (struct pci_dev *dev)
> > > {
> > > ....
> > > ret_val = agp_backend_initialize(dev);
> >
> > Whoops. Thanks, fixed up here.
> > I'll bet I duped that bug in other places too, as I've rejigged
> > stuff around. I'll double check those paths in a mo.
> >
> > > Ed, does it work if you take all the __init out of the agp code?
> >
> > My moneys on it working. The oops looked like it was jumping to oblivion
> > when it called agp_backend_initialize. So the new modutils discards
> > __init sections ? That's a new feature isn't it ?
>
> Yeah, kind of a bonus. It's actually arch-dependent.
>
> I've added an item in my TODO list to check for relocations on the
> non-init section which point into the init sections. It'd be cute.
> It'll probably never go into the main kernel, and it's no actually an
> error, you can imagine code which does:
>
> if (initializing)
> some_init_func();
Dave when you have this in a bk tree let me know and I will pull and
verify it working here.
Thanks to both of you
Ed Tomlinson
next parent reply other threads:[~2002-12-18 12:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021218094714.43C712C076@lists.samba.org>
2002-12-18 12:57 ` Ed Tomlinson [this message]
2002-12-18 16:29 ` Dave Jones
[not found] ` <200212181803.23279.tomlins@cam.org>
[not found] ` <20021219105909.GE29122@suse.de>
2002-12-20 23:29 ` Ed Tomlinson
2002-12-21 14:22 ` Dave Jones
2002-12-22 4:41 ` Ed Tomlinson
2002-12-22 12:28 ` Dave Jones
2002-12-22 14:08 ` Ed Tomlinson
2002-12-23 1:10 ` Rusty Russell
2002-12-23 12:10 ` Dave Jones
2002-12-26 3:51 ` Rusty Russell
2002-12-28 0:20 ` Roman Zippel
2002-12-17 1:49 Ed Tomlinson
2002-12-17 8:06 ` Paul P Komkoff Jr
2002-12-17 12:50 ` Ed Tomlinson
2002-12-20 1:30 ` Matt Bernstein
2002-12-20 1:43 ` Randy.Dunlap
2002-12-20 9:33 ` Dave Jones
2002-12-17 12:33 ` Dave Jones
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=200212180757.53583.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome