tiomap-dev team mailing list archive

Thread
Date

[Bug 640406] [NEW] Flashing OMAP4 kernel uses the wrong partition on Blaze

To: tiomap-dev@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <640406@xxxxxxxxxxxxxxxxxx>
Date: Thu, 16 Sep 2010 11:55:24 -0000
Reply-to: Bug 640406 <640406@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

You have been subscribed to a public bug by Nicolas Dechesne (ndec):

When flash_kernel runs on blaze, it flashes in /dev/mmcblk0p1 (as per
flash_kernel.conf). however on blaze mmcblk0 is the device name for the
eMMC, not the SD card.

also in the image, the initial boot.scr has mmcblk0 hard coded, so it
needs to be documented that this must be changed when booted on blaze.

blaze and panda are different machines at kernel level. on blaze
/proc/cpuinfo contains:L

$ cat /proc/cpuinfo 
Processor	: ARMv7 Processor rev 1 (v7l)
processor	: 0

<snip>

Hardware	: OMAP4430 4430SDP board
Revision	: 0010
Serial		: 0000000000000000

** Affects: jasper-initramfs (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: armel
-- 
Flashing OMAP4 kernel uses the wrong partition on Blaze
https://bugs.launchpad.net/bugs/640406
You received this bug notification because you are a member of TI OMAP Developers, which is a direct subscriber.