Are you using an LCD cape? I have seen flickering similar to what you 
described with the 3.8 kernel when I forced a video resolution via the 
"video=" kernel command line option (in uEnv.txt in the boot partition) for 
the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems. 
For those display capes, the resolution is pulled from the device tree 
overlay for the cape automatically, so you should not specify a video 
resolution. If you are using HDMI, you may not be getting the proper EDID 
resolution information from your display. In that case, the TILCDC driver 
will default to 1024x768, which your display (if it is an HDMI display) may 
not properly support. Either way, I have seen that refresh problem when the 
logical resolution that the TILCDC driver expects mismatches the physical 
resolution of your display device.

I have not seen that particular USB error before, but I also have not 
worked with the 3.10 kernel on the BBB. I've gone straight from 3.8 to 
3.13/14.

Andrew 

On Tuesday, March 17, 2015 at 4:45:42 PM UTC-4, Michael Gobbers wrote:
>
> Hi Andrew,
>
> Thanks for the reply. Indeed Keith Conger supplied me with the patches. 
> I have gotten a bit further now as I'm getting the hand of configuring and 
> building the kernel for the beaglebone black. I'm now able to boot all the 
> way to the android home screen.
>
> However, I have major graphical glitches. It seems that the boot animation 
> is being displayed together with the home screen. Their also seemed to be a 
> lot of flickering on the screen. So there is something seriously wrong 
> there.
>
> The biggest issue for me that I came across was the fact that my usb host 
> port didn't seem to work. So no mouse available there.
> Today I tried the 3.10 kernel and there I do not have the graphical 
> glitches. However, again there is no host port available.
>
> from the ftdi output I did find the following while booting the kernel:
>
> [    2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with 
> status -517
>
> [    2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe 
> deferral
>
> Have you ever come across this error?
>

-- 
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/d/optout.

Reply via email to