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.
Thanks,
-J
-----cut-----
--- config-pin 2015-09-10 00:01:26.596656005 +0000
+++ config-pin.new 2015-09-10 00:01:49.636656007 +0000
@@ -1,7 +1,7 @@
#!/bin/dash
# Some important directories for use later
-OCPDIR=/sys/devices/ocp.*
+OCPDIR=/sys/devices/ocp
GPIODIR=/sys/class/gpio
SLOTS=/sys/devices/bone_capemgr.*/slots
@@ -801,7 +801,7 @@
check_pin $PIN
# Expand filename using shell globbing
- for FILE in $OCPDIR/${PIN}_pinmux.*/state ; do
+ for FILE in "$OCPDIR/ocp:${PIN}_pinmux/state" ; do
if [ -r $FILE ] ; then
read MODE JUNK < $FILE
else
@@ -870,7 +870,7 @@
# Check whether support for a specific pin is loaded or not
# $1 pin to check
check_pin () {
- if [ -e $OCPDIR/${PIN}_pinmux.* ] ; then
+ if [ -e "$OCPDIR/ocp:${PIN}_pinmux" ] ; then
echo_dbg $1 pinmux file found
else
echo_err $1 pinmux file not found!
@@ -1000,7 +1000,7 @@
fi
# Expand filename using shell globbing
- for FILE in $OCPDIR/${PIN}_pinmux.*/state ; do
+ for FILE in "$OCPDIR/ocp:${PIN}_pinmux/state" ; do
echo_dbg "echo $MODE > $FILE"
sudo -A bash -c "echo $MODE > $FILE" || (echo_err
"Cannot write pinmux file: $FILE" && exit 1)
done
-----cut-----
--
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.
