linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Antonino Daplas <adaplas@pol.net>
Cc: Kendall Bennett <KendallB@scitechsoft.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [ANNOUNCE]: VM86 Daemon
Date: 01 Apr 2003 13:34:51 +0200	[thread overview]
Message-ID: <1049196891.596.57.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <1049189944.1009.61.camel@localhost.localdomain>

On Tue, 2003-04-01 at 11:41, Antonino Daplas wrote:

> How I'm currently doing it with the extended vesafb driver is this:
>
> .../...

Ok, good. I'll investigate adapting that to radeonfb & aty128fb
at least.

Also, It would be very useful if we defined a standard ioctl to
retreive the EDID block from userland when available.

This would help some fbdev based apps (especially the maconlinux
emulator) and would be useful for some distro X autoconfig tools,
especially on platforms where X cannot get that EDID via it's
current mecanisms.

Actually, I would like 2 things:

 - Be able to know that the display has been detected as beeing a
TFT panel, and in this case, a "simple" way to retreive the
fb_var_screeninfo of the "native" panel mode. 

 - Returning the full EDID block when it exist

What do you think about adding some ioctl's for that ?

Ben.



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

  reply	other threads:[~2003-04-01 11:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31  9:53 [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01  0:07 ` Jon Smirl
2003-04-01  0:27   ` Kendall Bennett
2003-04-01  1:27     ` Antonino Daplas
2003-04-01  8:29       ` Benjamin Herrenschmidt
2003-04-01  9:41         ` Antonino Daplas
2003-04-01 11:34           ` Benjamin Herrenschmidt [this message]
2003-04-01 13:38             ` Antonino Daplas
2003-04-01 13:53               ` Benjamin Herrenschmidt
2003-04-01 15:32                 ` Antonino Daplas
2003-04-01 15:22               ` Jon Smirl
2003-04-01 16:25                 ` Antonino Daplas
2003-04-01 16:44                   ` Benjamin Herrenschmidt
2003-04-01 18:30                   ` Small API change Benjamin Herrenschmidt
2003-04-01 20:10                     ` Geert Uytterhoeven
2003-04-01 22:03                       ` Benjamin Herrenschmidt
2003-04-02 22:01                         ` James Simmons
2003-04-02 22:11                           ` Benjamin Herrenschmidt
2003-04-01  1:04   ` [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01  4:01     ` Jon Smirl
2003-04-01  9:41       ` Antonino Daplas
     [not found]         ` <20030401120835.GA30421@skunk.convergence.de>
2003-04-01 13:38           ` [directfb-dev] " Antonino Daplas

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=1049196891.596.57.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=KendallB@scitechsoft.com \
    --cc=adaplas@pol.net \
    --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).