linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Li Yang" <leoli@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/83xx: Make serial ports work on MPC8315E-RDB w/FSL U-Boots
Date: Mon, 12 Jan 2009 18:20:07 +0100	[thread overview]
Message-ID: <c384c5ea0901120920u7cd349b3te9c57301d204aa55@mail.gmail.com> (raw)
In-Reply-To: <C37C3C8D-0DAA-4174-9A19-E2983CD32380@kernel.crashing.org>

Hello,

On Mon, Jan 12, 2009 at 4:07 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
> On Jan 12, 2009, at 1:55 AM, Li Yang wrote:
>>> -----Original Message-----
>> Freescale BSP is for customer who needs the out-of-box experience.  It's
>> better tested, but doesn't update very frequently.  I would suggest the
>> customer to use the upstream u-boot, if they decide to use latest
>> upstream kernel.
>>
>
The upstream u-boot did however not support PCI Express, which the
latest Freescale kernel did.

So it was a chicken-egg problem experience for people wanting to test
both the latest Freescale kernel as well as Antov's work to bring the
PCI Express support upstream.

Thanks Antov et al,
-- 
Leon

  reply	other threads:[~2009-01-12 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 15:30 [PATCH] powerpc/83xx: Make serial ports work on MPC8315E-RDB w/ FSL U-Boots Anton Vorontsov
2009-01-12  7:55 ` [PATCH] powerpc/83xx: Make serial ports work on MPC8315E-RDB w/FSL U-Boots Li Yang
2009-01-12 15:07   ` Kumar Gala
2009-01-12 17:20     ` Leon Woestenberg [this message]
2009-01-12 18:59       ` Kumar Gala
2009-01-13  5:52     ` Li Yang
2009-01-12 15:10 ` [PATCH] powerpc/83xx: Make serial ports work on MPC8315E-RDB w/ FSL U-Boots 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=c384c5ea0901120920u7cd349b3te9c57301d204aa55@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=leoli@freescale.com \
    --cc=linuxppc-dev@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 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).