From: Wolfgang Denk <wd@denx.de>
To: "XOL" <xol@mail.ru>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Re[4]: initrd problem. CRC Error.
Date: Mon, 09 Jun 2003 22:21:27 +0200 [thread overview]
Message-ID: <20030609202132.A0579C5FD7@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 09 Jun 2003 17:05:55 +0400." <E19PMLT-000Hhi-00.xol-mail-ru@f16.mail.ru>
In message <E19PMLT-000Hhi-00.xol-mail-ru@f16.mail.ru> you wrote:
>
> I think I found out what is a problem
> The thread bi_record and initrd
> http://lists.linuxppc.org/linuxppc-embedded/200211/msg00286.html
>
> Discuss the problem of corrupting initrd by bi_record - board info record.
> As I have no good background in bootloading could you please let me know
> 1. What is a current status of fixing the bug. Are there any
> new kernel version there it was fixed
Don't know. Never ran into this problem.
> 2. Does this problem depends on bootloader. Will u-boot fix it?
Yes, it probably depends on the bootloader. More exactly, itt depends
on the interface between the bootloader and the Linux kernel.
U-Boot works fine if your kernel is configured for U-Boot. I am not
aware of a problem that needs fixing.
> 3. Does anybody succeded to use 2.4.18 with initrd? How?
Yes, we did. Many times. We use U-=Boot, and make sure that the
kernel interface fits.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"That unit is a woman."
"A mass of conflicting impulses."
-- Spock and Nomad, "The Changeling", stardate 3541.9
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-06-09 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19PMLT-000Hhi-00.xol-mail-ru@f16.mail.ru>
2003-06-09 17:42 ` Booting Linux without bootloader on Sandpoint X3 with PPC755 CPU, Montavista Linux dong in kang
2003-06-09 21:29 ` Mark A. Greer
2003-06-09 20:21 ` Wolfgang Denk [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=20030609202132.A0579C5FD7@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xol@mail.ru \
/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).