From: Wolfgang Denk <wd@denx.de>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel for MPC Lite 5200 will not compile
Date: Thu, 30 Mar 2006 02:34:19 +0200 [thread overview]
Message-ID: <20060330003419.3FF71353A37@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 30 Mar 2006 01:02:00 +0200." <442B11E8.7020107@246tNt.com>
In message <442B11E8.7020107@246tNt.com> you wrote:
>
> It is ?
I think so.
> I don't know about the 2.6-denx, but the stock 2.6.15 should work just fine.
> What's wrong with it ? (except it misses some drivers ... it should compile
> and boot just fine)
Isn't the current reengineered implementation of the BestComm code
based on an very old Freescale version, which has known limitations
and problems?
Or has there any action resulted out of the discussion with the
Freescale engineers, and I have missed it?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
In accord with UNIX philosophy, Perl gives you enough rope to hang
yourself. - L. Wall & R. L. Schwartz, _Programming Perl_
next prev parent reply other threads:[~2006-03-30 0:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:07 Kernel for MPC Lite 5200 will not compile Matthias Fechner
2006-03-28 1:01 ` John Rigby
2006-03-28 9:49 ` Matthias Fechner
2006-03-28 16:15 ` John Rigby
2006-03-28 20:47 ` Sylvain Munaut
2006-03-29 15:32 ` Matthias Fechner
2006-04-01 9:19 ` Matthias Fechner
2006-04-02 17:42 ` Sylvain Munaut
2006-04-02 19:32 ` Matthias Fechner
2006-03-28 22:33 ` Wolfgang Denk
2006-03-29 15:31 ` Matthias Fechner
2006-03-28 22:31 ` Wolfgang Denk
2006-03-29 15:39 ` Matthias Fechner
2006-03-29 20:11 ` Wolfgang Denk
2006-03-29 23:02 ` Sylvain Munaut
2006-03-30 0:34 ` Wolfgang Denk [this message]
2006-03-30 6:36 ` Sylvain Munaut
2006-03-30 16:29 ` John Rigby
2006-03-30 16:39 ` John Rigby
2006-03-30 20:05 ` Dale Farnsworth
2006-03-30 21:51 ` John Rigby
2006-03-30 19:53 ` Dale Farnsworth
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=20060330003419.3FF71353A37@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tnt@246tNt.com \
/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).