From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 10:11:07 2004 Return-Path: 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 73E9F16A4CE; Fri, 30 Jan 2004 10:11:07 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEC7943D78; Fri, 30 Jan 2004 10:10:26 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0UIA6ET075080; Fri, 30 Jan 2004 11:10:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 30 Jan 2004 11:10:02 -0700 (MST) Message-Id: <20040130.111002.26275922.imp@bsdimp.com> To: jhb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200401301306.57986.jhb@FreeBSD.org> References: <20040130092529.GA725@laptop.6bone.nl> <20040130.083614.75932761.imp@bsdimp.com> <200401301306.57986.jhb@FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@jp.freebsd.org cc: current@FreeBSD.org Subject: Re: API to turn off the display X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 18:11:07 -0000 In message: <200401301306.57986.jhb@FreeBSD.org> John Baldwin writes: : On Friday 30 January 2004 10:36 am, M. Warner Losh wrote: : > In message: <20040130092529.GA725@laptop.6bone.nl> : > : > Mark Santcroos writes: : > : On Thu, Jan 29, 2004 at 11:32:54AM -0500, John Baldwin wrote: : > : > I read the spec yesterday, and what is supposed to happen is this: The : > : > display (LCD, CRT, etc.) is supposed to be powered down using DPMS. : > : > The actual adapter is then supposed to be powered down using either PCI : > : > or ACPI sleep states, and the adapter should not be powered down to a : > : > lower sleep state (like D3) w/o using DPMS to power the display down to : > : > at least that state first. This means that the kernel might need to : > : > grow a dummy vga driver of some sort and some simple dpms support for : > : > suspend/resume. : > : : > : I second this. : > : : > : Nate, can you put it on your acpi-todo list? : > : > The only problem with having a vga device for suspend/resume is that : > it will claim devices that drm wants to claim later and X won't work. : > : > I have about the simplest driver possible for vga in one of my trees, : > and found this to be a problem on my dell i8k. : : Yes, we need a way I think to have multiple drivers attach to a device, or : maybe have the drm drivers attach as a child of the vga device instead. For : the intel motherboards with onboard graphics, we already have this problem : where drm and agp both want the same device. Having a model of: : : vga0 : drm0 : agp0 : : Might be the sanest way to do this cleanly. Yes. I like that model. While it might be nice to have a reauction of devices in the newbus level, I think that for this case there's limited usefulness in doing that. Having vga driver that others attach to will also allow drm drivers to possibly attach to a vga driver that's attached to something other than a pci bus. Warner