From: Tom Roberts <tjroberts@lucent.com>
To: Dan Malek <dan@netx4.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Query: kernel version for MPC750/MPC7400
Date: Tue, 27 Jun 2000 09:00:28 -0500 [thread overview]
Message-ID: <3958B37C.1F280F3F@lucent.com> (raw)
In-Reply-To: 3957DEFF.9064056E@netx4.com
Dan Malek wrote:
> You shouldn't be using 2.2.15 with 8xx. I am not going to discuss
> the history right now, but the only reliable verion of 2.2.xx Linux
> is the 2.2.13 version on the MontaVista Web site (www.mvista.com).
How about on an embedded MPC750 or MPC7400? Before joining this
list I discovered Kernel version 2.2.15 on Yellowdog and have been
using that. I have made a dozen or so small mods to the kernel to
get it to run on our boards, and have seen no problems, so far....
There are zillions of references to CONFIG_8xx throughout the source.
These boards are essentially embedded supercomputers;
the only devices they have are the drivers I wrote, which
use memory buffers to/from the host PCI as a 'serial'
console and a network interface.
Tom Roberts tjroberts@lucent.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-27 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 21:16 Image caching/swap bugs Whitney, John
2000-06-26 22:53 ` Dan Malek
2000-06-27 14:00 ` Tom Roberts [this message]
2000-06-27 16:46 ` Query: kernel version for MPC750/MPC7400 Dan Malek
2000-06-27 23:19 ` Thomas Poole
-- strict thread matches above, loose matches on Subject: below --
2000-06-27 14:22 Patrick Lerda
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=3958B37C.1F280F3F@lucent.com \
--to=tjroberts@lucent.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.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).