linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] atyfb (2.6): Memory type correction
@ 2004-05-07  2:11 Ville Syrjälä
  2004-05-07  8:36 ` Geert Uytterhoeven
  0 siblings, 1 reply; 3+ messages in thread
From: Ville Syrjälä @ 2004-05-07  2:11 UTC (permalink / raw)
  To: linux-fbdev-devel

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

This patch changes the memory type message to match reality. This agrees 
with both my hardware and the Mobility register specs.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/

[-- Attachment #2: atyfb-2.6-mem_type.patch --]
[-- Type: text/plain, Size: 916 bytes --]

--- linux/drivers/video/aty/atyfb_base.c.orig	2004-05-07 03:48:44.109865088 +0300
+++ linux/drivers/video/aty/atyfb_base.c	2004-05-07 03:49:33.872300048 +0300
@@ -457,9 +457,9 @@
 #endif /* CONFIG_FB_ATY_GX */
 #ifdef CONFIG_FB_ATY_CT
 static char ram_edo[] __initdata = "EDO";
-static char ram_sdram[] __initdata = "SDRAM";
-static char ram_sgram[] __initdata = "SGRAM";
-static char ram_wram[] __initdata = "WRAM";
+static char ram_sdram[] __initdata = "SDRAM (1:1)";
+static char ram_sgram[] __initdata = "SGRAM (1:1)";
+static char ram_sdram32[] __initdata = "SDRAM (2:1) (32-bit)";
 static char ram_off[] __initdata = "OFF";
 #endif /* CONFIG_FB_ATY_CT */
 
@@ -476,7 +476,7 @@
 #ifdef CONFIG_FB_ATY_CT
 static char *aty_ct_ram[8] __initdata = {
 	ram_off, ram_dram, ram_edo, ram_edo,
-	ram_sdram, ram_sgram, ram_wram, ram_resv
+	ram_sdram, ram_sgram, ram_sdram32, ram_resv
 };
 #endif /* CONFIG_FB_ATY_CT */
 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] atyfb (2.6): Memory type correction
  2004-05-07  2:11 [PATCH] atyfb (2.6): Memory type correction Ville Syrjälä
@ 2004-05-07  8:36 ` Geert Uytterhoeven
  2004-05-07 11:37   ` Ville Syrjälä
  0 siblings, 1 reply; 3+ messages in thread
From: Geert Uytterhoeven @ 2004-05-07  8:36 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: Linux Frame Buffer Device Development

On Fri, 7 May 2004, Ville [iso-8859-1] Syrjälä wrote:
> This patch changes the memory type message to match reality. This agrees
> with both my hardware and the Mobility register specs.

I took the values from the RAGE II+ manual. So ATI recycled the WRAM value for
Mobility? Unless they never actually made boards with WRAM.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] atyfb (2.6): Memory type correction
  2004-05-07  8:36 ` Geert Uytterhoeven
@ 2004-05-07 11:37   ` Ville Syrjälä
  0 siblings, 0 replies; 3+ messages in thread
From: Ville Syrjälä @ 2004-05-07 11:37 UTC (permalink / raw)
  To: Linux Frame Buffer Device Development

On Fri, May 07, 2004 at 10:36:50AM +0200, Geert Uytterhoeven wrote:
> On Fri, 7 May 2004, Ville [iso-8859-1] Syrjälä wrote:
> > This patch changes the memory type message to match reality. This agrees
> > with both my hardware and the Mobility register specs.
> 
> I took the values from the RAGE II+ manual. So ATI recycled the WRAM value for
> Mobility? Unless they never actually made boards with WRAM.

My Rage Pro manual lists WRAM in CONFIG_STAT2.CFG_MEM_TYPEb. And that's 
the only place where WRAM in mentioned as a valid memory type in my 
manuals. Also the values of CFG_MEM_TYPEb look like the xor of 
CONFIG_STAT0.CFG_MEM_TYPE except that WRAM is CFG_MEM_TYPEb=001 and 
CFG_MEM_TYPE=110 is listed as a reserved value.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-05-07 11:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-07  2:11 [PATCH] atyfb (2.6): Memory type correction Ville Syrjälä
2004-05-07  8:36 ` Geert Uytterhoeven
2004-05-07 11:37   ` Ville Syrjälä

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).