From: Scott Wood <scottwood@freescale.com>
To: Dan.Geer@faa.gov
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BSE-IP
Date: Tue, 26 Jan 2010 16:17:53 -0600 [thread overview]
Message-ID: <4B5F6A11.70409@freescale.com> (raw)
In-Reply-To: <OF54D7A55A.FE6F4A1D-ON852576B7.00781D7D-852576B7.00794B17@faa.gov>
Dan.Geer@faa.gov wrote:
> Any idea of the last kernel version that worked? So I know I can count on
> that as a reference?
I'm not familiar with the board, sorry -- was just pointing out that
there shouldn't be anything too dependent on the particular boards/chips
that are currently supported out-of-the-box, and it should be easier
to add a new board than it used to be.
> I have the 2.2 pre7 from BSE, but there have been a few changes since. ;^)
Hopefully not changes in the board. :-)
That kernel should still work for extracting any knowledge about the
board's hardware that may or may not be clear from its documentation.
> It appears the image (bootwrapper) needs to be completely self-contained,
> and needs to understand how to read the flash parameters. That's on my
> list.
What firmware is on the board?
-Scott
next prev parent reply other threads:[~2010-01-26 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 20:30 BSE-IP Dan.Geer
2010-01-26 21:03 ` BSE-IP Scott Wood
2010-01-26 22:04 ` BSE-IP Dan.Geer
2010-01-26 22:17 ` Scott Wood [this message]
2010-01-26 23:28 ` BSE-IP Dan.Geer
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 18:08 BSE-IP Dan.Geer
2010-02-01 18:24 ` BSE-IP Scott Wood
2010-02-01 18:59 ` BSE-IP Dan.Geer
2010-02-01 19:06 ` BSE-IP Scott Wood
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=4B5F6A11.70409@freescale.com \
--to=scottwood@freescale.com \
--cc=Dan.Geer@faa.gov \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.