Re: [PATCH] 3c59x and resume

[Greg KH <greg@kroah.com>]

On Sun, Mar 24, 2002 at 09:25:45AM -0500, christophe barbé wrote:
> On Sun, Mar 24, 2002 at 12:07:29AM -0800, Greg KH wrote:
> > On Sat, Mar 23, 2002 at 05:44:33PM -0500, christophe barbé wrote:
> > > With the 'everything is module' and 'everything is hotplug' approach in
> > > mind (which is a appealing way and IMHO this is the way we are going),
> > > I see two part for this problem:
> > > 
> > > . Persistence after plug out/plug in 
> > > 
> > > . Persistence after suspend/resume
> > > 
> > > The first one is a userland problem. The card identification could be
> > > based on the MAC address (for NICs at least, in the case of cardbus the
> > > bus position has no real signification). This should then be the
> > > responsibility of the userspace tool (hotplug) to indicate the correct
> > > option for this card. The problem is when the module is already loaded,
> > > the userspace tool has no way to indicate this option.
> > 
> > Untrue.  See
> > 	http://www.kroah.com/linux/hotplug/ols_2001_hotplug_talk/html/mgp00014.html
> > for a 6 line version of /sbin/hotplug that always assigns the same
> > "ethX" value to the same MAC address.  I think the patch to nameif has
> > gone in to support this, but I'm not sure.
> 
> Untrue what ? The persistence after plug out/in ?

No, the sentence, "The problem is when the module is already loaded..."
/sbin/hotplug gets called when the network device is started up, it
doesn't only get called before the module is loaded.

> The problem here is not to give the same interface to a given NIC. The
> problem is to give the same options to a given NIC. But a solution can
> simply be to set the option from hotplug using the proc interface. The
> 3c59x doesn't support that for wol but that can be changed.

Understood.

> > And why is there a limitation of only 8 devices?  Why not do what all
> > USB drivers do, and just create the structure that you need to use at
> > probe() time, and destroy it at remove() time?
> 
> This is an implementation issue which is not really important. It comes
> from Donald Becker. Your dynamic structure doesn't solve the problem
> 'which options for which cards', does it ? 

No, but it solves the problem, "only 8 devices max", and "what to do
when a card is removed and then plugged back in."  Both seems like good
things to fix in the driver :)

thanks,

greg k-h