linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Daniel THOMPSON <daniel.thompson@st.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 2.6.17-rc6-mm2] fbdev: tag by	scantype in sysfs
Date: Fri, 23 Jun 2006 20:00:11 +0800	[thread overview]
Message-ID: <449BD7CB.1050904@gmail.com> (raw)
In-Reply-To: <449BB94A.6000003@st.com>

Daniel THOMPSON wrote:
> Geert Uytterhoeven wrote:
>> On Fri, 23 Jun 2006, Daniel THOMPSON wrote:
>>> On Tue, 2006-06-20 at 18:29 +0800, Antonino A. Daplas wrote:
>>>>  /sys/class/graphics---fb0
>>>>                     :
>>>>                     --fb1
>>>>                     :
>>>>                     --fbn
>>>>                     :
>>>>                     --mode0---640x480@60
>>>>                     :       :
>>>>                     :       --1024x768@60
>>>>                     :  
>>>>                     --mode1
>>> So the directory mode0 contains all the modes that fb0 is capable of
>>> displaying? Can't that go inside fb0?
>> Let's hope not, as most machines/fb combos don't have enough RAM to store all
>> modes the fb is capable of.
> 
> Fair point.
> 
> By default the existing modes includes only the VESA standard modes,
> although I would expect drivers for TV-like hardware to override the
> mode list to get the supportable CEA-851 standards instead.
>

It only includes modes that are in the driver's private mode list. For
most drivers, that's one entry, for others with EDID, it can be as
much as 40 (near-maximum the EDID block is capable of), but typically
less than 10.
 
> I confess I'm having a great deal of difficulty trying to think of any
> way to update the mode list while sticking to one file, one value.

We can unbind fb[n] from display[n], echo the mode we want added to an 'x'
file one by one, and the modes we don't want into a 'y' file. Finally,
we can bind fb[n] back to display[n]. It's ugly, but can work.

After giving it some thought, sysfs is just not appropriate to serve the
needs of the framebuffer system. So I'll leave fbsysfs untouched for now and
just find/invent more appropriate interfaces.

Tony

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-06-23 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  7:57 [PATCH 2.6.17-rc6-mm2] fbdev: tag by scantype in sysfs Daniel THOMPSON
2006-06-20  8:42 ` Antonino A. Daplas
2006-06-20  9:40   ` Daniel THOMPSON
2006-06-20 10:29     ` Antonino A. Daplas
2006-06-23  8:04       ` Daniel THOMPSON
2006-06-23  9:16         ` Geert Uytterhoeven
2006-06-23  9:50           ` Daniel THOMPSON
2006-06-23 12:00             ` Antonino A. Daplas [this message]
2006-06-23 20:23         ` Luca

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=449BD7CB.1050904@gmail.com \
    --to=adaplas@gmail.com \
    --cc=daniel.thompson@st.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).