linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Takashi Oe <toe@unlinfo.unl.edu>,
	linuxppc-dev@lists.linuxppc.org,
	Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: linuxppc-user@lists.linuxppc.org
Subject: Re: XServer for controlfb (fix)
Date: Wed, 5 May 1999 12:55:31 +0200	[thread overview]
Message-ID: <19990505125531.028926@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.990430114242.412A-100000@selq119.unl.edu>


This patch seems to fix the problem with controlfb and x servers when
vram is in bank2 only (my 8500 video doesn't work at all, even under
MacOS, when I put the vram in bank 1):

--- linux.orig/drivers/video/controlfb.c	Mon Feb  8 14:29:33 1999
+++ linux.mol/drivers/video/controlfb.c	Wed May  5 12:45:05 1999
@@ -720,9 +720,11 @@
 	p->total_vram = (bank1 + bank2) * 0x200000;
 	/* If we don't have bank 1 installed, we hope we have bank 2 :-) */
 	p->control_use_bank2 = !bank1;
-	if (p->control_use_bank2)
+	if (p->control_use_bank2) {
 		p->frame_buffer += 0x600000;
-
+		p->frame_buffer_phys += 0x600000;
+	}
+	
 	init_control(p);
 }
 

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>




[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

           reply	other threads:[~1999-05-05 10:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.3.96LJ1.1b7.990430114242.412A-100000@selq119.unl.edu>]

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=19990505125531.028926@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.org \
    --cc=toe@unlinfo.unl.edu \
    /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).