linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: Antonino Daplas <adaplas@pol.net>,
	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: Tue, 1 Apr 2003 07:22:09 -0800 (PST)	[thread overview]
Message-ID: <20030401152209.91116.qmail@web14913.mail.yahoo.com> (raw)
In-Reply-To: <1049203284.1050.14.camel@localhost.localdomain>

--- Antonino Daplas <adaplas@pol.net> wrote:
> 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
>

Wouldn't it be better to make fb_get_mode only return
the list of valid modes based on the hardware and
monitor (if available) combination rather than letting
the app sort it out?

We could then make a new IOCTL fb_get_hwmode for
returning the card's capabilities if more detail is
desired.


=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://platinum.yahoo.com


-------------------------------------------------------
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/

  parent reply	other threads:[~2003-04-01 15:22 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
2003-04-01 13:53               ` Benjamin Herrenschmidt
2003-04-01 15:32                 ` Antonino Daplas
2003-04-01 15:22               ` Jon Smirl [this message]
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=20030401152209.91116.qmail@web14913.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=KendallB@scitechsoft.com \
    --cc=adaplas@pol.net \
    --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).