Tue, Apr 28, 2009 at 11:12:49AM CEST, davem@xxxxxxxxxxxxx wrote: >From: Jiri Pirko <jpirko@xxxxxxxxxx> >Date: Tue, 28 Apr 2009 10:30:48 +0200 > >> Tue, Apr 28, 2009 at 03:48:54AM CEST, davem@xxxxxxxxxxxxx wrote: >>>From: Chris Leech <christopher.leech@xxxxxxxxx> >>>Date: Mon, 27 Apr 2009 15:28:00 -0700 >>> >>>> Ignoring the issue of intended use for the moment, if an ethernet driver >>>> wanted to advertise several MAC addresses to the system how should it go >>>> about that? >>> >>>Now that's a more interesting question. >>> >>>It seems better to formalize this. It can be an ethtool >>>callback or whatever, but what it should do is return >>>an array of addresses, types, and perhaps even indexes >>>with types. >> >> Well the list of device addresses from my patch can pretty much solve this. >> There can be additional field in struct netdev_hw_addr to store flags to >> identify the mac address type (like primary, lan, san, slave, etc). >> >> I think it would be better to do this in general (in struct net_device) then >> inside each driver exported by ethtool or whatever. > >Agreed, can you update your patch to provide such a 'type' tag? Ok, I'll do that. What types do you have on the top of your head? > >Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
