From owner-freebsd-current Tue Sep 10 5:29:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 039F137B400 for ; Tue, 10 Sep 2002 05:29:52 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA8DA43E4A for ; Tue, 10 Sep 2002 05:29:50 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g8ACTnZP010572; Tue, 10 Sep 2002 14:29:49 +0200 Received: (nullmailer pid 3310 invoked by uid 1000); Tue, 10 Sep 2002 12:29:10 -0000 Date: Tue, 10 Sep 2002 14:29:10 +0200 From: Mark Santcroos To: Mitsuru IWASAKI Cc: acpi-jp@jp.FreeBSD.org, current@FreeBSD.ORG Subject: Re: ACPI video driver (for Dell Latitude C640) Message-ID: <20020910122910.GA2338@laptop.6bone.nl> References: <20020825193459.GA725@laptop.6bone.nl> <20020826.223258.00576482.iwasaki@jp.FreeBSD.org> <20020826134202.GA1637@laptop.6bone.nl> <20020827.175855.112858711.iwasaki@jp.FreeBSD.org> <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020829211115.GB2059@laptop.6bone.nl> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 29, 2002 at 11:11:15PM +0200, Mark Santcroos wrote: > I worked around this by making the driver a child of pci instead of a > child of acpi. (Which is even more correct too) My driver is a child of acpi again and at this point it always seems to be called at resume too. I don't know whether that is due to the latest acpi patches (29/8) or other changes in the kernel. (At this point I don't want to spent time tracking that down) > However, getting my screen back doesn't work yet. So there might be more > too it. (In the worst case, the 'OFF' I do, is different than the 'OFF' > the system does, so doing my 'ON' doesn't influence the systems 'OFF') It turned out to be the 'worst case'. The 'OFF' I was doing is not the same 'OFF' as the system itself is doing. (Actually my OFF was a display switch from one to another without going to the other actually. It was a wild guess and turned to be wrong) Do you think that there is a change that this is in the direction of DPMS, or is that very unliky? I tried to find the spec for DPMS but it seems to be a closed on (at least to non-members). I'm back to where I started basicly (besides knowing more about acpi now). Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message