Currently it seems that the only bug that's blocking xM is bug 613855. With that fixed xM will probably work fine.
If you want to test I generated a kernel at http://people.canonical.com/~rsalveti/maverick/kernel/linux-image-2.6.35-19-omap_2.6.35-19.25rsalveti1_armel.deb with the proposed fix for bug 613855. With this kernel it seems that everything works fine, besides a kernel trace that shouldn't affect much: [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: at /home/ubuntu/kernel/ubuntu-maverick/arch/arm/mach-omap2/serial.c:727 omap_serial_init_port+0x88/0x1f8() [ 0.000000] (null): can't init uart3, no clocks available [ 0.000000] Modules linked in: [ 0.000000] [<c004c438>] (unwind_backtrace+0x0/0x100) from [<c051334c>] (dump_stack+0x18/0x1c) [ 0.000000] [<c051334c>] (dump_stack+0x18/0x1c) from [<c0081a78>] (warn_slowpath_common+0x5c/0x6c) [ 0.000000] [<c0081a78>] (warn_slowpath_common+0x5c/0x6c) from [<c0081b2c>] (warn_slowpath_fmt+0x38/0x40) [ 0.000000] [<c0081b2c>] (warn_slowpath_fmt+0x38/0x40) from [<c0010814>] (omap_serial_init_port+0x88/0x1f8) [ 0.000000] [<c0010814>] (omap_serial_init_port+0x88/0x1f8) from [<c00109b4>] (omap_serial_init+0x30/0x3c) [ 0.000000] [<c00109b4>] (omap_serial_init+0x30/0x3c) from [<c00125e0>] (omap3_beagle_init+0x6c/0xfc) [ 0.000000] [<c00125e0>] (omap3_beagle_init+0x6c/0xfc) from [<c000c660>] (customize_machine+0x24/0x2c) [ 0.000000] [<c000c660>] (customize_machine+0x24/0x2c) from [<c00443bc>] (do_one_initcall+0x3c/0x1dc) [ 0.000000] [<c00443bc>] (do_one_initcall+0x3c/0x1dc) from [<c00085b4>] (do_basic_setup+0x64/0x74) [ 0.000000] [<c00085b4>] (do_basic_setup+0x64/0x74) from [<c0008654>] (kernel_init+0x90/0x120) [ 0.000000] [<c0008654>] (kernel_init+0x90/0x120) from [<c0045af4>] (kernel_thread_exit+0x0/0x8) [ 0.000000] ---[ end trace da227214a82491b7 ]--- Note: as my xM (P8) has memory issues, I need to boot it with mem=256M. -- [Maverick] omap flavour does not work on beagle XM board https://bugs.launchpad.net/bugs/589624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
