Flashing OMAP4 kernel uses the wrong partition on Blaze

Bug #640406 reported by Nicolas Dechesne
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jasper-initramfs (Ubuntu)
Fix Released
Medium
Oliver Grawert

Bug Description

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

Tags: armel
Oliver Grawert (ogra)
Changed in jasper-initramfs (Ubuntu):
status: New → Confirmed
assignee: nobody → Oliver Grawert (ogra)
importance: Undecided → Medium
milestone: none → ubuntu-10.10
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jasper-initramfs - 0.25

---------------
jasper-initramfs (0.25) maverick; urgency=low

  * make sure we use the right partition for booting when running from SD on
    OMAP4 blaze (LP: #640406)
 -- Oliver Grawert <email address hidden> Thu, 16 Sep 2010 18:27:07 +0200

Changed in jasper-initramfs (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.