linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, 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 17:01:16 +0100	[thread overview]
Message-ID: <200403231701.19786.lkml@kcore.org> (raw)
In-Reply-To: <20040323122627.GA22830@lambda>

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

On Tuesday 23 March 2004 13:26, Sven Luther wrote:

> > - 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.
>
> Notice that /display is what is used by most OF implementations, so this
> kinda makes sense. I would vote like BenH on this if i was consulted.

OF implementations?

>
> > Display would be the EDID info of my screen (physical), and graphics...
> > well... I'd half expect something like capture cards to be there...
>
> But this also makes sense, still, i guess we are concerned with more
> info than just the framebuffer, right ?

Yup. What's in a name indeed. But one might try to make it as non-confusing as 
possible.

Kind regards,

Jan De Luyck

- -- 
Anything is possible on paper.
		-- Ron McAfee
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAYF9OUQQOfidJUwQRAlUCAJ9gevHf51xYtw7Zu4PAAI3Lq+VvJgCbByUB
c2zgx+ZzG9zKZo/9Lslr76s=
=zzhB
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-03-23 16:01 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
2004-03-23 12:26           ` Sven Luther
2004-03-23 16:01             ` Jan De Luyck [this message]
2004-03-23 16:13               ` [Linux-fbdev-devel] " 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=200403231701.19786.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 \
    --cc=sven.luther@wanadoo.fr \
    /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).