linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Kronos <kronos@kronoz.cjb.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] Re: [PATCH] Sysfs for framebuffer
Date: Tue, 23 Mar 2004 12:11:00 +0100	[thread overview]
Message-ID: <200403231211.09334.lkml@kcore.org> (raw)
In-Reply-To: <20040322195720.GA27480@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 22 March 2004 20:57, Greg KH wrote:
> On Mon, Mar 22, 2004 at 09:50:46AM +1100, Benjamin Herrenschmidt wrote:
> > > 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.
> >
> > I still prefer display...
>
> Bah, I don't want to argue here.  I've applied Kronos's patch as is to
> my device-2.6 tree which will end up in the next -mm release.
>
> I'll hold off forwarding this patch to Linus until after 2.6.5 is out,
> so that gives everyone a few days in which to argue the name a bunch and
> then send me a patch that changes it to the decided apon name (if it is
> to be changed.)

- From a users point of view: if there are only to be framebuffer devices listed 
in this class, why not call it just what it is: "Framebuffer" ? Naming it 
after something it is only in a broad sense makes no sense to me. I'd be 
looking in /sys/.../framebuffer instead of /sys/.../graphics or /display.

Display would be the EDID info of my screen (physical), and graphics... 
well... I'd half expect something like capture cards to be there...

Just my 0.02EUR.

Jan

- -- 
patent:
	A method of publicizing inventions so others can copy them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAYBtMUQQOfidJUwQRAugBAJ4jSuhjpzr2jySPGmc6yk4lYflILgCfTB0M
nA8OHiWcRfjRllgoxC/KJBY=
=I8ag
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-03-23 11:11 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   ` [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 [this message]
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=200403231211.09334.lkml@kcore.org \
    --to=lkml@kcore.org \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --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).