From: Michael Ellerman <michael@ellerman.id.au>
To: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: microblaze-uclinux@itee.uq.edu.au,
devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] of/flattree: use callback to setup initrd from /chosen
Date: Wed, 23 Dec 2009 00:17:36 +1100 [thread overview]
Message-ID: <1261487856.10767.128.camel@concordia> (raw)
In-Reply-To: <200912221854.37572.jeremy.kerr@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Tue, 2009-12-22 at 18:54 +0800, Jeremy Kerr wrote:
> Hi Michael,
>
> > > void early_init_dt_setup_initrd_arch(unsigned long start,
> > > unsigned long end);
> >
> > arch_early_init_dt_setup_initrd() makes more sense to me, but ..
>
> <foo>_arch has been the general convention for arch-specific hooks in
> drivers/of/.
Yuck, doh, guess I should have read those patches before they went in :)
> > > +#ifdef CONFIG_BLK_DEV_INITRD
> > > +void __init early_init_dt_setup_initrd_arch(unsigned long start,
> > > + unsigned long end)
> > > +{
> > > + initrd_start = (unsigned long)__va(start);
> > > + initrd_end = (unsigned long)__va(end);
> > > + initrd_below_start_ok = 1;
> > > +}
> > > +#endif
> >
> > Given you have two identical implementations why not make that the
> > default and make it weak, and let ARM override it.
>
> Yeah, that would be good too; just been avoiding weak as a potential source of
> magic voodoo complexity. Grant - up to you on this one.
Yeah, depends on what toolchains you're supporting, modern ones should
be OK but it can be troublesome.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-12-22 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 9:39 [PATCH] of/flattree: use callback to setup initrd from /chosen Jeremy Kerr
2009-12-22 10:47 ` Michael Ellerman
2009-12-22 10:54 ` Jeremy Kerr
2009-12-22 13:17 ` Michael Ellerman [this message]
2010-01-13 6:43 ` Grant Likely
2010-01-13 11:03 ` Michael Ellerman
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=1261487856.10767.128.camel@concordia \
--to=michael@ellerman.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jeremy.kerr@canonical.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.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;
as well as URLs for NNTP newsgroup(s).