From: Kronos <kronos@kronoz.cjb.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] Re: [PATCH] Sysfs for framebuffer
Date: Sat, 20 Mar 2004 22:52:19 +0100 [thread overview]
Message-ID: <20040320215219.GA20277@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040320213030.GA3950@kroah.com>
Il Sat, Mar 20, 2004 at 01:30:30PM -0800, Greg KH ha scritto:
> 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... :)
Hum, I remeber your patch that did the same thing, but it didn't use
class_simple, did it?
> 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.
It was discussed a while ago (this is James):
<quote>
On Tue, 9 Sep 2003, Benjamin Herrenschmidt wrote:
> > On Tue, 2003-09-09 at 21:24, Kronos wrote:
> > > +static struct class fb_class = {
> > > + .name = "video",
> >
> > I'd rather use "display" here. "video" is too broad and will cause
> > confusion with multimedia stuff.
>
> Exactly my comment. I was thinking about `graphics' instead of
> `video', but indeed `display' sounds better. Gr{oetje,eeting}s,
I prefere graphics myself. Display sounds to generic. That is what video
and graphics output is piped to. Since fbdev doesn't handle video ouput
normally this is kind of fuzzy sounding.
</quote>
Luca
--
Home: http://kronoz.cjb.net
"Di tutte le perversioni sessuali, la castita` e` la piu` strana".
Anatole France
next prev parent reply other threads:[~2004-03-20 21:52 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
2004-03-20 21:52 ` Kronos [this message]
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=20040320215219.GA20277@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--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).