Hi Charles, RCN, 

I've got the 4.1.10-armv7-rt-x5 kernel running on my bbb; switched over to 
this version to avoid the ethernet 0xfffffffb detection problem (and to 
monopolize the CPU for 7-10ms).  Fixed, and capemgr seems installed 
properly per https://github.com/RobertCNelson/bb.org-overlays, but the 
pinmux state files are absent.  Have they moved?  Must the pinmuxes be 
programmed in some other way? 

e.g. 
> ls /sys/devices/platform/ocp/ocp:P8_07_pinmux
driver_override modalias of_node power subsystem uevent

No 'state' file as needed by config-pin (which includes the recent 
patches).  Should I move back to an older or different kernel? 

appreciated, 
Tim

On Thursday, September 10, 2015 at 6:23:36 AM UTC-7, Charles Steinkuehler 
wrote:
>
> On 9/9/2015 7:17 PM, [email protected] <javascript:> wrote: 
> > Hi Charles, 
> > 
> > No experience with how patches should be introduced, but below is a 
> patch 
> > for config-pin on linux 3.14.51 
> > Hope this helps someone. 
> > 
> > md5sum of the original config pin: 74a71c0a84c46d2df4e14113dea4834a 
> > 
> > The problem was related to changes in how the /sys/ files are named. 
> > Tried 4.1.x a couple weeks back and it was rebooting spontaneously for 
> me. 
> > The 3.14 kernel has been stable for me so far. 
>
> <snip code patch> 
>
> Thanks for the patch, I'm glad it was a simple fix for you. 
>
> The code provided may work for 3.14, but will break other kernel 
> versions.  I'll see if I can fold in an update that will do the proper 
> thing based on detecting the kernel verison so the code won't break on 
> the 3.8 kernels still used by lots of folks (including me). 
>
> -- 
> Charles Steinkuehler 
> [email protected] <javascript:> 
>

-- 
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