2015-11-08 13:07 GMT+01:00 Russell Senior <[email protected]>: >>>>>> "Felix" == Felix Fietkau <[email protected]> writes: > > Felix> On 2015-11-08 07:24, Russell Senior wrote: >>> >>> Reworked from patch by Ben Pfountz <[email protected]> Builds and >>> boots. >>> >>> Signed-off-by: Russell Senior <[email protected]> > Felix> Why do we need a subtarget for APU instead of just running the > Felix> generic one on it? > > It conveniently selects/deselects a bunch of .config options (e.g. sets > an appropriate BAUDRATE, selects USB options). I haven't studied all the > differences closely.
Hello, Just my two cents. What with apu2x [1] then (ex. different eth)? Another subtarget? For me, that LED/BTN code looks like... workaround. This hardware (apu1x) needs two, proper GPIO drivers for: - GPIO controlled by AMD A50M chipset (LEDs, button) - look at [2] - GPIO controlled by Nuvoton NCT5104D (GPIO in J19 header) Cheers, Piotr [1] http://pcengines.ch/apu2b4.htm [2] https://lkml.org/lkml/2013/7/4/251 _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
