linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Sven Luther <sven.luther@wanadoo.fr>
Subject: Re: monitor detection through ddc/edid stuff.
Date: Sun, 12 Sep 2004 18:11:01 +0800	[thread overview]
Message-ID: <200409121811.01426.adaplas@hotpop.com> (raw)
In-Reply-To: <20040912100407.GB27133@pegasos>

On Sunday 12 September 2004 18:04, Sven Luther wrote:
> On Sun, Sep 12, 2004 at 05:32:44PM +0800, Antonino A. Daplas wrote:
> > On Sunday 12 September 2004 16:42, Sven Luther wrote:
> > > Now, another question which has me baffled. In set_par, i set the video
> > > mode for the card, but i only seem to have access to the bpp, and not
> > > the actual depth. Since i can distinguish between depth 15 (5551) and
> > > 16 (5650), as well as between depth 24 (8888) and 30 (AAA2), where do i
> > > get the information concerning the actual depth used from ?
> >
> > var->green.length
>
> So, on a 5551 more, i should get :
>
>   var->green.length + var->red.length + var->blue.length == 15
>
> right ?

Yes, sorry for being cryptic.  Only if (visual == truecolor ||
visual == directcolor), otherwise color depth = var->green.length.  If you
are using at least a 2.6.8 kernel, there is a new helper in
drivers/video/fbmem.c that you can check out:

int fb_get_color_depth(struct fb_info *)

Tony




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

  reply	other threads:[~2004-09-12 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10 11:16 monitor detection through ddc/edid stuff Sven Luther
2004-09-10 11:44 ` Sven Luther
2004-09-11 15:36 ` Kronos
2004-09-11 16:52   ` Jon Smirl
2004-09-12  8:42   ` Sven Luther
2004-09-12  9:32     ` Antonino A. Daplas
2004-09-12 10:04       ` Sven Luther
2004-09-12 10:11         ` Antonino A. Daplas [this message]
2004-09-12 10:31           ` Sven Luther
2004-09-12 13:54           ` Sven Luther
2004-09-12 21:00             ` Antonino A. Daplas
2004-09-12 14:36           ` Sven Luther
2004-09-12 21:16             ` Antonino A. 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=200409121811.01426.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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).