linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Thomas Maenner <tmaenner@aehr.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19
Date: Sun, 25 Mar 2007 21:35:24 +0200	[thread overview]
Message-ID: <20070325193524.824BC35264E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 23 Mar 2007 10:29:04 MST." <200703231029.04488.tmaenner@aehr.com>

In message <200703231029.04488.tmaenner@aehr.com> you wrote:
> 
> please enlighten us (or maybe just me) on why the TQ8xx are not supported by 
> 2.6, since the ppc sources are in the 2.6.19 kernel source tree, that comes 
> with ELDK 4.1

The working 2.4 code was copied to 2.5 and later to 2.6 without  ever
being  actively maintained. In early 2.6 kernels, support for 8xx was
more or less broken. Lately, it has become clear that ARCH=ppc  is  a
dead end and things should move to ARCH=powerpc. That's why I said we
(DENX) will not support the 8xx in the ARCH=ppc context.

Last but not least I would like to remind you that 2.6 is bigger and
slower than 2.4, which is especially visible on low end systems like
the 8xx.

The kernel code that comes with the ELDK is very close to the vanilla
kernel.org tree (plus some local extensions that have  not  yet  been
pushed  upstream).  The  8xx  support  in  both  trees  is absolutely
identical, i. e. the fact that 8xx code is in the ELDK has  the  very
same reason why x86 code is there, or why sh4 or etrax or ... code is
theee,  even  if these systems are not supported by the ELDK at all -
this code is part of the vanilla kernel.org tree.

AFAIK, 2.6 has never been fully ported to  the  TQM8xxL  and  TQM8xxM
systems yet.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Computers are not intelligent.  They only think they are.

  reply	other threads:[~2007-03-25 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  3:44 TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19 Thomas Maenner
2007-03-22  7:40 ` Wolfgang Denk
2007-03-22 15:01   ` Thomas Maenner
2007-03-22 21:10     ` Thomas Maenner
2007-03-22 21:26       ` Wolfgang Denk
2007-03-23 11:19         ` Ralph Hempel
2007-03-23 13:27           ` Wolfgang Denk
2007-03-23 17:29             ` Thomas Maenner
2007-03-25 19:35               ` Wolfgang Denk [this message]
2007-03-23 17:26         ` Thomas Maenner

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=20070325193524.824BC35264E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tmaenner@aehr.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).