All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zajicek <santiago@mail.cz>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Bug in vga16fb?
Date: Thu, 6 Apr 2006 16:39:01 +0200	[thread overview]
Message-ID: <20060406143901.GA9683@localhost.localdomain> (raw)
In-Reply-To: <44351E1A.8050404@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

On Thu, Apr 06, 2006 at 09:56:42PM +0800, Antonino A. Daplas wrote:
> 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

I think that this bit says something different - ordering of bits inside
one color component. This is OK for all VGA (MSB bit of color index is
left), i hope.

Problem is in ordering of pixels inside a byte, which is completely
orthogonal to bitplane.msb_right-ness.

But maybe i misunderstood of meaning of 
var->{red|green|blue|transp}.msb_right ...


-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@mail.cz, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2006-04-06 14:39 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
2006-04-06 14:39       ` Ondrej Zajicek [this message]
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=20060406143901.GA9683@localhost.localdomain \
    --to=santiago@mail.cz \
    --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 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.