From: Jesse Barnes <jbarnes@sgi.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] small fix for aty128fb support on ia64
Date: Fri, 14 Mar 2003 13:48:27 -0800 [thread overview]
Message-ID: <20030314214827.GC1037@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303081510380.28479-100000@phoenix.infradead.org>
Here's a patch I had to use on ia64. The framebuffer worked nicely,
but it looks like X doesn't restore the state correctly when I switch
back to an fb console, so I just got a blank screen.
Maybe you can think of a better way to address the #ifdef issue, it
certainly looks bad...
Thanks,
Jesse
--- linux-2.5.64-ia64-sn/drivers/video/aty128fb.c Tue Mar 4 19:29:18 2003
+++ linux-2.5.64-ia64/drivers/video/aty128fb.c Fri Mar 14 12:12:19 2003
@@ -1448,7 +1448,10 @@
}
}
#endif /* CONFIG_ALL_PPC */
+#if defined(CONFIG_PMAC_PBOOK) || defined(CONFIG_MTRR) || \
+ defined(CONFIG_ALL_PPC)
else
+#endif /* this is getting ugly */
mode_option = this_opt;
}
return 0;
@@ -1709,7 +1712,7 @@
"Guessing...\n");
else {
printk(KERN_INFO "aty128fb: Rage128 BIOS located at "
- "segment %4.4X\n", (unsigned int)bios_seg);
+ "segment %4.4lX\n", (unsigned long)bios_seg);
aty128_get_pllinfo(par, bios_seg);
}
#endif
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
prev parent reply other threads:[~2003-03-14 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 0:26 [BK updates] James Simmons
2003-03-08 1:46 ` Antonino Daplas
2003-03-08 22:02 ` Antonino Daplas
2003-03-08 14:40 ` Geert Uytterhoeven
2003-03-08 15:11 ` James Simmons
2003-03-14 21:48 ` Jesse Barnes [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=20030314214827.GC1037@sgi.com \
--to=jbarnes@sgi.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).