linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Mike Coy <coym@embeddedplanet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 2.3 kernels
Date: Thu, 27 Jul 2000 22:21:49 +0200	[thread overview]
Message-ID: <200007272021.WAA31472@denx.local.net> (raw)
In-Reply-To: Your message of "Thu, 27 Jul 2000 15:01:02 EDT." <4.3.2.7.0.20000727145521.00ae8410@10.0.0.2>


Hi Mike,

in message <4.3.2.7.0.20000727145521.00ae8410@10.0.0.2> you wrote:
>
> I'm trying to get a 2.3 kernel working on an RPX-LITE board.  After a bunch
> of guesswork, I got it to compile.  A good number of hte things I disabled
> can probably be re-enabled now, but that isn't the problem.  It now
> compiles OK, but when I download it to the board and run it, I get no
> output whatsoever.

Do you have any indication  how  far  it  comes?  Do  you  have  kgdb
working, or a good BDM debugger (i. e. one with MMU support)?

> Has anyone successfully ran a 2.3 kernel on one of these boards?

It depends on what you mean with 2.3; it's just two days that I  have
2.4.0-test5  running  stable  on  TQM8xxL boards. This is the _first_
kernel after 2.3.18 that ever ran for me on a MPC8xx. And  even  this
is  only  when  you  fix cache problems in string.S (either by simply
replacing the file with the version from 2.2.13, or by applying Dan's
patch).

Sorry, I don't have any RPX boards here to test, but  I  have  tested
three  systems  (2  x 850 and a 860), two of them under > 24 h stress
tests (with things like compiling the linux kernel  on  the  target),
and I had not a single problem since.

In  case  you're  interested  -  I've  put  my  patches  against  the
2.4.0-test5  BitKeeper  sources on our FTP server (the "COMMON" patch
includes all I neded to change for TQM8xxL  support  to  the  current
kernel;  the "TQM" patch is probably of little interest since this is
just needed when you use the old TQ monitor instead of PPCBOOT):

ftp://ftp.denx.de/pub/LinuxPPC/usr/src/patches/COMMON-2.4.0-test5.patch.gz
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/patches/TQM-2.4.0-test5.patch.gz

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Real programmers don't comment their code. It was hard to  write,  it
should be hard to understand.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-07-27 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27 19:01 2.3 kernels Mike Coy
2000-07-27 20:21 ` Wolfgang Denk [this message]

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=200007272021.WAA31472@denx.local.net \
    --to=wd@denx.de \
    --cc=coym@embeddedplanet.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).