i'm just following the logic for the simple clean targets, and i'm
confused as to how "make clean" and "make dirclean" work. in a
fully-cleaned openwrt tree, running either of those dumps one into
"make menuconfig", which would seem to be a pointless exercise if the
tree is already clean.
in
[EMAIL PROTECTED] wrote:
> openwrt supports some time sync applications (openntp, rdate...) be
> there is no timezone configuration. if this would be supported, the time
> sync applications could be updated to represent the correct time (create
> /etc/TZ).
>
> cheers
> michu
>
> Signed-off-by: Mi
(given that, in some cases, you don't have the freedom to select the
kernel version you want when building a new image, this idea might not
have much value, but what the heck.)
is there any value to creating a new directory of kernel patches
created against the latest git pull of the kernel?
i'm perusing the generic-2.6.24 linux patches in the svn checkout,
and i'm curious about patch 004-extra_optimization.patch:
=
--- linux-2.6.23-rc6.orig/Makefile 2007-09-21 16:23:55.0 +0800
+++ linux-2.6.23-rc6/Makefile 2007-09-21 16:23:56.0 +0800
@@ -508,6 +508,9 @@
This patch enables the new "default-on" trigger for the AR7 target and uses it
to ensure the "power" LED on the DG834G is initialised in the ON state.
Previously this LED would turn off when the driver loaded and stay off until
turned back on from userspace. With this patch it remains on through
The current LED subsystem always initialises LEDs in the OFF state. This is
fine for most LEDs but some should be on right from boot (e.g. POWER LED).
Following some discussion with the LED subsystem maintainers, a trigger was
recommended as the best way to implement this functionality.
Here is
