From: Jon Loeliger <jdl@freescale.com>
To: "Garcia Jérémie" <GARCIAJ@3il.fr>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: RE : Booting linux for 405EP --> mem_pieces_find( ) nightmare
Date: Thu, 28 Apr 2005 11:25:10 -0500 [thread overview]
Message-ID: <1114705509.4084.3.camel@gleep> (raw)
In-Reply-To: <D4FDDD1349B5AC46B68FC26AD8AF42D6226B25@exnet.3il.fr>
On Thu, 2005-04-28 at 05:36, Garcia Jérémie wrote:
> So the return of this function was incoherent and drove me to a kernel
> panic.
> As a conclusion I just defined my own board info structure in the
> platform_init() function:
Oh no!
We're going to have to work on isolating the bd_t virus
with my patch on the linuxppc-embedded list...
*sigh*
jdl
prev parent reply other threads:[~2005-04-28 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 10:36 RE : Booting linux for 405EP --> mem_pieces_find( ) nightmare Garcia Jérémie
2005-04-28 16:25 ` Jon Loeliger [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=1114705509.4084.3.camel@gleep \
--to=jdl@freescale.com \
--cc=GARCIAJ@3il.fr \
--cc=linuxppc-dev@ozlabs.org \
/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).