linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Branden Robinson <branden@debian.org>
Cc: Clint Adams <schizo@debian.org>,
	226973@bugs.debian.org, Geert Uytterhoeven <geert@linux-m68k.org>,
	Sven Luther <sven.luther@wanadoo.fr>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Bug#226973: Re: Bug#226973: xserver-xfree86: [glint] second card at wrong resolution
Date: Thu, 1 Apr 2004 08:51:02 +0200	[thread overview]
Message-ID: <20040401065102.GB637@lambda> (raw)
In-Reply-To: <20040401064122.GH16695@deadbeast.net>

On Thu, Apr 01, 2004 at 01:41:22AM -0500, Branden Robinson wrote:
> On Wed, Mar 31, 2004 at 11:10:02AM -0500, Clint Adams wrote:
> > > If your graphics controller is limited by memory bandwidth, the maximum pixel
> > > clock depends on the number of bits per pixels, since larger pixels mean more
> > > memory bandwidth.
> > 
> > I'm unclear on the differences between 24 bpp and 32 bpp and how this
> > relates to internal pixmap format.
> 
> Some hardware uses a "packed-pixel format"; that is, 4 24-bit pixels are
> encoded in 3 32-bit words (what Intel calls "DWORDS", I think).

Yeah, DWORDS, because they are stil living in the era of 16bit hardware :)

> Other hardware tosses in a zero byte with every 32-bit "DWORD" transfer.

Well, the permedia2 should support both formats, depending on chosen
mode.

Friendly,

Sven Luther


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-04-01  6:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040109163119.GA10151@scowler.net>
     [not found] ` <20040112121558.GA24511@iliana>
     [not found]   ` <20040112215543.GB2150@scowler.net>
2004-01-13  7:41     ` Bug#226973: xserver-xfree86: [glint] second card at wrong resolution Sven Luther
2004-01-13 15:40       ` Clint Adams
2004-01-13 16:02         ` Sven Luther
2004-01-14 21:06           ` Clint Adams
2004-01-14 21:12             ` Sven Luther
2004-01-14 21:17               ` Clint Adams
2004-01-14 21:12           ` Clint Adams
2004-01-14 21:16             ` Sven Luther
2004-01-15 21:55               ` Clint Adams
2004-01-15 22:47               ` Clint Adams
2004-03-30 15:32               ` Clint Adams
2004-03-30 16:57                 ` Sven Luther
2004-03-30 23:02                   ` Clint Adams
2004-03-30 23:08                     ` Sven Luther
2004-03-31  8:12                       ` Geert Uytterhoeven
2004-03-31 16:10                         ` Clint Adams
2004-04-01  6:41                           ` Bug#226973: " Branden Robinson
2004-04-01  6:51                             ` Sven Luther [this message]
2004-04-01 16:41                               ` Branden Robinson

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=20040401065102.GB637@lambda \
    --to=sven.luther@wanadoo.fr \
    --cc=226973@bugs.debian.org \
    --cc=branden@debian.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=schizo@debian.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 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).