public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] radeon frame buffer bug?
Date: Wed, 10 Jul 2002 06:51:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905751@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905750@msgid-missing>

>>>>> On Tue, 9 Jul 2002 21:24:39 -0700, David Mosberger <davidm@linux.hpl.hp.com> said:

  David> Normally I don't turn on the frame buffer code, but by
  David> coincidence, I had it turned on today on an Itanium 2 box
  David> with a Radeon card.  The kernel crashed late in the boot when
  David> the frame buffer driver was trying to blink the cursor (I
  David> think).  I took a quick look at the code and it seems to me
  David> that the Radeon driver is missing an ioremap().  The patch
  David> below isn't quite correct, as the second argument to
  David> ioremap() needs to be the size of the buffer (not sure what
  David> it is); of course, on ia64 the size doesn't really matter due
  David> to the identity mapping that we're using.

  David> Anybody who's more familiar with this code have any comments?

It turns out the real problem was due to the fact that the return
value from ioremap() got truncated to 32 bits (ouch!).

The patch below should fix that.  It appears that the vodoo frame
buffer code (sstfb.c) has an analogous truncation problem.

The patch below is for 2.4.18, but it seems 2.5 has the same issues.

	--david

--- drivers/video/radeonfb.c~	Tue Jul  9 19:06:15 2002
+++ drivers/video/radeonfb.c	Tue Jul  9 23:36:32 2002
@@ -258,8 +258,8 @@
 	u32 mmio_base_phys;
 	u32 fb_base_phys;
 
-	u32 mmio_base;
-	u32 fb_base;
+	void *mmio_base;
+	void *fb_base;
 
 	struct pci_dev *pdev;
 
@@ -800,8 +800,7 @@
 	}
 
 	/* map the regions */
-	rinfo->mmio_base = (u32) ioremap (rinfo->mmio_base_phys,
-				    		    RADEON_REGSIZE);
+	rinfo->mmio_base = ioremap (rinfo->mmio_base_phys, RADEON_REGSIZE);
 	if (!rinfo->mmio_base) {
 		printk ("radeonfb: cannot map MMIO\n");
 		release_mem_region (rinfo->mmio_base_phys,
@@ -947,8 +946,7 @@
 		}
 	}
 
-	rinfo->fb_base = (u32) ioremap (rinfo->fb_base_phys,
-				  		  rinfo->video_ram);
+	rinfo->fb_base = ioremap (rinfo->fb_base_phys, rinfo->video_ram);
 	if (!rinfo->fb_base) {
 		printk ("radeonfb: cannot map FB\n");
 		iounmap ((void*)rinfo->mmio_base);


      reply	other threads:[~2002-07-10  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  4:24 [Linux-ia64] radeon frame buffer bug? David Mosberger
2002-07-10  6:51 ` David Mosberger [this message]

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=marc-linux-ia64-105590701905751@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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