From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Jones <davej@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@osdl.org>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] back out fbdev sysfs support
Date: Sun, 15 Feb 2004 10:02:02 +1100 [thread overview]
Message-ID: <1076799722.868.33.camel@gaston> (raw)
In-Reply-To: <20040214172839.GA2065@redhat.com>
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.
next prev parent reply other threads:[~2004-02-14 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 16:50 [PATCH] back out fbdev sysfs support Christoph Hellwig
2004-02-14 17:02 ` Linus Torvalds
2004-02-14 17:06 ` Christoph Hellwig
2004-02-14 17:28 ` Dave Jones
2004-02-14 23:02 ` Benjamin Herrenschmidt [this message]
2004-02-14 17:58 ` viro
2004-02-14 19:57 ` Paul Mundt
2004-02-14 23:04 ` Benjamin Herrenschmidt
2004-02-16 22:49 ` James Simmons
2004-02-16 22:58 ` Benjamin Herrenschmidt
2004-02-16 23:07 ` James Simmons
2004-02-16 22:44 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1076799722.868.33.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davej@redhat.com \
--cc=hch@lst.de \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox