From: Ralf Baechle <ralf@linux-mips.org>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: why the early_initcall(au1x00_setup) do not work?
Date: Mon, 9 Jan 2006 14:56:10 +0000 [thread overview]
Message-ID: <20060109145610.GB4286@linux-mips.org> (raw)
In-Reply-To: <50c9a2250601082159p238cacd6r930709da9305479e@mail.gmail.com>
On Mon, Jan 09, 2006 at 01:59:34PM +0800, zhuzhenhua wrote:
> i download a standard 2.6.14 kernel, and compile it for dbau1100, and
> i find the early_initcall(au1x00_setup) was not compiled into the
> vmlinux.
> and i find at the linux-mips cvs, it used plat_setup instead of early_initcall.
> does it means my toolchain is not correct to compile the
> early_initcall, or in the standard 2.6.14 kernel, the early_initcall
> do not work well?
You've downloaded a kernel.org kernel it would seem - doesn't fly for MIPS.
Instead get a kernel from linux-mips.org.
The early_initcall() construct has been removed.
Ralf
next prev parent reply other threads:[~2006-01-09 14:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 5:59 why the early_initcall(au1x00_setup) do not work? zhuzhenhua
2006-01-09 14:56 ` Ralf Baechle [this message]
2006-01-09 15:20 ` P. Christeas
2006-01-09 15:24 ` Ralf Baechle
2006-01-10 1:02 ` zhuzhenhua
2006-01-10 14:19 ` Ralf Baechle
2006-01-10 15:40 ` Ivan Korzakow
2006-01-10 15:57 ` P. Christeas
2006-01-10 16:38 ` Ivan Korzakow
2006-01-10 16:57 ` P. Christeas
2006-01-10 17:15 ` Ivan Korzakow
2006-01-10 23:20 ` Ralf Baechle
2006-01-11 15:17 ` Ivan Korzakow
2006-01-10 21:53 ` Ralf Baechle
2006-01-11 11:10 ` Ivan Korzakow
2006-01-11 11:20 ` Ralf Baechle
2006-01-11 15:07 ` Ivan Korzakow
2006-01-11 19:07 ` Ralf Baechle
2006-01-11 15:14 ` Ivan Korzakow
2006-01-10 17:38 ` Jordan Crouse
2006-01-11 2:04 ` zhuzhenhua
2006-01-11 12:16 ` Ralf Baechle
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=20060109145610.GB4286@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=zzh.hust@gmail.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.