On Tue, 2006-01-03 at 23:17 +0000, David Woodhouse wrote: > This isn't the right answer, but it's a hack which makes it reassociate > after resume. Really, we should implement suspend/resume methods in > softmac itself. > > --- linux-2.6.15/drivers/net/wireless/bcm43xx/bcm43xx_main.c~ 2006-01-03 > 22:56:55.000000000 +0000 > +++ linux-2.6.15/drivers/net/wireless/bcm43xx/bcm43xx_main.c 2006-01-03 > 23:00:15.000000000 +0000 > @@ -4543,6 +4541,7 @@ static int bcm43xx_resume(struct pci_dev > } > > netif_device_attach(net_dev); > + queue_work(bcm->softmac->workqueue,&bcm->softmac->associnfo.work); > > dprintk(KERN_INFO PFX "Device resumed.\n");
Does that restore things like selected rate, essid, etc... ? We do lose those with ifdown/ifup ... Also, another problem is the firmware load stuff. It's done synchronously, which means that if your device hapens to be resumed before your hard disk, you are toast ... Ben. _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
