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
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
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
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
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
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
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
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
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
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
10 matches
Mail list logo