[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49B9B716.4060506@weinigel.se>
Date: Fri, 13 Mar 2009 02:29:58 +0100
From: Christer Weinigel <christer@...nigel.se>
To: Neil Horman <nhorman@...driver.com>
CC: Jamie Lokier <jamie@...reable.org>, davem@...emloft.net,
shemminger@...tta.com, s.hauer@...gutronix.de, yanok@...raft.com,
linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org,
wd@...x.de, dzu@...x.de
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver
Neil Horman wrote:
> So, I've avoided asking this question, because I didn't want to get off topic,
> but since it appears we're winding up here, I have to ask what your long term
> plan is for your final application. I can understand being hesitant to invest
> in an initramfs when its solely for your intermediate development (even though I
> think that will pay off for you in the long run), but when your development
> ends, and you ship a product, how do you plan to implement your application? I
> would imagine you at least need an initramfs to store, load and run your final
> application don't you? How do you plan on executing it?
Most probably no ramdisk at all, just the mtd driver and flash file
system driver compiled into the kernel and then "root=/dev/mtdblock4".
For one old product the bootloader programs the mac address into the
ethernet chip before the kernel boots. For another embedded system
thats out in production the bootloader is really dumb and it's up to
early userspace to extract the mac address from nonvolatile memory and
do ifconfig hwaddr.
And as I wrote in a different post, most systems I'm working on now
won't even have ethernet.
/Christer
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists