[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090312.055523.193191701.davem@davemloft.net>
Date: Thu, 12 Mar 2009 05:55:23 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: christer@...nigel.se
Cc: 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
From: Christer Weinigel <christer@...nigel.se>
Date: Thu, 12 Mar 2009 11:41:24 +0100
> 1. The bootloader can pass a command line to the kernel and it is saved in non-volatile storage that can be changed from the bootloader
>
> 2. I can not modify the bootloader
>
> 3. I can modify the Linux kernel
>
> 4. The manufacturer has hardcoded a MAC address in the ethernet driver
>
> 5. I want to use NFS root to make it easy to develop on the platform
>
> 6. We get a second board so the hardcoded MAC addresses collide
This is getting rediculious.
If you can modify the kernel, you can have the kernel look in the
non-volatile storage for the MAC address and export that information
to the ethernet driver.
Or, you can parse the command line in your platform specific code
and program the MAC address into the chip.
In fact there are many reasonable ways to solve the problem in
your scenerio, and none of them require device driver command
line option handler.
None.
--
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