From: Antonino Daplas <adaplas@pol.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 21:38:49 +0800 [thread overview]
Message-ID: <1049203284.1050.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1049196891.596.57.camel@zion.wanadoo.fr>
On Tue, 2003-04-01 at 19:34, Benjamin Herrenschmidt wrote:
> 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.
I'm planning to submit a patch to James to add more functionality to
fbmon.c, fbmon.c should have these at least:
1. struct fb_videomode* fb_create_modedb(unsigned char *edid)
- this will create a mode database that can be used with fb_find_mode()
2. fb_destroy_modedb(struct fb_videomode *modedb)
- destroy mode database
3. fb_get_monitor_limits(struct fb_monspecs *specs, unsigned char *edid)
- place monitor operating limits to specs
4. fb_validate_mode(struct fb_var_screeninfo *var, struct fb_info *info)
- validate mode timings in var
5. fb_get_mode(int flags, int val, struct fb_var_screeninfo *var, struct
fb_info *info)
- compute mode timings using GTF (refresh driven, hsync driven, pixclock
driven, or maximized refresh) and place result in var
#4 and #5 are already in fbmon.c
> Also, It would be very useful if we defined a standard ioctl to
> retreive the EDID block from userland when available.
>
I have no problem with this, and this was discussed some time ago, but
nothing was really decided. It's actually a very nice fallback solution
if there's really no method to get the EDID.
> 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 ?
>
It's okay by me.
Tony
-------------------------------------------------------
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/
next prev parent reply other threads:[~2003-04-01 13:43 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
2003-04-01 13:38 ` Antonino Daplas [this message]
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=1049203284.1050.14.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=KendallB@scitechsoft.com \
--cc=benh@kernel.crashing.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).