On Sat, 19 Feb 2000, Russell King wrote:
> Jeff Garzik writes:
> > But... per a discussion a month ago or so, people made the point that
> > this stuff can be better done in userspace.
> >
> > Can we take IP autoconfig out of the kernel?
> >
> > You should be able to accomplish the same thing with dhcpcd, bootp,
> > pump, etc.
>
> I have a quick "hack" to get this working you may be interested in:
>
> --- linux.orig/arch/arm/vmlinux-armv.lds.in Sat Jan 22 19:46:12 2000
> +++ linux/arch/arm/vmlinux-armv.lds.in Sat Feb 12 20:20:02 2000
> @@ -19,6 +19,8 @@
> *(.setup.init)
> __setup_end = .;
> __initcall_start = .;
> + drivers/net/net.o(.initcall.init)
> + fs/fs.o(.initcall.init)
> *(.initcall.init)
> __initcall_end = .;
> . = ALIGN(4096);
>
> This seems to work fine for me, however I haven't tried it without networking
> configured (I think it may fail to link). This behaviour should be checked
> before it goes into Linus' kernel.
That looks good, though you are right it may fail to link. My (7:31am)
solution is somewhat along the same lines: Declare initcall
dependencies somewhere, and then have a script wade through those
and create vmlinux.lds... We'll see how well this works after morning
coffee and some thinking...
jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:23 EST