All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: santiago@mail.cz
Subject: Re: Bug in vga16fb?
Date: Thu, 06 Apr 2006 21:56:42 +0800	[thread overview]
Message-ID: <44351E1A.8050404@gmail.com> (raw)
In-Reply-To: <20060406073713.GA3051@localhost.localdomain>

Ondrej Zajicek wrote:
> On Thu, Apr 06, 2006 at 12:48:48AM +0200, Petr Vandrovec wrote:
>> Ondrej Zajicek wrote:
> 
> Even if we find some possibility to autodetect what hardware does (or in
> case of another, non-VGA hardware using CFB4 mode) there would be
> problem that driver cannot say it to userspace (or generic kernel
> functions like cfb_imageblit). Maybe there should be some flag in
> type_aux specifying whether given packed pixel mode is LSB-first or
> MSB-first (relevant only for bpp % 8 != 0) ?
> 

var->{red|green|blue|transp}.msb_right

This field is currently ignored by fbcon, but you can use this field to
inform userspace what you want.

And once a driver uses this flag, we can probably alter the drawing
functions to not ignore this flag.

Tony


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-04-06 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 20:40 Bug in vga16fb? Ondrej Zajicek
2006-04-05 22:48 ` Petr Vandrovec
2006-04-06  7:37   ` Ondrej Zajicek
2006-04-06 13:56     ` Antonino A. Daplas [this message]
2006-04-06 14:39       ` Ondrej Zajicek
2006-04-06 16:44         ` 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=44351E1A.8050404@gmail.com \
    --to=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=santiago@mail.cz \
    /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.