There a couple threads on this list over the past 2 years about the need for device-specific targets for atheros, due to certain manufacturers' differing GPIO assignments for reset, flash CS, etc. I have to apply roughly similar patches to Attitude Adjustment for it to boot correctly on Engenius EOC-1650 and Open Mesh OM1P, albeit each with mutually exclusive GPIO assignments. Looks like FON2201 has its own GPIO assignment for the power LED.
How does one start a new device-specific target for the atheros platform? On Sun, Nov 10, 2013 at 1:13 PM, Daniel Gimpelevich < [email protected]> wrote: > In Backfire, the power LED worked normally on the Fonera+, but in > Barrier Breaker, it's unused. I can't seem to find a way to > differentiate among hardware in the atheros target, so I'm submitting a > "FIXME" patch to be further patched with info from other devices. > > Signed-off-by: Daniel Gimpelevich <[email protected]> > --- /dev/null 2013-11-09 12:36:28.330833697 -0800 > +++ b/target/linux/atheros/base-files/etc/diag.sh 2013-11-10 > 07:34:45.372612754 -0800 > @@ -0,0 +1,27 @@ > +#!/bin/sh > +# Copyright (C) 2013 OpenWrt.org > + > +. /lib/functions/leds.sh > + > +set_state() { > + status_led="gpio4" > + > + [ -d /sys/class/leds/gpio4/ ] && > + [ -d /sys/class/leds/gpio7/ ] && { > + > + case "$1" in > + preinit) > + led_timer "gpio7" 200 200 > + status_led_off > + ;; > + failsafe) > + status_led_blink_failsafe > + led_off "gpio7" > + ;; > + done) > + status_led_on > + led_off "gpio7" > + ;; > + esac > + } > +} > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > -- Ben West http://gowasabi.net [email protected] 314-246-9434
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
