From owner-freebsd-current Tue Sep 10 8:22:33 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 3E83E37B400 for ; Tue, 10 Sep 2002 08:22:30 -0700 (PDT) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A55143E42 for ; Tue, 10 Sep 2002 08:22:28 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g8AFMFY33137; Wed, 11 Sep 2002 00:22:15 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Wed, 11 Sep 2002 00:22:04 +0900 (JST) Message-Id: <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> To: acpi-jp@jp.FreeBSD.org, marks@ripe.net Cc: current@freebsd.org Subject: Re: [acpi-jp 1789] Re: ACPI video driver (for Dell Latitude C640) From: Mitsuru IWASAKI In-Reply-To: <20020910122910.GA2338@laptop.6bone.nl> References: <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> <20020910122910.GA2338@laptop.6bone.nl> X-Mailer: Mew version 2.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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) Sorry for my late response. I've been checking your driver, and it always seems suspend/resume methods are called. It's; DRIVER_MODULE(acpi_agp, acpi, acpi_agp_driver, acpi_agp_devclass, 0, 0); version. > > 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). It seems that old laptops don't have VGA specific ACPI objects, so many people will be happy if we can implement non-ACPI VGA driver w/ ATI chips hack. BTW, have you checked for XFree86 code? Hopefully we might find some hints on DPMS for ATI chips. > I'm back to where I started basicly (besides knowing more about acpi now). Never mind. I know one more guy who writing ACPI VGA driver, takawata-san(takawata@axe-inc.co.jp). Could you send him your latest code and contact him? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message