From: Richard Cochran <richardcochran@gmail.com>
To: Matt Porter <mporter@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
Mark Jackson <mpfj-list@mimc.co.uk>,
Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>
Subject: Re: OMAP baseline test results for v3.8-rc4
Date: Mon, 21 Jan 2013 19:34:51 +0100 [thread overview]
Message-ID: <20130121183451.GD2342@netboy.at.omicron.at> (raw)
In-Reply-To: <20130121182419.GE10020@beef>
On Mon, Jan 21, 2013 at 01:24:19PM -0500, Matt Porter wrote:
> On Mon, Jan 21, 2013 at 06:20:03PM +0000, Richard Cochran wrote:
> > On Mon, Jan 21, 2013 at 10:45:10AM -0600, Nishanth Menon wrote:
> > > for MMC filesystem - we need the edma series. for a ramdisk, I am able
> > > to boot up to shell with 3.8-rc4 tag
> >
> > Yep, I also could boot 3.8-rc3 using ramfs, no problem.
>
> Do you use appended dtb? The only different that jumped out at me first
> Paul's reported hang is he uses appended dtb and I boot my boards with a
> single uImage and multiple dtbs the traditional DT way.
No, not appended. I have a u-boot that supports dtb:
U-Boot SPL 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)
U-Boot 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)
and using the omap2plus_defconfig, with a minicom script like the one
below, and it works just fine.
HTH,
Richard
verbose on
send setenv ipaddr 192.168.1.77
send setenv serverip 192.168.1.12
send setenv netmask 255.255.255.0
send setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x82000000,16MB ramdisk_size=16384 earlyprintk=serial
send tftp 81000000 uImage
expect {
"U-Boot# "
}
send tftp 82000000 beaglebone-initrd.gz
expect {
"U-Boot# "
}
send tftp 80000000 am335x-bone.dtb
expect {
"U-Boot# "
}
send bootm 81000000 - 80000000
WARNING: multiple messages have this Message-ID (diff)
From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.8-rc4
Date: Mon, 21 Jan 2013 19:34:51 +0100 [thread overview]
Message-ID: <20130121183451.GD2342@netboy.at.omicron.at> (raw)
In-Reply-To: <20130121182419.GE10020@beef>
On Mon, Jan 21, 2013 at 01:24:19PM -0500, Matt Porter wrote:
> On Mon, Jan 21, 2013 at 06:20:03PM +0000, Richard Cochran wrote:
> > On Mon, Jan 21, 2013 at 10:45:10AM -0600, Nishanth Menon wrote:
> > > for MMC filesystem - we need the edma series. for a ramdisk, I am able
> > > to boot up to shell with 3.8-rc4 tag
> >
> > Yep, I also could boot 3.8-rc3 using ramfs, no problem.
>
> Do you use appended dtb? The only different that jumped out at me first
> Paul's reported hang is he uses appended dtb and I boot my boards with a
> single uImage and multiple dtbs the traditional DT way.
No, not appended. I have a u-boot that supports dtb:
U-Boot SPL 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)
U-Boot 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)
and using the omap2plus_defconfig, with a minicom script like the one
below, and it works just fine.
HTH,
Richard
verbose on
send setenv ipaddr 192.168.1.77
send setenv serverip 192.168.1.12
send setenv netmask 255.255.255.0
send setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x82000000,16MB ramdisk_size=16384 earlyprintk=serial
send tftp 81000000 uImage
expect {
"U-Boot# "
}
send tftp 82000000 beaglebone-initrd.gz
expect {
"U-Boot# "
}
send tftp 80000000 am335x-bone.dtb
expect {
"U-Boot# "
}
send bootm 81000000 - 80000000
next prev parent reply other threads:[~2013-01-21 18:35 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 21:38 OMAP baseline test results for v3.8-rc4 Paul Walmsley
2013-01-20 21:38 ` Paul Walmsley
2013-01-21 16:32 ` Mark Jackson
2013-01-21 16:32 ` Mark Jackson
2013-01-21 16:45 ` Nishanth Menon
2013-01-21 16:45 ` Nishanth Menon
2013-01-21 18:20 ` Richard Cochran
2013-01-21 18:20 ` Richard Cochran
[not found] ` <f36acfaf128c4844b8f696ea4440e253@DLEE74.ent.ti.com>
2013-01-21 18:24 ` Matt Porter
2013-01-21 18:24 ` Matt Porter
2013-01-21 18:34 ` Richard Cochran [this message]
2013-01-21 18:34 ` Richard Cochran
2013-01-21 20:36 ` Peter Korsgaard
2013-01-21 20:36 ` Peter Korsgaard
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:40 ` Peter Korsgaard
2013-01-22 9:40 ` Peter Korsgaard
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 12:19 ` Peter Korsgaard
2013-01-22 12:19 ` Peter Korsgaard
2013-01-25 8:23 ` Paul Walmsley
2013-01-25 8:23 ` Paul Walmsley
2013-01-22 10:15 ` Mark Jackson
2013-01-22 10:15 ` Mark Jackson
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:39 ` Mark Jackson
2013-01-22 13:39 ` Mark Jackson
2013-01-22 18:23 ` Tony Lindgren
2013-01-22 18:23 ` Tony Lindgren
2013-01-23 10:18 ` Mark Jackson
2013-01-23 10:18 ` Mark Jackson
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-25 16:59 ` Tony Lindgren
2013-01-25 16:59 ` Tony Lindgren
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-25 8:42 ` Paul Walmsley
2013-01-25 8:42 ` Paul Walmsley
2013-02-06 22:00 ` Paul Walmsley
2013-02-06 22:00 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-07 14:42 ` Bedia, Vaibhav
2013-02-07 14:42 ` Bedia, Vaibhav
[not found] ` <49ca66a84bb245ca9cfe4fd044c4d6f6@DFLE72.ent.ti.com>
2013-01-21 17:10 ` Matt Porter
2013-01-21 17:10 ` Matt Porter
2013-01-21 20:36 ` Peter Korsgaard
2013-01-21 20:36 ` Peter Korsgaard
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=20130121183451.GD2342@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj-list@mimc.co.uk \
--cc=mporter@ti.com \
--cc=nm@ti.com \
--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.