From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263537AbUBNXC1 (ORCPT ); Sat, 14 Feb 2004 18:02:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263539AbUBNXC1 (ORCPT ); Sat, 14 Feb 2004 18:02:27 -0500 Received: from gate.crashing.org ([63.228.1.57]:42908 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S263537AbUBNXC0 (ORCPT ); Sat, 14 Feb 2004 18:02:26 -0500 Subject: Re: [PATCH] back out fbdev sysfs support From: Benjamin Herrenschmidt To: Dave Jones Cc: Christoph Hellwig , Linus Torvalds , James Simmons , Linux Kernel list In-Reply-To: <20040214172839.GA2065@redhat.com> References: <20040214165037.GA15985@lst.de> <20040214170600.GA16147@lst.de> <20040214172839.GA2065@redhat.com> Content-Type: text/plain Message-Id: <1076799722.868.33.camel@gaston> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 15 Feb 2004 10:02:02 +1100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2004-02-15 at 04:28, Dave Jones wrote: > On Sat, Feb 14, 2004 at 06:06:00PM +0100, Christoph Hellwig wrote: > > > What I meant is that the FB maintainer should try to get the existing > > fixes merged before adding dubious features. > > Whilst on the subject, why does the fb code need sysfs support > anyway ? We want a class device so the drivers can expose some informations like the monitor probing data (EDID), allowed modes list etc... to userland. I now have access to these infos in some drivers like radeonfb that do full monitor probing, and the fbdev "API" provides no way to get that down to userland (for use by xserver or MOL for example). I could just add some cases to the existing ioctl API, but I don't like that ;) Ben.