From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc-leon patches round 5 (to follow) (right numbering)
Date: Mon, 17 Aug 2009 10:27:32 +0000 [thread overview]
Message-ID: <4A893094.8050400@gaisler.com> (raw)
In-Reply-To: <20090802.195140.26174602.davem@davemloft.net>
Hi,
> arch/sparc/kernel/built-in.o: In function `leon_node_init':
> (.init.text+0x29c4): undefined reference to `_amba_init'
I posted the patchset version 6 (see mailing list). This time
_amba_init() is not called directly. I had to use another aproach
than the XXX_initcall() aproach that Thomas Boegendoerfer suggested:
leon_node_init() is called too early in the boot process
(main()->setup_arch()->paging_init()->prom_build_devicetree()..) and
as far as I understand it there is no xxx_initcall() that gets
called that early => therefore I used a callback instead:
...
void __initdata (*prom_amba_init)(struct device_node *dp, struct device_node ***nextp) = 0;
...
if (prom_amba_init &&
...
prom_amba_init(dp, nextp);
}
...
The callback will be initialized by the _bootloader_.
> When you fix this up and repost the series, do me another favor, try
> to build the kernel successfully after each and every patch. With
> LEON enabled, the tree does not build after patch #3 because srmmu.c
> doesn't include asm/leon.h yet and thus srmmu_swprobe() isn't declared.
I didnt really undestand this one: The patch is split up in 5 subpatches
that should logically divide the big patch. There guess are dependencies
among the subpatches. The only way I can think of is to send all 5 subpatches
as one big patch.
Is it ok with the version 6 patches that I just sent on the mailing list
anyway? (that is 5 subpatches)?
-- Greetings Konrad
next prev parent reply other threads:[~2009-08-17 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 2:51 sparc-leon patches round 5 (to follow) (right numbering) David Miller
2009-08-03 3:13 ` David Miller
2009-08-03 19:05 ` konrad
2009-08-03 20:05 ` Thomas Bogendoerfer
2009-08-04 4:17 ` David Miller
2009-08-17 10:27 ` Konrad Eisele [this message]
2009-08-18 1:39 ` David Miller
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=4A893094.8050400@gaisler.com \
--to=konrad@gaisler.com \
--cc=sparclinux@vger.kernel.org \
/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.