Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966304AbWKNTln (ORCPT ); Tue, 14 Nov 2006 14:41:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S966305AbWKNTln (ORCPT ); Tue, 14 Nov 2006 14:41:43 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:13229 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S966304AbWKNTlm (ORCPT ); Tue, 14 Nov 2006 14:41:42 -0500 Date: Tue, 14 Nov 2006 19:41:37 +0000 (GMT) From: James Simmons To: Linux Kernel Mailing List cc: Linux Fbdev development list , Miguel Ojeda Sandonis , Luming Yu , Andrew Zabolotny , Jamey Hicks Subject: ACPI output/lcd/auxdisplay mess Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 827 Lines: 12 I have noticed a bunch of patches coming in dealing with the same problem. How to handle displays i.e LCD, CRT etc. We have a lcd class in video/backlight which no one is using. Because no one was aware of it auxdisplay was created instead. Then we have the acpi code which wants a output class to handle powering down the display device. Plus the acpi layer does something very similar to the framebuffer with getting edids and data relating to the display device. We really should place all this handling in one standard place. To do this I need to know what all of you require. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/