From: Greg KH <greg@kroah.com>
To: Kronos <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Sysfs for framebuffer
Date: Sat, 20 Mar 2004 13:30:30 -0800 [thread overview]
Message-ID: <20040320213030.GA3950@kroah.com> (raw)
In-Reply-To: <20040320174956.GA3177@dreamland.darkstar.lan>
On Sat, Mar 20, 2004 at 06:49:56PM +0100, Kronos wrote:
> Hi,
> the following patch (against 2.6.5-rc2) teaches fb to use class_simple.
> With this patch udev will automagically create device nodes for each
> framebuffer registered. Once all drivers are converted to
> framebuffer_{alloc,release} we can switch to our own class.
yeah, it's about time! Didn't I post this patch a few months ago... :)
Anyway, it looks good, I only have one comment:
> notebook:~# tree /sys/class/graphics/
> /sys/class/graphics/
"graphics"? Why that? Why not "fb"?
It doesn't really matter to me, just curious.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-20 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 17:49 [PATCH] Sysfs for framebuffer Kronos
2004-03-20 21:30 ` Greg KH [this message]
2004-03-20 21:52 ` [Linux-fbdev-devel] " Kronos
2004-03-20 21:59 ` Greg KH
2004-03-21 8:02 ` Ingo Oeser
2004-03-22 17:41 ` Gerd Knorr
2004-03-21 22:50 ` Benjamin Herrenschmidt
2004-03-22 19:57 ` [Linux-fbdev-devel] " Greg KH
2004-03-23 11:11 ` Jan De Luyck
2004-03-23 12:26 ` Sven Luther
2004-03-23 16:01 ` [Linux-fbdev-devel] " Jan De Luyck
2004-03-23 16:13 ` Geert Uytterhoeven
2004-03-23 17:58 ` 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=20040320213030.GA3950@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).