Finally able to verify with a lucid -> Maverick upgrade test.
Everything works.
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://bugs.launchpad.net/bugs/608266
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package linux - 2.6.35-16.22
---
linux (2.6.35-16.22) maverick; urgency=low
[ Andy Whitcroft ]
* debian -- more agressivly clean up after depmod on purge
- LP: #618591
[ Henrik Rydberg ]
* SAUCE: hid: 3m: Simplify touchsreen emulation logic
** Also affects: linux (Ubuntu Maverick)
Importance: Medium
Assignee: Mathieu Poirier (mathieu.poirier)
Status: Fix Committed
** Changed in: linux (Ubuntu Maverick)
Milestone: None => ubuntu-10.10-beta
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://
The problem came from the gpmc not being initialized before accessing
the nand flash. Gpmc and the nand flash driver were decoupled after
Lucid and the change was not reflected in "omap3beagle_flash_init".
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
[regression]
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.
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://bugs.launchpad.net/bugs/608266
You rece
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://bugs.launchpad.net/bugs/608266
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
