From: Christer Weinigel <christer@weinigel.se> Date: Thu, 12 Mar 2009 11:41:24 +0100This 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Re: init's children list is long and slows reaping children. |
| Kohei KaiGai | [PATCH 0/3] exporting capability name/code pairs (final#2) |
git: | |
| Gerrit Renker | [PATCH 33/37] dccp: Initialisation framework for feature negotiation |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Mark Ryden | Re: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 |
