Donald Becker wrote: > > On Thu, 2 Nov 2000, Jeff Garzik wrote: > > Paul Gortmaker wrote: > > > On a related note, there are a handful of drivers that register ioports > > > (and IRQ) with the name dev->name (e.g. eth0) as opposed to a more > > > meaningful model name (e.g. "3c503/16"). And some drivers do one for > ... > > For ISA, it's more informative. For PCI, it's less informative because > > the requested resource appears in /proc/ioports underneath the parent > > PCI device. > > Using dev->name is much more meaningful. > I switched over all of my drivers to use dev->name a few years ago. I noticed while writing some hashed device lookup-by-name code that names can be changed at run time. Would that affect the decision any? -- Ben Greear (greearb@candelatech.com) http://www.candelatech.com Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL) http://scry.wanfear.com http://scry.wanfear.com/~greear - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org