Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272057AbTHOWh1 (ORCPT ); Fri, 15 Aug 2003 18:37:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272135AbTHOWh1 (ORCPT ); Fri, 15 Aug 2003 18:37:27 -0400 Received: from pub234.cambridge.redhat.com ([213.86.99.234]:18695 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S272057AbTHOWhY (ORCPT ); Fri, 15 Aug 2003 18:37:24 -0400 Date: Fri, 15 Aug 2003 23:37:21 +0100 (BST) From: James Simmons To: Greg KH cc: Otto Solares , Linux Kernel Mailing List , Linux Fbdev development list Subject: Re: FBDEV updates. In-Reply-To: <20030814231620.GA4632@kroah.com> 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: 1055 Lines: 23 > > Is there an API (or lib) to use framebuffers devices without > > worring about differents visuals?, to quering, setting or > > disabling EDID support? will these drivers export sysfs > > entries instead of control via ioctl's? > > I have some initial sysfs patches for the fb code that I've been sitting > on in my trees. I was waiting for these patches to hit the mainline > before bothering James and the rest of the world with them. > > But they don't export any of the ioctl stuff through the sysfs > interface, but that would not be very hard to do at all if you want to. > They just basically show the major/minor of the fb device, and point > back to the proper place in the device tree where the fb device lives, > which is all udev really needs right now. Could you send me those patches :-) - 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/