From owner-freebsd-mobile Tue Jun 3 16:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA29424 for mobile-outgoing; Tue, 3 Jun 1997 16:01:43 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29419 for ; Tue, 3 Jun 1997 16:01:40 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA28822; Tue, 3 Jun 1997 17:01:37 -0600 (MDT) Date: Tue, 3 Jun 1997 17:01:37 -0600 (MDT) Message-Id: <199706032301.RAA28822@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: Brian Somers , freebsd-mobile@freebsd.org Subject: Re: 3c589c resume In-Reply-To: <199706032259.QAA28802@rocky.mt.sri.com> References: <199706032146.WAA04884@awfulhak.demon.co.uk> <199706032259.QAA28802@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams writes: > > My 3c589c doesn't resume properly - I get an "eeprom failed to > > come ready" message. > > > > Has anyone else seen/fixed this ? If not, I'm ready to look > > deeper now. > > Look deeper. I guess that was a little too terse. This is a 'known bug', so feel free to come up with a correct fix. Look at the PAO code for a start, but that code wasn't complete as I can still get it to fail. (They recommend turning off the card before removing it, but that doesn't help with suspend/resume.) Nate