From: Borlizzi Giacomo <giacomo.borlizzi@tei.ericsson.se>
To: Thomas <tle@home.se>
Cc: linuxppc-embedded@lists.linuxppc.org,
"Giacomo Borlizzi (TEI)" <giacomo.borlizzi@tei.ericsson.se>
Subject: Re: 2.4 Kernel for mpc860
Date: Wed, 10 Jan 2001 19:55:58 +0100 [thread overview]
Message-ID: <3A5CB03E.CC4B6C5D@tei.ericsson.se> (raw)
In-Reply-To: 3A5C823A.6353DCE2@home.se
Hi,
I have same problem. It is not clear wich is better.
I'm trying to adapt to my board in this days the linux-2.4.0-test9, previous
version was 2.2.13
but now?
/Giacomo Borlizzi
Thomas wrote:
> Hi all.
> I want to compile 2.4 for my custom board with
> a mpc860. Which source tree should I base my
> kernel on?
>
> Regards,
> /Thomas Lange/
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-10 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 15:39 2.4 Kernel for mpc860 Thomas
2001-01-10 18:55 ` Borlizzi Giacomo [this message]
2001-01-11 0:58 ` 405GP f_dentry panics Glenn Toshi Martin
2001-01-11 17:56 ` Frank Rowand
2001-01-18 19:35 ` Booting MCP750 stand alone Tom Shaver
2001-01-18 16:50 ` Matt Porter
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=3A5CB03E.CC4B6C5D@tei.ericsson.se \
--to=giacomo.borlizzi@tei.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tle@home.se \
/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).