Le dimanche 9 mai 2010 05:21:46, Michael Evans a écrit :
Florian, I'm very much not a fan of the Makefile level solution you've
used.
Is that behavior required to work regardless of multi-threading
linkers/make processes? I can see situations where it could work for
some builders all the
Le dimanche 9 mai 2010 06:10:37, Michael Evans a écrit :
Yes, that patch indeed solves my problem as well. Why isn't it in a
generic (all platforms) patch area?
Applied in r21408, I assume not that many models needed support for Samsung
flahs parts.
On Sat, May 8, 2010 at 5:13 AM,
I could finally install everything onto my 4MB WRT54g v2.2.
Avoided ntpclient plus dependencies with the patch from #7316.
Added BusyBox's ether-wake to the build.
Put all kmods (2) I needed into the kernel.
This freed up enough JFFS2 space to normally install OpenVPN and a
web-interface (here
Hello list,
Over the past couple of weeks, I've been trying to make extroot run on an
SDcard.
I came up with an sdcard preinit script, which is nothing more that the stock
sdcard init script modified so as to run from preinit, and I was told to drop a
line in here.
I'm not sure how good it is
Put all kmods (2) I needed into the kernel.
How?
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
That's how it works. Y adds kernel modules to the kernel, and programs
to the image.
..ede
On 09.05.2010 18:10, Matthias Buecher / Germany wrote:
In 'make menuconfig' I included them with 'Y' instead of 'M'.
According to my (newbie) knowledge that adds them to the kernel image.
Can somebody
Actually, Y in menuconfig doesn't add the modules into the kernel,
they will still be kernel modules. It only places the modules directly
in the image and is in no way different from Y for programs. M creates
packages for the modules/program without placing it in the image.
If you want to compile
true, my bad, actually one can see it in the end of a make run, how the
packages (incl. kmods) are installed to the image filesystem.
thanks ede
On 09.05.2010 18:19, Bernhard Loos wrote:
Actually, Y in menuconfig doesn't add the modules into the kernel,
they will still be kernel modules. It
If you are really bored, you could use gcc 4.5 and link time optimization.
Support for it is already enabled in the openwrt gcc, but you have to
add the compiler flags to use it to packages and/or the kernel. In
theory, it could reduce the binary size, but I have no idea how well
this will work in
Re-checked the configs from my last build (available at
ftp://ftp.maddes.net/openwrt/backfire/brcm-2.4/build_21402/squashfs/)
In the menu config it is CONFIG_PACKAGE_kmod-tun=y, but in the kernel
and final/used config it is CONFIG_TUN=m.
So the better squashfs compression was what helped me.
10 matches
Mail list logo
