From: Michel Lanners <mlan@cpu.lu>
To: ldl@chpc.utah.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb.c bug in VRAM bank2 check if bank1
Date: Fri, 10 Sep 1999 20:33:11 +0200 (CEST) [thread overview]
Message-ID: <199909101833.UAA17210@piglet.cpu.lu> (raw)
In-Reply-To: <37D929E4.205A04B8@chpc.utah.edu>
On 10 Sep, this message from Lou Langholtz echoed through cyberspace:
> After getting an extra 2MB VRAM for my PowerMac7500 and seeing that only
> 2MB were still being recognized (despite having just added the 2MB to
> total to 4MB VRAM), I dug into the controlfb.c code from 2.2.11 and
> 2.2.12 and made the following changes to get all 4MB VRAM recognized:
> < out_8(&p->frame_buffer[0x600000], 0xa5);
> < out_8(&p->frame_buffer[0x600001], 0x38);
> ---
>> out_8(&p->frame_buffer[0x200000], 0xa5);
>> out_8(&p->frame_buffer[0x200001], 0x38);
Hmm, if I remember right, there have been half a dozen patch pairs that
changed 0x600000 to 0x200000 and back over the years ;-)
I guess it's time to clear thgis up once and for all. By the way, I do
have 4 MB of VRAM, and all of it is detected with the current version
of controlfb.....
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-10 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 15:55 controlfb.c bug in VRAM bank2 check if bank1 Lou Langholtz
1999-09-10 17:08 ` Lou Langholtz
1999-09-10 18:33 ` Michel Lanners [this message]
1999-09-12 16:58 ` Lou Langholtz
1999-09-13 18:13 ` Michel Lanners
1999-09-15 15:14 ` Lou Langholtz
1999-10-12 7:07 ` Lou Langholtz
1999-10-12 7:23 ` Bizarre g++ problem Patrik Jonsson
1999-10-12 6:49 ` controlfb.c bug in VRAM bank2 check if bank1 Lou Langholtz
1999-10-12 14:50 ` Daniel Jacobowitz
1999-10-12 15:36 ` Lou Langholtz
1999-10-13 6:30 ` Geert Uytterhoeven
1999-09-11 10:51 ` Brad Boyer
1999-09-10 20:13 ` Daniel Jacobowitz
1999-09-11 9:23 ` Benjamin Herrenschmidt
1999-09-12 18:10 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
1999-09-15 17:05 Kevin_Hendricks
1999-09-15 18:26 ` Kevin Puetz
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=199909101833.UAA17210@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=ldl@chpc.utah.edu \
--cc=linuxppc-dev@lists.linuxppc.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.