From: Benjamin Herrenschmidt <bh40@calva.net>
To: Daniel Jacobowitz <drow@false.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb.c bug in VRAM bank2 check if bank1
Date: Sat, 11 Sep 1999 11:23:23 +0200 [thread overview]
Message-ID: <19990911112323.032168@smtp.calvacom.fr> (raw)
In-Reply-To: <19990910161322.A1674@them.org>
>I have a bunch of information on this lying around, and most of my
>other kernel problems seem to be resolved now. I'm in the process of
>upgrading to current vger; if it succeeds, I'll try to merge all
>pending controlfb stuff tomorrow.
I also have a pair of crazy 8500 who have 2Mb of VRAM but in bank2 (they
don't work if the VRAM is moved to bank1, even under MacOS). The current
controlfb appears to work well. Send me your merge results, I'll test on
one of those weird machines Monday.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-11 9:23 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
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 [this message]
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=19990911112323.032168@smtp.calvacom.fr \
--to=bh40@calva.net \
--cc=drow@false.org \
--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.