Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] radeonfb ATI 9100IGP shared main memory / VRAM
Date: Thu, 22 Dec 2005 09:56:50 +1100	[thread overview]
Message-ID: <1135205811.10035.138.camel@gaston> (raw)
In-Reply-To: <20051221203706.GR4495@sunbeam.de.gnumonks.org>

On Wed, 2005-12-21 at 21:37 +0100, Harald Welte wrote:

> I've altered radeon_base.c with a special exception for this chip, see
> the patch below.  Now everything works like a charm.

Hi !

Actually, this isn't the right way, the PCI resource might be bigger
than the RAM assigned to the IGP chip. I'll try to get something better
for you. The thing to do looks like that in X:

    else if ((info->ChipFamily == CHIP_FAMILY_RS100) ||
	     (info->ChipFamily == CHIP_FAMILY_RS200) ||
	     (info->ChipFamily == CHIP_FAMILY_RS300)) {
        CARD32 tom = INREG(RADEON_NB_TOM);

	pScrn->videoRam = (((tom >> 16) -
			    (tom & 0xffff) + 1) << 6);

	OUTREG(RADEON_CONFIG_MEMSIZE, pScrn->videoRam * 1024);

With
	#define RADEON_NB_TOM                       0x15c

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

      parent reply	other threads:[~2005-12-21 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 20:37 [PATCH] radeonfb ATI 9100IGP shared main memory / VRAM Harald Welte
2005-12-21 22:26 ` Harald Welte
2005-12-23  0:40   ` Benjamin Herrenschmidt
2005-12-21 22:56 ` Benjamin Herrenschmidt [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=1135205811.10035.138.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=laforge@gnumonks.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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