On Sun, 2012-12-16 at 09:26 +0100, John Crispin wrote: > as always please just state what yoiu want so we can implement it > properly instead of random hacks
Here is a list of things the "random hacks" do: 1) Fix a typo in the "internet" LED name 2) Provide some useful function for the power2 LED 3) Fix the fact that trunk fails to generate any image for the DGN3500A profile 4) Add the usbdev trigger to the Kconfig since the devtree file already uses it 5) Make the 42_athfix, when it's applicable again, apply to both flavors of DGN3500, not just the B 6) Assign the _correct_ LED to netdev 7) As previously stated, the bootargs code as is leaves the original bootargs unconditionally inaccessible, so restore the previous behavior This time, I have refrained from stepping on anything you might conceivably already be working on differently. You might still consider all of the above "random hacks" not to be done "properly" and you say to wait, but you know, one of the purposes of bringing a deck of cards on a mountain hike is that if you're alone and start playing Solitaire, it guarantees someone will come along and tell you which card to move where. When that happens, you can either get annoyed and shoo them away, or accept the input and bring the game to a sooner conclusion. Either way, the input is still there. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
