Re: [E1000-devel] Supporting platforms with no EEPROM?

2008-09-12 Thread Bill Gatliff
Riku Voipio wrote: > On Fri, Sep 12, 2008 at 10:23:06AM -0700, Brandeburg, Jesse wrote: > >> we don't want to support this in the default drivers, but maybe we could >> in the kernel with a Kconfig option that defaulted to off. > > This could be acceptable, we would only turn that option on the

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread Bill Gatliff
Lennart Sorensen wrote: > On Fri, Sep 12, 2008 at 12:59:06PM -0400, Daniel Kahn Gillmor wrote: >> What about stuffing an equivalent line into your initramfs? >> >> Something like: >> >> ip link set eth0 address 12:34:56:78:9a:bc >> >> (assuming you've got /bin/ip and dependencies -- i can't seem t

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread Bill Gatliff
Daniel Kahn Gillmor wrote: > What about stuffing an equivalent line into your initramfs? > > Something like: > > ip link set eth0 address 12:34:56:78:9a:bc > > (assuming you've got /bin/ip and dependencies -- i can't seem to make > this work from busybox's implementation of ip) Is there not s

Re: [E1000-devel] Supporting platforms with no EEPROM?

2008-09-12 Thread Riku Voipio
On Fri, Sep 12, 2008 at 10:23:06AM -0700, Brandeburg, Jesse wrote: > we don't officially support eepromless designs in our normal drivers > (most embedded users expect to modify their drivers). I know that there > is some test patches to allow the eepromless set up in our drivers, that > our TME t

RE: [E1000-devel] Supporting platforms with no EEPROM?

2008-09-12 Thread Brandeburg, Jesse
Bill Gatliff wrote: > John Winters wrote: >> Bill Gatliff wrote: >> [snip] >>> The MAC Address will be reset to 00:00:00:00:00:00, which is invalid >>> and requires you to set the proper MAC address manually before >>> continuing >>> to enable this network device. the Linux kernel actually can ma

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread Lennart Sorensen
On Fri, Sep 12, 2008 at 12:59:06PM -0400, Daniel Kahn Gillmor wrote: > What about stuffing an equivalent line into your initramfs? > > Something like: > > ip link set eth0 address 12:34:56:78:9a:bc > > (assuming you've got /bin/ip and dependencies -- i can't seem to make > this work from busybo

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread Daniel Kahn Gillmor
On Fri 2008-09-12 12:26:09 -0400, Bill Gatliff wrote: > John Winters wrote: > >> Can't you just put a made-up MAC address into /etc/network/interfaces? >> Like this: >> >> allow-hotplug eth0 >> iface eth0 inet dhcp >> hwaddress ether 12:34:56:78:9a:bc > > One could, but that won't work for r

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread John Winters
Bill Gatliff wrote: [snip] > The MAC Address will be reset to 00:00:00:00:00:00, which is invalid > and requires you to set the proper MAC address manually before continuing > to enable this network device. [snip] > To date, the only way I've seen around this is to just hack out the code in > the

Re: Supporting platforms with no EEPROM?

2008-09-12 Thread Bill Gatliff
John Winters wrote: > Bill Gatliff wrote: > [snip] >> The MAC Address will be reset to 00:00:00:00:00:00, which is invalid >> and requires you to set the proper MAC address manually before continuing >> to enable this network device. > [snip] >> To date, the only way I've seen around this is to jus

Supporting platforms with no EEPROM?

2008-09-12 Thread Bill Gatliff
Guys: I'm working on a Thecus N4100 platform, which has two e1000's but no EEPROMs. The MAC addresses are set by the bootloader, using values that are stored in the platform's equivalent of a BIOS (flash memory). The platform boots into Linux, currently 2.6.27-rc5. It's an ARM instruction set a