From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] initcall and setup
Date: Fri, 14 Jan 2000 17:13:44 -0800 [thread overview]
Message-ID: <200001150113.RAA16646@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Fri, 14 Jan 2000 17:48:31 PST." <20000114174831.W11300@thepuffingroup.com>
Matthew Wilcox wrote:
>
> One of the things which has changed during 2.3 development is
> initialisation.
...
> Unfortunately, we can't take advantage of this, because we don't yet have
> ELF tools. This is implemented through an ELF section called __initcall
> which contains the address of the function to call. We could try to hack
> something together with SOM, but I'd really rather not put the work in
> that will just be dumped later.
Just a clarification: The kernel will use ELF once the tool chain is
in place. The kernel is SOM now only because of our dependency
on HP-UX ld. Any forcasts for when we can switch to ELF?
...
> and why if you diff our kernel against Linus', you will find that we have
> reinserted some of the explicit calls to the setup routines that have
> been eliminated from the mainline tree. It also explains why sometimes
> a driver may not be called even though you compiled it in.
Any general rules on where to reinsert stuff? (eg tulip_probe)
In the same place it's in the linux-2.2?
Is someone making a note to make sure the reinserted code gets
dropped when we migrate to either the next 2.3 (or possibly 2.4) release?
thanks,
grant
Grant Grundler
Unix Development Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-01-15 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 22:48 [parisc-linux] initcall and setup Matthew Wilcox
2000-01-15 1:13 ` Grant Grundler [this message]
2000-01-15 2:41 ` Alex deVries
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=200001150113.RAA16646@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox