From: Matt Porter <mporter@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP baseline test results for v3.7-rc2
Date: Mon, 22 Oct 2012 21:53:46 -0400 [thread overview]
Message-ID: <20121023015346.GB1855@beef> (raw)
In-Reply-To: <50859505.5010306@ti.com>
On Mon, Oct 22, 2012 at 01:48:37PM -0500, Jon Hunter wrote:
>
> On 10/22/2012 01:35 PM, Paul Walmsley wrote:
> > (including the lists in my reply this time, oops; also adding some more
> > detail)
> >
> > On Mon, 22 Oct 2012, Jon Hunter wrote:
> >
> >> On 10/20/2012 04:26 PM, Paul Walmsley wrote:
> >>
> >>> Failing tests: fixed by posted patches
> >>> --------------------------------------
> >>>
> >>> Boot tests:
> >>>
> >>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
> >>> - due to a GPMC bug
> >>> - Apparently fixed by http://www.spinics.net/lists/arm-kernel/msg200787.html
> >>
> >> This is now addressed and I have verified it is booting on v3.7-rc2. The
> >> following patch address this boot problem ...
> >>
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8119024ef7363591fd958ec89ebfaee7c18209e3
> >
> > Great, thanks, will update the README. Did you also enable
> > CONFIG_ARM_APPENDED_DTB and CONFIG_ARM_ATAG_DTB_COMPAT, or were you able
> > to pass the DTB from the bootloader?
>
> Actually, I built u-boot release 2012.10 for the am335x-evm and that
> worked for the bone board too. So that is what I used. I have not
> checked with Vaibhav and team if that is what they are using. So with
> this u-boot I just passed the dtb to the kernel and did not append.
I've mentioned this a few times in various threads...no need to use
appended DTB on a current U-Boot. Some of us are indeed booting this way
with the DTB properly passed separately from the bootloader and chosen
filled out by the bootloader. And yes, am335x_evm_config applies to all
AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all
that is used to determine what board is present so a single
MLO/u-boot.img can be used.
BTW, if you pick up an RS-232 cape, you can avoid using the FTDI->UART0
connection for console and switch to any UART brought out on the Bone
connectors. This is useful for those using a power controller and
console server for local automated testing.
-Matt
WARNING: multiple messages have this Message-ID (diff)
From: mporter@ti.com (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc2
Date: Mon, 22 Oct 2012 21:53:46 -0400 [thread overview]
Message-ID: <20121023015346.GB1855@beef> (raw)
In-Reply-To: <50859505.5010306@ti.com>
On Mon, Oct 22, 2012 at 01:48:37PM -0500, Jon Hunter wrote:
>
> On 10/22/2012 01:35 PM, Paul Walmsley wrote:
> > (including the lists in my reply this time, oops; also adding some more
> > detail)
> >
> > On Mon, 22 Oct 2012, Jon Hunter wrote:
> >
> >> On 10/20/2012 04:26 PM, Paul Walmsley wrote:
> >>
> >>> Failing tests: fixed by posted patches
> >>> --------------------------------------
> >>>
> >>> Boot tests:
> >>>
> >>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
> >>> - due to a GPMC bug
> >>> - Apparently fixed by http://www.spinics.net/lists/arm-kernel/msg200787.html
> >>
> >> This is now addressed and I have verified it is booting on v3.7-rc2. The
> >> following patch address this boot problem ...
> >>
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8119024ef7363591fd958ec89ebfaee7c18209e3
> >
> > Great, thanks, will update the README. Did you also enable
> > CONFIG_ARM_APPENDED_DTB and CONFIG_ARM_ATAG_DTB_COMPAT, or were you able
> > to pass the DTB from the bootloader?
>
> Actually, I built u-boot release 2012.10 for the am335x-evm and that
> worked for the bone board too. So that is what I used. I have not
> checked with Vaibhav and team if that is what they are using. So with
> this u-boot I just passed the dtb to the kernel and did not append.
I've mentioned this a few times in various threads...no need to use
appended DTB on a current U-Boot. Some of us are indeed booting this way
with the DTB properly passed separately from the bootloader and chosen
filled out by the bootloader. And yes, am335x_evm_config applies to all
AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all
that is used to determine what board is present so a single
MLO/u-boot.img can be used.
BTW, if you pick up an RS-232 cape, you can avoid using the FTDI->UART0
connection for console and switch to any UART brought out on the Bone
connectors. This is useful for those using a power controller and
console server for local automated testing.
-Matt
next prev parent reply other threads:[~2012-10-23 1:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 21:26 OMAP baseline test results for v3.7-rc2 Paul Walmsley
2012-10-20 21:26 ` Paul Walmsley
2012-10-21 17:06 ` Paul Walmsley
2012-10-21 17:06 ` Paul Walmsley
2012-10-22 16:10 ` Jon Hunter
2012-10-22 16:10 ` Jon Hunter
2012-10-22 17:17 ` Paul Walmsley
2012-10-22 17:17 ` Paul Walmsley
2012-10-22 17:18 ` Paul Walmsley
2012-10-22 17:18 ` Paul Walmsley
2012-10-22 16:28 ` Jon Hunter
2012-10-22 16:28 ` Jon Hunter
2012-10-22 16:38 ` Tony Lindgren
2012-10-22 16:38 ` Tony Lindgren
2012-10-23 19:34 ` Paul Walmsley
2012-10-23 19:34 ` Paul Walmsley
2012-10-22 18:35 ` Paul Walmsley
2012-10-22 18:35 ` Paul Walmsley
2012-10-22 18:36 ` Paul Walmsley
2012-10-22 18:36 ` Paul Walmsley
2012-10-22 18:50 ` Jon Hunter
2012-10-22 18:50 ` Jon Hunter
2012-10-22 18:48 ` Jon Hunter
2012-10-22 18:48 ` Jon Hunter
2012-10-23 1:53 ` Matt Porter [this message]
2012-10-23 1:53 ` Matt Porter
2012-10-23 3:15 ` Paul Walmsley
2012-10-23 3:15 ` Paul Walmsley
2012-10-23 4:57 ` Paul Walmsley
2012-10-23 4:57 ` Paul Walmsley
2012-10-23 12:24 ` Matt Porter
2012-10-23 12:24 ` Matt Porter
2012-10-23 13:11 ` Matt Porter
2012-10-23 13:11 ` Matt Porter
2012-10-23 21:03 ` Kevin Hilman
2012-10-23 21:03 ` Kevin Hilman
2012-10-23 21:11 ` Matt Porter
2012-10-23 21:11 ` Matt Porter
2012-10-25 14:14 ` Kevin Hilman
2012-10-25 14:14 ` Kevin Hilman
2012-10-23 1:04 ` Kevin Hilman
2012-10-23 1:04 ` Kevin Hilman
2012-10-23 18:19 ` Kevin Hilman
2012-10-23 18:19 ` Kevin Hilman
2012-10-24 9:01 ` Igor Grinberg
2012-10-24 9:01 ` Igor Grinberg
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=20121023015346.GB1855@beef \
--to=mporter@ti.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.