From: Eugene Surovegin <ebs@ebshome.net>
To: Pawel Studencki <pstudencki@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: using initramfs with ppc
Date: Mon, 18 Apr 2005 15:01:33 -0700 [thread overview]
Message-ID: <20050418220133.GD25352@gate.ebshome.net> (raw)
In-Reply-To: <20050418212401.33270.qmail@web51310.mail.yahoo.com>
On Mon, Apr 18, 2005 at 02:24:01PM -0700, Pawel Studencki wrote:
> It can be wrong kernel parameter or problem with mtd
> or cramfs support. But if I see my kernel messages,
> everything seems to be OK for me. I've attached kernel
> logging, so let me know, if I'm wrong.
Could you send me privately your .config ?
--
Eugene
next prev parent reply other threads:[~2005-04-18 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 21:24 using initramfs with ppc Pawel Studencki
2005-04-18 22:01 ` Eugene Surovegin [this message]
2005-04-19 0:36 ` Manoj Padhi
2005-04-19 3:35 ` HW + SW development tools for embedded linux (was Re: using initramfs with ppc) Ricardo Scop
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 15:34 using initramfs with ppc Pawel Studencki
2005-04-18 16:03 ` Eugene Surovegin
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=20050418220133.GD25352@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=pstudencki@yahoo.com \
/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).