From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: avorontsov@ru.mvista.com
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH v2 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E
Date: Wed, 7 Jan 2009 01:40:54 +0100 [thread overview]
Message-ID: <c384c5ea0901061640i54fc8cbg91f970177448f104@mail.gmail.com> (raw)
In-Reply-To: <20090106234256.GA26089@oksana.dev.rtsoft.ru>
Hello Anton,
On Wed, Jan 7, 2009 at 12:42 AM, Anton Vorontsov
<avorontsov@ru.mvista.com> wrote:
> On Tue, Jan 06, 2009 at 11:33:35PM +0100, Leon Woestenberg wrote:
>> So to summarize, we need u-boot to initialize the PCIe controller, in
>> order for Linux to further take it over.
>>
>> What u-boot versions/releases do provide this initialization?
>
> Only FSL U-Boots so far (i.e. community u-boot + fsl patches).
>
Could you be more specific?
I would like to test your Linux kernel patch for 83xx/PCIe mainlining.
What version (and what patches) of u-boot do both initialize pcie
*and* work with recent Linux kernels?
I am aware of the latest MPC8315E BSP (~2008-06), bitshrine.org/gpp/,
the 83xx git tree at denx, and master git.
The first works with 2.6.24, but not with 2.6.25+
The patches at bitshrine are not newer than that.
The tree's are not FSL, or is this the FSL U-Boot you mean?
>> I know the u-boot with the board works, but it's incompatible with
>> recent Linux kernels.
>
> We should fix that (if possible).
>
I was told "just to upgrade u-boot", not what the actual problem was,
although I would like to learn that.
http://www.mail-archive.com/u-boot-users@lists.sourceforge.net/msg06551.html
Basically, this means I am unable to ship a bootloader now, supporting
2.6.24.7 now and 2.6.28 later.
Regards,
--
Leon
next prev parent reply other threads:[~2009-01-07 0:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 16:40 [PATCH 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E Anton Vorontsov
2008-12-30 17:46 ` Kumar Gala
2008-12-30 20:19 ` [PATCH v2 " Anton Vorontsov
2008-12-31 16:48 ` Kumar Gala
2008-12-31 17:10 ` Wolfgang Denk
2009-01-01 14:26 ` Kumar Gala
2009-01-05 17:46 ` Scott Wood
2009-01-05 18:01 ` Anton Vorontsov
2009-01-06 12:18 ` Leon Woestenberg
2009-01-07 15:43 ` Scott Wood
2009-01-06 18:53 ` Leon Woestenberg
2009-01-06 19:27 ` Anton Vorontsov
2009-01-06 20:38 ` Kumar Gala
2009-01-06 21:15 ` Anton Vorontsov
2009-01-06 22:33 ` Leon Woestenberg
2009-01-06 23:42 ` Anton Vorontsov
2009-01-07 0:40 ` Leon Woestenberg [this message]
2008-12-31 17:41 ` Anton Vorontsov
2009-01-01 14:29 ` Kumar Gala
2009-01-05 16:37 ` Anton Vorontsov
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=c384c5ea0901061640i54fc8cbg91f970177448f104@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=wd@denx.de \
/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).