From: Matt Sealey <matt@genesi-usa•com>
To: ppc-dev <linuxppc-dev@ozlabs•org>, linuxppc-embedded@ozlabs•org
Subject: Re: OF /chosen/initrd,* variables - patch, official?
Date: Tue, 21 Aug 2007 12:21:18 +0100 [thread overview]
Message-ID: <46CACAAE.5000304@genesi-usa.com> (raw)
In-Reply-To: <46CAC89F.2040100@genesi-usa.com>
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that
it "just works" on OF platforms? It seems only to be usable way too late
in boot to work, this code would have to be called in boot/main.c which seems
relatively.. impossible to achieve.. or called in some specialised platform
init code..
I hacked up a patch initially before I saw Milton's work and did it all
in main.c (and did the same to mkvmlinuz..) and it seemed to work okay
there.
I'm really curious as to the status and usefulness of this here.. :(
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
Matt Sealey wrote:
> Hi guys,
>
> Just a query here, there was a patch for /chosen/initrd,start and initrd,end
> variables gained from firmware or so, which allowed booting without getting
> those values into r3/r4, does anyone know the maintainer/author of that
> patch?
>
> Also, what are the chances of pushing it for 2.6.23 or 2.6.24? I can imagine
> it's fairly useful (at least it is to me)..
>
next prev parent reply other threads:[~2007-08-21 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 11:12 OF /chosen/initrd,* variables - patch, official? Matt Sealey
2007-08-21 11:21 ` Matt Sealey [this message]
2007-08-21 11:32 ` David Gibson
2007-08-21 12:19 ` Linux 2.6.23.rc3 boot issues on XUPV2P Computer - Service
2007-08-21 12:52 ` Grant Likely
2007-08-21 12:36 ` OF /chosen/initrd,* variables - patch, official? Matt Sealey
2007-08-21 12:42 ` David Gibson
2007-08-21 12:58 ` Matt Sealey
2007-08-21 13:54 ` David Gibson
2007-08-21 14:24 ` Matt Sealey
2007-08-22 1:44 ` David Gibson
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=46CACAAE.5000304@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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