On 01/10/2014 04:11 PM, Robert Nelson wrote:
OK I registered, but awaiting approval. In the meantime, I got the following:It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;)First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases
Uncompressing Linux... done, booting the kernel. [ 0.369399] omap2_mbox_probe: platform not supported [ 0.526579] tps65217-bl tps65217-bl: no platform data provided [ 0.591595] bone-capemgr bone_capemgr.9: slot #0: No cape found [ 0.628702] bone-capemgr bone_capemgr.9: slot #1: No cape found [ 0.665810] bone-capemgr bone_capemgr.9: slot #2: No cape found [ 0.702918] bone-capemgr bone_capemgr.9: slot #3: No cape found[ 0.718940] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.728585] bone-capemgr bone_capemgr.9: slot #6: Failed verification[ 0.735360] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 0.752808] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [ 0.814570] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [ 0.826308] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [ 0.833623] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
Don't know whether this is a bug or not, but I am also a bit confused as I thought the capemgr was not yet in 3.13....?
Dave. -- For more options, visit http://beagleboard.org/discuss--- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
<<attachment: dave.vcf>>
