All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theo Gjaltema <gjalt007@chello.nl>
To: Stephen Williams <steve@icarus.com>,  linuxppc-embedded@ozlabs.org
Subject: Re: Choices of 2.4 Kernel for PPC
Date: Sun, 03 Sep 2006 13:07:03 +0200	[thread overview]
Message-ID: <44FAB757.3000801@chello.nl> (raw)
In-Reply-To: <e2b1fi$klf$1@sea.gmane.org>

Stephen Williams schreef:
> I'd been using the BK tree (I know, old old) but it's been stable
> for me for a while. But I'm starting to see so problems and I want
> to work with a recent kernel tree. I'm using a PPC405GPr processor.
>
> I downloaded the linux-2.4.32 tree from kernel.org, but it has
> none of the Xilinx stuff so I immediately wonder about other things
> it lacks for embedded PPC.
>
> I downloaded the linux 2.4 .git tree from Denx, but the makefile
> in top says it's based on 2.4.25, which is even older then what
> I've got now.
>
> I've looked on the penguinppc.org page, but it points me back
> to the kernel.org distribution and possibly the bk repository.
> Hmm...
>
> So what tree is most universally accepted as current so far as
> embedded PPC goes? And can the penguinppc.org pages be updated
> to reflect the consensus?
>   
I've run into the same problems with the kernel.org version of the linux 
kernel 2.4.32.
the fec_enet module for the ppc was 0.3 instead of 0.4 (denx 2.4.25) and 
the config.in file did not contain any of the physical driver info.
Apart from this the generated kernel crashed when accessing the flash, 
this worked fine in the denx 2.4.25 kernel as well.
We decided that the kernel.org 2.4.32 is not suitable for the ppc and 
stick to the 2.4.25 version as present in the ELDK3.1.1.

Succes,
   Theo Gjaltema.

      reply	other threads:[~2006-09-03 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 16:32 Choices of 2.4 Kernel for PPC Stephen Williams
2006-09-03 11:07 ` Theo Gjaltema [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=44FAB757.3000801@chello.nl \
    --to=gjalt007@chello.nl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=steve@icarus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.