On Thu, Apr 11, 2013 at 12:02:48PM -0500, Ben West wrote: > > > Previous discussion on this topic indicated the preferred approach is to > > > migrate the atheros platform to board-specific target profiles, like how > > > was done with ar71xx. > > > > > > What is the best way to begin here? Is there information available on > > > how board-specific target profiles are defined? > > Board specific target profiles are not a suitable way to deal with this > > problem. With platforms like ar71xx, the same build works on all common > > devices (through kernel command line patching). > > ar71xx is not a good example on where a platform rework should go, the > > use of Device Tree is preferred, and it has been implemented in the > > ramips and lantiq platforms. If you want to do a proper rework of the > > target, those are good examples to look at. > > > > Thank you very much for the pointer to Device Tree in the ramips and lantiq > platforms. That helps greatly. >
Do buttons work on your device? I've submitted http://patchwork.openwrt.org/patch/3536/ which to the best of my knowledge fixes things, but, as you know, there's clearly more than one "atheros" board out there. Mine will do reboot from the command line quite ok, but I have to switch the AR2315_RESET_GPIO from 5 to 6 to make the buttons work properly. I'm more than happy to test out any changes here for atheros platforms, but I only have the one type of atheros device, the dragino MS12, ar2317: http://wiki.openwrt.org/toh/dragino/ms12 Sincerely, Karl Palsson _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
