All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kylo Ginsberg <kylo@kylo.net>
To: linuxppc-embedded@ozlabs.org
Subject: Recommended kernel version/tree for use with MPC8555E?
Date: Tue, 08 Mar 2005 16:01:17 -0800	[thread overview]
Message-ID: <422E3CCD.4020204@kylo.net> (raw)

I've just started working on s/w for an 8555E-based board.  On the 8555E 
I will be using the TSECs (Gigabit ethernet interfaces), DMA engines, 
the security engine, UARTs, DDR and Local Bus controllers and that's 
about it.

Right now I've got an MPC8560ADS eval board to test against.  This board 
came with a 2.4.26-based kernel; it boots ok and runs the basic apps 
fine, however I haven't yet had an opportunity to exercise the wide 
array of functionality on the chip, so I don't know what gotchas or 
porting difficulties I might meet ahead.

Based on that, what kernel version/tree would you recommend?  Should I 
stick with what I've got, move to a ppc-specific 2.4 tree, or jump to 
2.6.x?  Are there performance/features vs. stability tradeoffs I should 
be warned of?

Thanks in advance for any thoughts you may have.

Kylo

             reply	other threads:[~2005-03-09  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  0:01 Kylo Ginsberg [this message]
2005-03-09  0:34 ` Recommended kernel version/tree for use with MPC8555E? Kumar Gala

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=422E3CCD.4020204@kylo.net \
    --to=kylo@kylo.net \
    --cc=linuxppc-embedded@ozlabs.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 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.