"Erez, Maya" <merez@xxxxxxxxxxxxxx> writes: > On 3/30/2016 3:13 PM, Kalle Valo wrote: > > Lior David <liord@xxxxxxxxxxxxxx> writes: > > > As I see it, it is an issue of classification. Network drivers use a > > default > > interface name prefix depending on the device type. Ethernet drivers get > > "eth%d", > > wireless drivers get "wlan%d" and so on. There are even existing drivers > that give different prefixes based on other conditions, for example see > drivers/s390/net/ctcm_main.c, ctcm_init_netdevice. > For our 11ad device, in many platforms it is used as a wifi replacement, > > so > > the wlan%d name is appropriate, in other platforms it is used as > a different wireless device for different purposes, so the default > > "wigig%d" > > prefix seems appropriate. > > Every platform works differently, even systemd even has it's own weird > naming scheme: > > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterf > aceNames/ > > I really don't think that we should start working around interface > naming problems by selecting the name with module parameters. But having > "wigig%d" as the default sounds like a good idea to me. > > > Thanks, Kalle. We will check your suggestion to change the interface name to > "wigig%d". > > Can you drop this patch for now? Ok, patch 2 dropped. Patch 1 is still on my queue and will be applied "really soon now" :) -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
