Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+natsemi\s+update\s+1\/4\s+Use\s+assigned\s+MAC\s+address\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+natsemi\s+update\s+1\/4\s+Use\s+assigned\s+MAC\s+address\s*$/: 20 ]

Total 20 documents matching your query.

1. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: xxxxxxxxxxxxxx>; Date: Sun, 06 Jun 2004 15:30:25 +0200; This is the first of a series of patches needed to support our product using the DP83815. This patch accepts the MAC address as a parameter because our implementation does not have an EEPROM. I tried; /archives/netdev/2004-06/msg00127.html (13,745 bytes)
2. [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: rl@xxxxxxxxxxx>; Date: Fri, 04 Jun 2004 14:51:59 -0500; This is the first of a series of patches needed to support our product using the DP83815. This patch accepts the MAC address as a parameter because our implementation does not have an EEPROM. I trie; /archives/netdev/2004-06/msg00146.html (9,124 bytes)
3. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: inger@xxxxxxxx>; Date: Mon, 07 Jun 2004 12:58:55 -0500; I agree with all comments. Regarding the total elimination of this patch ... Only our bootrom knows the MAC address that should be used, and it appends it to the bootargs. If there is a way for the; /archives/netdev/2004-06/msg00157.html (14,675 bytes)
4. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: baugh@xxxxxxxx>; Date: Mon, 7 Jun 2004 11:16:38 -0700; /proc/cmdline??; /archives/netdev/2004-06/msg00159.html (9,548 bytes)
5. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: s@xxxxxxxxxxxx>; Date: Mon, 07 Jun 2004 16:12:49 -0500; Scrap patch 1 of 4, we don't need or want it. (I'm feeling so sheepish.) Thanks, Gary ** REPLY SEPARATOR ** oooooooooooooooooooooooooooooooooooooooooooooooooo Gary Spiess (Gary.Spiess@xxxxxxxxxxxx); /archives/netdev/2004-06/msg00172.html (10,052 bytes)
6. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: s@xxxxxxxxxxxx>; Date: Tue, 8 Jun 2004 07:12:52 +0930; Hi Manfred, Gary, Stephen, "But: I'm not sure that the change is required. What about just setting the mac to 0, and the actual mac address is set from user space? It's possible to set the mac addres; /archives/netdev/2004-06/msg00173.html (9,499 bytes)
7. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: xxxxxxxxxxxxxx>; Date: Mon, 7 Jun 2004 14:46:54 -0700; Actually, it won't let you add any interface to a bridge without a valid ether address now (ie non-zero and not multicast).; /archives/netdev/2004-06/msg00174.html (10,397 bytes)
8. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: inger@xxxxxxxx>; Date: Mon, 7 Jun 2004 14:48:36 -0700; How about random_ether_addr(dev->dev_addr); it does the right thing.; /archives/netdev/2004-06/msg00175.html (9,299 bytes)
9. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: vem@xxxxxxxxxx>; Date: Tue, 8 Jun 2004 07:41:05 +0930; <snip> That's good, I first noticed this issue when I happened to add a dummy interface into a bridge configuration, and found that its zero MAC address ended up disrupting the spanning tree. I also; /archives/netdev/2004-06/msg00177.html (10,484 bytes)
10. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: zik <jgarzik@xxxxxxxxx>; Date: Tue, 08 Jun 2004 14:31:24 -0400; since there was discussion and multiple patches flying about, could you resend the patchset, now that the dust has settled?; /archives/netdev/2004-06/msg00207.html (8,875 bytes)
11. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>; Date: Sun, 06 Jun 2004 15:30:25 +0200; Jeff, This is the first of a series of patches needed to support our product using the DP83815. This patch accepts the MAC address as a parameter because our implementation does not have an EEPROM.; /archives/netdev/2004-06/msg01011.html (13,873 bytes)
12. [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: "Gary N Spiess" <Gary.Spiess@xxxxxxxxxxxx>; Date: Fri, 04 Jun 2004 14:51:59 -0500; Jeff, This is the first of a series of patches needed to support our product using the DP83815. This patch accepts the MAC address as a parameter because our implementation does not have an EEPROM. I; /archives/netdev/2004-06/msg01030.html (9,124 bytes)
13. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: "Gary N Spiess" <Gary.Spiess@xxxxxxxxxxxx>; Date: Mon, 07 Jun 2004 12:58:55 -0500; Jeff, I agree with all comments. Regarding the total elimination of this patch ... Only our bootrom knows the MAC address that should be used, and it appends it to the bootargs. If there is a way for; /archives/netdev/2004-06/msg01041.html (14,758 bytes)
14. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 7 Jun 2004 11:16:38 -0700; /proc/cmdline??; /archives/netdev/2004-06/msg01043.html (9,677 bytes)
15. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: "Gary N Spiess" <Gary.Spiess@xxxxxxxxxxxx>; Date: Mon, 07 Jun 2004 16:12:49 -0500; Stephen, Scrap patch 1 of 4, we don't need or want it. (I'm feeling so sheepish.) Thanks, Gary ** REPLY SEPARATOR ** oooooooooooooooooooooooooooooooooooooooooooooooooo Gary Spiess (Gary.Spiess@xxxxxx; /archives/netdev/2004-06/msg01056.html (10,208 bytes)
16. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Mark Smith <random@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 8 Jun 2004 07:12:52 +0930; Hi Manfred, Gary, Stephen, "But: I'm not sure that the change is required. What about just setting the mac to 0, and the actual mac address is set from user space? It's possible to set the mac addres; /archives/netdev/2004-06/msg01057.html (9,499 bytes)
17. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 7 Jun 2004 14:46:54 -0700; Actually, it won't let you add any interface to a bridge without a valid ether address now (ie non-zero and not multicast).; /archives/netdev/2004-06/msg01058.html (10,473 bytes)
18. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 7 Jun 2004 14:48:36 -0700; How about random_ether_addr(dev->dev_addr); it does the right thing.; /archives/netdev/2004-06/msg01059.html (9,375 bytes)
19. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Mark Smith <random@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 8 Jun 2004 07:41:05 +0930; <snip> That's good, I first noticed this issue when I happened to add a dummy interface into a bridge configuration, and found that its zero MAC address ended up disrupting the spanning tree. I also; /archives/netdev/2004-06/msg01061.html (10,584 bytes)
20. Re: [PATCH] natsemi update 1/4 Use assigned MAC address (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 08 Jun 2004 14:31:24 -0400; Manfred, since there was discussion and multiple patches flying about, could you resend the patchset, now that the dust has settled?; /archives/netdev/2004-06/msg01091.html (8,986 bytes)

Current List: 1 - 20
Page: [1]