is the tilcdc part correct?

W dniu 2014-11-24 o 21:36, Robert Nelson pisze:
On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl <breme...@gmail.com> wrote:
This is the output on debug serial now:

.
.
.Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.338981] omap2_mbox_probe: platform not supported
[    0.493971] tps65217-bl tps65217-bl: no platform data provided
[    0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found
[    0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
failed
[    0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[    0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22
[    0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single
Loading, please wait...
systemd-fsck[205]: rootfs: clean, 21581/111104 files, 122520/444160 blocks
systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters
[    6.507830] tilcdc 4830e000.fb: no encoders/connectors found
[    6.513806] tilcdc 4830e000.fb: failed to initialize mode setting

There is still no visual. It says:
... tilcdc..
Does that mean hes not using the driver for tfp410?
Also, could you please confirm either the I2C2 in the tree overlay is the
I2C2 on the header? I am still not certain.
Verfiy:
https://github.com/derekmolloy/boneDeviceTree/tree/master/docs

Regards,


--
Bremenpl

--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to