Hi Alex,
What I tried to say that the fix I applied had same logic which was
described by Jay @ Control Module Industries in this discussion. Since I
can not use device tree features of latest kernels, I made the changes
which can fit in kernel 3.2 which is supplied by TI Android code. In my
Well, may be you can add your mdio command inside u-boot source code's
default bootcmd and rebuild the u-boot.
In my case, I updated my cpsw platform data (I use 3.2 kernel, so no device
tree) inside kernel dynamically to fix this problem. It seems to be working
for me.
Regards,
Pratik
On
I also believe the issue mentioned here :
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/366351.aspx is the same
as we are facing in bbb.
Regards,
Pratik
On Monday, 24 November 2014 21:12:50 UTC+5:30, alexschn...@gmail.com wrote:
It appears that the issue is known for a long time: several
Hello,
I am also experiencing the same issue here of etherenet not working on some
boot-ups.
I am using A6C board. My other problem is it is my requirement to use
Android on beaglebone black only from internal storage i.e. eMMC. To
support all necessary functionality of Android 4.2.2, I have
