Op 14 nov 2008, om 11:56 heeft Koen Kooi het volgende geschreven:
Op 14 nov 2008, om 11:17 heeft Koen Kooi het volgende geschreven:Hi,I updated to the current head (5ecf98b76fa95078277c9037bb01640fd3de5e2c) and get this on boot (with debug_ll) on omap3evm:<7>omap-dss DISPLAY: panel 'panel-dvi' registered <6>Serial: 8250/16550 driver4 ports, IRQ sharing enabled <6>serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654<....,...:4...4../0400..1=......F1.5S.<....,...:4.3^F!^C../ 0.0^F00..1=7K....F1.5S.<.....%;..&=%.".$.<."F:..5. .!*$.<...0^G.. 5. .!*$.<...%^B-J/.0.."..%C0^G...5(V6..!^C0.^D000)^V.6...%C0^G%C%. %^C!"2^G.."...$...&R...%C0^G...8).% ..'%:%.#. ...,.<.!.74^C3..:..#.#V%...1.V..<.).5...v8. {...$.r. 3...6......Any ideas?I get this on rc3 now as well, it seems that the evm dss2 patch has some side effects, console is restored when userspace launches getty
I can boot rc4 + dss2 + dss2-evm into userspace if the omap_rev() TWL writes don't get triggered in board-omap3evm.c. Once those get run I get more garbage and a crash, without them a little garbage that getty fixes up.
regards, Koen
Attachment:
PGP.sig
Description: This is a digitally signed message part
