All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: linuxppc-dev@ozlabs.org,
	LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>
Subject: some (MPC8313) Freescale patches not in latest kernel
Date: Wed, 10 Dec 2008 15:00:56 +0100	[thread overview]
Message-ID: <493FCB98.7000803@aimvalley.nl> (raw)


I'm preparing the latest (2.6.28-rc7) linux kernel for an MPC8313 based project
that's about to start.

Things seems to work great with the base 2.6.28-rc7 kernel. On our MPC8313E-RDB
the kernel boots without problems, ethernet (with eTSEC2/eth1) works and even
eTSEC1/eth0 has a 1gbit link. Most other peripherals seems to work as well, I never
really tried them though.

However, the Freescale MPC8313 BSP (and http://www.bitshrine.org/gpp/) includes a few
patches which I believe I need and/or are useful, for instance:
linux-fsl-2.6.23-MPC8313ERDB-ETSEC27-errata-workaround.patch
linux-fsl-2.6.23-MPC8313ERDB-IEEE-1588.patch
linux-fsl-2.6.23-GIANFAR_PARAMETER_ADJUST.patch
linux-fsl-2.6.23-GIANFAR_SKB_BUFFER_RECYCLING_SUPPORT.patch
linux-fsl-2.6.23-GIANFAR_SKB_BUFFER_RECYCLING_SUPPORT-2.patch

These patches are not in the latest (2.6.28-rc7) linux kernel
nor in any of the powerpc devlopment trees
(e.g. git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git)
Of course users like me can simply check out the patches and apply them
if needed for the project.
Before I do that I would just like to understand why they're not in.
They're not MPC8313(-RDB) specific and they seem very useful to me.

Is it lack of time/importance ?

             reply	other threads:[~2008-12-10 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 14:00 Norbert van Bolhuis [this message]
2008-12-10 16:42 ` some (MPC8313) Freescale patches not in latest kernel 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=493FCB98.7000803@aimvalley.nl \
    --to=nvbolhuis@aimvalley.nl \
    --cc=linuxppc-dev@ozlabs.org \
    --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.