From: "Pedro Aguilar" <paguilar@junkerhq.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: kernel 2.4.26 doesn't seem to work with a MPC859T
Date: Fri, 16 Jul 2004 12:25:21 +0200 (CEST) [thread overview]
Message-ID: <54144.127.0.0.1.1089973521.squirrel@junkerhq.net> (raw)
In-Reply-To: <s0f7edc2.025@EMAIL>
Hi,
I have a custom board with a MPC859T. When I do the 'gmake xconfig' in the
processor type option, the MPC859T does not appear. I have tried the 860L
and FADS but the kernel does not boot, it doesn't print any message.
Wich processor type could be compatible with the 859T?
Are there other options that are affecting this behaviour?
I download a vanilla kernel 2.4.26 and I'm using ELDK 3.0.
Thanks in advance.
Pedro Aguilar
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-16 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 9:25 Why not kmalloc() ?? Rupesh S
2004-07-16 10:25 ` Pedro Aguilar [this message]
2004-07-16 11:34 ` Magnus Damm
2004-07-16 12:06 ` sanjeev ramachandran
2004-07-16 13:32 ` Dan Malek
2004-07-16 14:06 ` Mark Chambers
2004-07-16 15:42 ` Rune Torgersen
2004-07-16 19:03 ` Dan Malek
2004-07-16 19:02 ` Dan Malek
2004-07-16 13:29 ` Dan Malek
2004-07-16 11:46 ` Dan Malek
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=54144.127.0.0.1.1089973521.squirrel@junkerhq.net \
--to=paguilar@junkerhq.net \
--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).