From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Clint Adams <schizo@debian.org>,
226973@bugs.debian.org,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: Bug#226973: xserver-xfree86: [glint] second card at wrong resolution
Date: Wed, 31 Mar 2004 10:12:45 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.58.0403311011400.22944@waterleaf.sonytel.be> (raw)
In-Reply-To: <20040330230829.GA5257@lambda>
On Wed, 31 Mar 2004, Sven Luther wrote:
> On Tue, Mar 30, 2004 at 06:02:03PM -0500, Clint Adams wrote:
> > > I believe that the cloack is different for 8bpp and 16 or 24 bpp, don't
> > > remember exactly. At 8bpp, the max clock range is 230Mhz in the driver i
> > > think. You looked at it, you have the hardware, you just have become the
> > > resident expert on this issue :).
> >
> > Ahh. I tried increasing the 32bpp number to 150MHz, and was successfully
> > able to use a mode at 135MHz. I am confused as to why the Pixmap setting
> > affects the ramdac frequency. Is this a mistake or am I misunderstanding
> > something? Would it be okay to set the maximum based on depth instead
> > of bitsPerPixel, or is bitsPerPixel wrong if it's set to 32 at a plain
> > 24-bit depth?
>
> I would have to look in the specs, but i believe the ramdac is only able
> to push less pixels if those are of 16 or 32 bpp. This is the case for
> all 3Dlabs chips prior to the permedia3. Look at the part in glint_driver.c
> where these values are set. I have no explanation also, since my
> involvement was with the permedia3, so maybe ask Alan Hourihane about
> it.
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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-31 8:12 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 [this message]
2004-03-31 16:10 ` Clint Adams
2004-04-01 6:41 ` Bug#226973: " Branden Robinson
2004-04-01 6:51 ` Sven Luther
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=Pine.GSO.4.58.0403311011400.22944@waterleaf.sonytel.be \
--to=geert@linux-m68k.org \
--cc=226973@bugs.debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=schizo@debian.org \
--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 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.