From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: alan@lxorguk.ukuu.org.uk, haveblue@us.ibm.com, akpm@digeo.com,
rmk@arm.linux.org.uk, rddunlap@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: The magical mystical changing ethernet interface order
Date: Thu, 8 May 2003 13:24:35 -0300 [thread overview]
Message-ID: <20030508162434.GB9526@conectiva.com.br> (raw)
In-Reply-To: <20030508.075438.52189319.davem@redhat.com>
Em Thu, May 08, 2003 at 07:54:38AM -0700, David S. Miller escreveu:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Date: 08 May 2003 15:55:31 +0100
>
> Unfortunately for the ISA driver code we *have* to rely on link
> order or rip out the __init stuff and use Space.c type hacks.
>
> I do no argue that needing an invocation order is bogus.
> I merely disagree with the way we're trying to achieve it.
>
> You don't need Space.c magic, the linker in binutils has mechanisms by
> which this can be accomplished and we already use this in 2.5.x
>
> Have a peek at __define_initcall($NUM,fn), imagine it with one more
> argument $PRIO. It might look like this:
>
> #define __define_initcall(level,prio,fn) \
> static initcall_t __initcall_##fn __attribute__
> ((unused,__section__ ("\.initcall" level "." prio ".init"))) = fn
>
> Use the 'prio' number to define the ordering. The default for
> modules that don't care about relative ordering within a class
> use a value like "9999" or something like that.
I was thinking of a different implementation, that I just made sure to forgot
as this one seems _much_ nicer indeed.
- Arnaldo
next prev parent reply other threads:[~2003-05-08 16:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 13:14 The magical mystical changing ethernet interface order Russell King
2003-05-07 15:18 ` Dick Streefland
2003-05-07 15:38 ` Jeff Garzik
2003-05-07 15:24 ` Randy.Dunlap
2003-05-07 17:14 ` Russell King
2003-05-07 22:04 ` Andrew Morton
2003-05-07 22:28 ` Dave Hansen
2003-05-08 12:05 ` David S. Miller
2003-05-08 14:55 ` Alan Cox
2003-05-08 14:54 ` David S. Miller
2003-05-08 16:24 ` Arnaldo Carvalho de Melo [this message]
2003-05-08 16:26 ` Jeff Garzik
2003-05-08 16:30 ` Randy.Dunlap
2003-05-11 18:41 ` Jeff Garzik
2003-05-08 17:56 ` Kai Germaschewski
2003-05-08 17:36 ` Linus Torvalds
2003-05-09 6:51 ` Richard Henderson
2003-05-08 19:32 Jean Tourrilhes
2003-05-08 21:43 ` Eli Carter
2003-05-08 22:19 ` Jean Tourrilhes
2003-05-08 21:46 ` Alan Cox
2003-05-08 23:23 ` Randy.Dunlap
2003-05-08 23:38 Ray Lee
2003-05-09 12:41 ` Dick Streefland
2003-05-09 14:33 ` Mr. James W. Laferriere
2003-05-10 7:42 Thomas Hood
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=20030508162434.GB9526@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rmk@arm.linux.org.uk \
/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).