All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kars de Jong <jongk@linux-m68k.org>,
	Linux/m68k kernel mailing list <linux-m68k@lists.linux-m68k.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: HP300 support checked in
Date: Wed, 14 Jul 2004 16:38:43 +0800	[thread overview]
Message-ID: <200407141638.45154.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0407140957470.17289@waterleaf.sonytel.be>

On Wednesday 14 July 2004 16:00, Geert Uytterhoeven wrote:
> On Wed, 14 Jul 2004, Antonino A. Daplas wrote:
> > On Monday 12 July 2004 15:25, Geert Uytterhoeven wrote:
> > > On Sun, 11 Jul 2004, Kars de Jong wrote:
> > > > Support for <8 bit framebuffers is probably broken. I don't know how
> > > > I'm going to support them yet. It used to be "special-cased" in
> > > > drivers/video/fbcon.c.
> > > >
> > > > They are laid out in memory like normal 8 bit chunky framebuffers,
> > > > but the upper bits are basically ignored.
> > > >
> > > > So for blitting purposes the bits_per_pixel == 8 code should be used,
> > > > but just setting bits_per_pixel to 8 doesn't work because then the
> > > > amount of colours is assumed to be 256.
> > > >
> > > > I think we basically need to distinguish between bpp and depth.
> > >
> > > What are the possible values of depth? Just 1 (monochrome)? Or also 4
> > > (16 colors)?
> > >
> > > If it's just 1 (monochrome), you can probably get away with setting
> > > var.bits_per_pixel = 256 and fix.visual = FB_VISUAL_MONO01 (or MONO10).
> >
> > Or we can use the fields in var->green, var->red, var->blue, ie,  to
> > describe a 4-color 8-bit chunky framebuffer:
> >
> > var->red.length = 2;
> > var->red.offset = 0;
> > var->green = var->blue = var->red.
> > var->bits_per_pixel = 8;
>
> This breaks something different, since for pseudocolor visuals, the
> *.lengths indicate the sizes of the CLUT entries (e.g. 8 bit per component
> for modern 24-bit color, 6 bit for VGA-style 18-bit color).

I don't know.  For pseudocolor, color depth == CLUT size.  So if we check if all
lengths are equal and if all offsets are equal to zero, then color depth = CLUT size. 
Otherwise, color depth = red.length + green.length + blue.length. Transparency 
can be ignored for now.
  
Tony





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-07-14  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1089576608.2555.35.camel@kars.perseus.home>
2004-07-12  7:25 ` HP300 support checked in Geert Uytterhoeven
2004-07-14  7:32   ` Antonino A. Daplas
2004-07-14  8:00     ` Geert Uytterhoeven
2004-07-14  8:38       ` Antonino A. Daplas [this message]
2004-07-14  9:05         ` Geert Uytterhoeven

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=200407141638.45154.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=geert@linux-m68k.org \
    --cc=jongk@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-m68k@lists.linux-m68k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.