From: Thierry Bultel <tbultel@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: mx6: Disable PCIe on SABRE Lite/Nitrogen6x
Date: Sat, 22 Mar 2014 21:50:52 +0100 [thread overview]
Message-ID: <532DF7AC.1000801@free.fr> (raw)
In-Reply-To: <201403221926.41815.marex@denx.de>
When I communicated about the bug I had,
and said that my temporary workaround was to disable the PCIe,
my intention was not to make the suppression become a standard,
and I believe it is a little bit frustrating for Marek.
The AMOS820, based on the sabrelite/nitrogen has a PCIe slot on the main
board,
so there might be some interest of having the PCIe support enabled.
To my mind, the bug is in the kernel I am using, it should be robust
to the fact that PCIe has been formerly probed.
Wouldn't that be smarter to have the PCIe enabled or not,
by an environment variable (defaulted to YES, and that the user could
set to NO eventually for older kernels) ?
Best regards
Thierry
Le 22/03/2014 19:26, Marek Vasut a ?crit :
> On Saturday, March 22, 2014 at 04:17:09 PM, Eric Nelson wrote:
>> Use of PCIe on SABRE Lite and Nitrogen6x boards
>> is atypical and requires the use of custom daughter
>> boards.
>>
>> Use in U-Boot is even rarer, so this patch removes it from
>> the standard configuration.
>>
>> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
> :-(
>
> Acked-by: Marek Vasut <marex@denx.de>
>
> Best regards,
> Marek Vasut
next prev parent reply other threads:[~2014-03-22 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 11:28 [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0 tbultel at free.fr
2014-03-18 12:34 ` Stefano Babic
2014-03-21 18:47 ` Thierry Bultel
2014-03-21 22:50 ` Eric Nelson
2014-03-22 1:33 ` Marek Vasut
2014-03-22 15:13 ` Eric Nelson
2014-03-22 15:17 ` [U-Boot] [PATCH] ARM: mx6: Disable PCIe on SABRE Lite/Nitrogen6x Eric Nelson
2014-03-22 18:26 ` Marek Vasut
2014-03-22 20:50 ` Thierry Bultel [this message]
2014-03-22 21:49 ` Eric Nelson
2014-03-23 0:15 ` Marek Vasut
2014-03-23 0:11 ` Marek Vasut
2014-03-23 16:50 ` Stefano Babic
2014-03-23 16:48 ` Stefano Babic
2014-04-01 8:17 ` Stefano Babic
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=532DF7AC.1000801@free.fr \
--to=tbultel@free.fr \
--cc=u-boot@lists.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 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.