Date: Sat, 25 Jul 2015 17:45:53 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: John Baldwin <jhb@freebsd.org>, Joseph Mingrone <jrm@ftfl.ca>, "Brandon J. Wandersee" <brandon.wandersee@gmail.com>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: suspend/resume regression Message-ID: <CAJ-Vmo=pZ7X3JV2PzLtyPi%2BoJVjJpyCm%2BSjY8dJ8NVXbh0Vg9Q@mail.gmail.com> In-Reply-To: <CAN6yY1uKNmDkhm2vntoRvVMLFhNfw04OCqsmc5ggdoRFeFbEMw@mail.gmail.com> References: <86oak289hv.fsf@gly.ftfl.ca> <86oaj9dnbo.fsf@gly.ftfl.ca> <CAN6yY1ubQhsCMqXqV9Fp0M9bLRZGGg07qt0Z3KZNSaxW80GAOg@mail.gmail.com> <12509399.h3RdpFfE1l@ralph.baldwin.cx> <CAN6yY1vaxDd6raCf5p%2BFh5Pw%2BYhHUc9VwRA258roAadozdRLuw@mail.gmail.com> <CAN6yY1uKNmDkhm2vntoRvVMLFhNfw04OCqsmc5ggdoRFeFbEMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Yes, the USB device suspend/resume thing is a more generic suspend/resume problem. Warner has some ideas - eg, registering a "is this a new device?" method; the device driver will check if the device has changed upon resume and optionally go through a detach/reattach process. So for USB it could be something about the serial or FS label; for wifi drivers it could be the MAC / serial number of the NIC, etc. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=pZ7X3JV2PzLtyPi%2BoJVjJpyCm%2BSjY8dJ8NVXbh0Vg9Q>