From owner-freebsd-mobile Fri Apr 7 6:34:29 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id EA4D337BE6D for ; Fri, 7 Apr 2000 06:34:01 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA24143; Fri, 7 Apr 2000 15:33:19 +0200 (MET DST) Message-ID: <38EDE39C.94D94F43@we.lc.ehu.es> Date: Fri, 07 Apr 2000 15:33:16 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Nate Williams Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: proposal of a better solution for "statclock broken" laptops References: <38ECA91E.F98AE48@we.lc.ehu.es> <200004061710.LAA22387@nomad.yogotech.com> <38ED1721.BF297B57@we.lc.ehu.es> <200004062303.RAA25151@nomad.yogotech.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > > > They deal with different problems. The statclock did not start on my > > Dell I3.7k because of a pending interrupt being not cleared at startup. > > The patch included in PR 17800 fixes this problem. > > Ok, so even if it starts up, it doesn't work right if you suspend, > correct? Yes, indeed. Summarizing: - at first, statclock didn't work and APM suspend worked on my laptop. - after I fixed the statclock initialization (PR 17800), it worked, but APM suspend got broken. I needed to set the apm(4)'s 0x20 flag in order to get suspend working again, but this disabled the statclock, going back to the beginning. - with my second set of changes, which disable the statclock interrupts just before suspend, and re-enable them just after resume, APM suspend works, and the statclock does too. > I thought maybe you found a special initialization routine that caused > it work without any special 'suspend/resume' code. Unfortunately I didn't. The RTC periodic interrupt generator is very simple, and there is little to do with its initialization. Saludos, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message