From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Marc Leeman <marc.leeman@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: 2.6.22 flash boot
Date: Fri, 13 Jul 2007 23:48:57 +0400 [thread overview]
Message-ID: <4697D729.5010307@ru.mvista.com> (raw)
In-Reply-To: <20070713194013.GU2660@chiana.homelinux.org>
Hello.
Marc Leeman wrote:
> With the release of the 2.6.22, our boards didn't boot anymore. I traced
> the change back to 2.6.21-git10/2.6.21-git11.
> The reason they didn't boot was that the kernel didn't detect the flash
> where the root filesystem is stored on. The boards boot without an
> initrd, directly from flash.
> A file was removed (rom.c) and mentioned as obsolete in the ChangeLog.
[...]
> Am I missing something here?
It's been removed as conflicting with the new of_device probing code.
You can either register the "rom" device explicitly in your platform code, or
put it on some bus below the ones specified to of_platform_device_probe() --
by your platform code again...
WBR, Sergei
prev parent reply other threads:[~2007-07-13 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 19:40 2.6.22 flash boot Marc Leeman
2007-07-13 19:48 ` Sergei Shtylyov [this message]
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=4697D729.5010307@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=marc.leeman@gmail$(echo .)com \
/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