On 22/01/13 02:24, Paul Walmsley wrote:
Hi guys,
Regarding the AM33xx test failures with appended DTBs, it would be very
helpful if especially the TI people could try reproducing the problem.
My non-working setup (I'm using a recent U-Boot) is as follows ...
[Note that the DTB patch
On 22/01/13 12:21, Peter Korsgaard wrote:
Mark == Mark Jackson mpfj-l...@mimc.co.uk writes:
Hi,
Mark Bytes transferred = 3963919 (3c7c0f hex)
Mark ## Booting kernel from Legacy Image at 8000 ...
MarkImage Name: Linux
MarkImage Type: ARM Linux Kernel Image
On 22/01/13 13:32, Bedia, Vaibhav wrote:
snip
Following works for me:
Kernel
===
git checkout next-20130122
make distclean
make omap2plus_defconfig
Enable the appended DTB related options via menuconfig
make -j7
cat arch/arm/boot/zImage arch/arm/boot/dts/am335x-bone.dtb
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
On 06/11/12 09:47, Mark Jackson wrote:
On 06/11/12 06:16, Hiremath, Vaibhav wrote:
Where is your DTB? Is it appended to Kernel image?
Can you try below sequence/commands from u-boot?
mmc rescan 0
fatload mmc 0 8000 am335x-bone.dtb
fatload mmc 0 8100 uImage
setenv bootargs console
On 13/11/12 15:35, Paul Walmsley wrote:
instead of this:
$ cat arch/arm/boot/uImage arch/arm/boot/am335x-bone.dtb
arch/arm/boot/uImage-dtb.am335x-bone
$ cp arch/arm/boot/uImage-dtb.am335x-bone /media/boot/uImage
something like this is what you need to do instead:
$ cat
On 06/11/12 06:16, Hiremath, Vaibhav wrote:
Where is your DTB? Is it appended to Kernel image?
Can you try below sequence/commands from u-boot?
mmc rescan 0
fatload mmc 0 8000 am335x-bone.dtb
fatload mmc 0 8100 uImage
setenv bootargs console=ttyO0,115200n8 mem=256M
On 31/10/12 13:57, Hiremath, Vaibhav wrote:
On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
On 30/10/12 14:48, Vaibhav Hiremath wrote:
Okay, so I'm now coming up against a brick wall regarding U-Boot.
The Kernel boots fine (as per the tree + patch above) provided I build
U-Boot using
On 31/10/12 14:24, Mark Jackson wrote:
On 31/10/12 13:57, Hiremath, Vaibhav wrote:
On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
If I try the latest mainline U-Boot (or the TI branch), I just get to
Starting kernel ... and then
hangs.
I am using Mainline u-boot and it works
On 30/10/12 14:48, Vaibhav Hiremath wrote:
On 10/30/2012 6:09 PM, Hiremath, Vaibhav wrote:
Mark,
MMC is dependent on EDMA-DMA conversion patches from Matt, which he has
already submitted to the list recently. So MMC support will come along with
EDMA support. DMA-EDMA patches are
On 31/10/12 13:57, Hiremath, Vaibhav wrote:
On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
If I try the latest mainline U-Boot (or the TI branch), I just get to
Starting kernel ... and then
hangs.
I am using Mainline u-boot and it works for me. Can you paste u-boot boot
log
anyone testing a new
kernel will probably expect the same setup to work.
Cheers
Mark JACKSON
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
such as gpmc_cs_request() ?
Is there a method to delay my test code, or maybe get the omap-gpmc registered
earlier ?
Cheers
Mark JACKSON
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On 24/09/12 12:13, Mohammed, Afzal wrote:
Hi Mark,
On Mon, Sep 24, 2012 at 16:21:40, Mark Jackson wrote:
On 24/09/12 05:51, Mohammed, Afzal wrote:
It seems you are using PSP Kernel.
Invoking omap_init_gpmc before gpmc request should help.
Okay ... I'm now using earlyprintk
?
Cheers
Mark JACKSON
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
this delay be removed ?
My total boot time is only 1.3sec, so a 0.5sec delay is quite significant !?!
Below is the first portion of my boot log.
Thanks for any advice
Mark JACKSON
---
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.28+ (mpfj@mpfj-nanobone) (gcc version 4.5.4
On 18/09/12 11:40, Mark Jackson wrote:
I'm using a BeagleBone, and the linux kernel from Koen Kooi
(https://github.com/koenkooi/linux.git).
I have noticed there is a 0.5sec delay between OMAP UART0 being initialised
and the console being
enabled.
It is, of course, when the printk
On 29/06/12 18:56, Hiremath, Vaibhav wrote:
On Fri, Jun 29, 2012 at 19:50:45, Mark Jackson wrote:
This does appear to work using the ramdisk, but there seems to be no support
for booting off MMC.
This is known thing and clearly mentioned/highlighted above.
Use the ramdisk image to boot
in ?
Cheers
Mark Jackson
[1] https://github.com/koenkooi/linux
[2] http://processors.wiki.ti.com/index.php/Sitara_Linux_Upstream_Status
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Running 2.6.38 on my beagleboard, I can boot using nfs:-
regulator_init_complete: VDVI: incomplete constraints, leaving on
regulator_init_complete: VDAC: incomplete constraints, leaving on
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: host does not support reading
101 - 120 of 120 matches
Mail list logo
