[regression] no more /dev/mtdblock devices on omap3 in maverick
Bug #608266 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Maverick |
Fix Released
|
Medium
|
Unassigned |
Bug Description
in lucid we had /dev/mtdblock devices on omap3, we need these if NAND exists on the HW to modify the bootloader defaults from userspace, please enable NAND support again in maverick.
Changed in linux (Ubuntu): | |
assignee: | nobody → Mathieu Poirier (mathieu.poirier) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu Maverick): | |
milestone: | none → ubuntu-10.10-beta |
To post a comment you must log in.
The driver is compiled in but the flash start address is not properly set. Initialization of mtd device changed between Lucid and Maverick. Base address seems to have been left out.