From: mpfj-list@mimc•co.uk (Mark Jackson)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.8-rc4
Date: Mon, 21 Jan 2013 16:32:13 +0000 [thread overview]
Message-ID: <50FD6D8D.6030106@mimc.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1301202136290.31667@utopia.booyaka.com>
Vaibhav / Matt
On 20/01/13 21:38, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.8-rc4.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.8-rc4/20130120122039/
<snip>
> Failing tests: needing investigation
> ------------------------------------
>
> Boot tests:
>
> * am335xbone: hangs after "Starting kernel"
> - Cause unknown
> - http://www.mail-archive.com/linux-omap at vger.kernel.org/msg82297.html
<snip>
> Failing tests: needing local investigation (may be due to testbed issues)
> -------------------------------------------------------------------------
>
> Boot tests:
>
> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
> - May be fixed now, pending retest:
> - http://marc.info/?l=linux-omap&m=135082257727502&w=2
> - Not yet part of the automated test suite
> - Nishanth Menon & Vaibhav Hiremath report that it works for them
> * May be due to an old U-boot with FDT support problems used here?
> Pending local investigation and re-test
Does anyone know when the BeagleBone support is going to be fixed in mainline ?
I've just tried the latest linux-next git, and no joy.
However, Matt's edma-dmaengine-am33xx-v5 branch on github seems to be working:-
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.8.0-rc3-61978-g108da76-dirty (mpfj at mpfj-nanobone) (gcc version 4.5.4
(Buildroot 2012.11-git-00497-ge48bf89) ) #7 SMP Mon Jan 21 15:52:14 GMT 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
Are we just waiting for Matt's DMA stuff to be accepted ?
Cheers
Mark J.
next prev parent reply other threads:[~2013-01-21 16:32 UTC|newest]
Thread overview: 32+ 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-21 16:32 ` Mark Jackson [this message]
2013-01-21 16:45 ` Nishanth Menon
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:34 ` Richard Cochran
2013-01-21 20:36 ` Peter Korsgaard
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:40 ` Peter Korsgaard
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 12:19 ` Peter Korsgaard
2013-01-25 8:23 ` Paul Walmsley
2013-01-22 10:15 ` Mark Jackson
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:39 ` Mark Jackson
2013-01-22 18:23 ` Tony Lindgren
2013-01-23 10:18 ` Mark Jackson
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-25 16:59 ` Tony Lindgren
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-25 8:42 ` Paul Walmsley
2013-02-06 22:00 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-07 14:42 ` Bedia, Vaibhav
[not found] ` <49ca66a84bb245ca9cfe4fd044c4d6f6@DFLE72.ent.ti.com>
2013-01-21 17:10 ` Matt Porter
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=50FD6D8D.6030106@mimc.co.uk \
--to=mpfj-list@mimc$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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