From: Kronos <kronos@kronoz.cjb.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Carlo E. Prelz" <fluido@fluido.as>,
James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
Date: Fri, 17 Oct 2003 16:44:30 +0200 [thread overview]
Message-ID: <20031017144430.GB463@dreamland.darkstar.lan> (raw)
In-Reply-To: <1066389397.662.228.camel@gaston>
Il Fri, Oct 17, 2003 at 01:16:37PM +0200, Benjamin Herrenschmidt ha scritto:
>
> > Aha... So, from what you know, is there any possibility (fb, X, X with
> > ATI drivers, anything else) to use the video output (or the second
> > head) of radeon cards under Linux? And have you tried your drivers
> > with 2 cards (one PCI and one AGP)?
>
> I haven't tried with 2 cards, no. It's possible to do dual head
> with XFree.
>
> > And in all cases, why is parameter "mode" not working? If I could set
> > 1280x1024-32@60 from Lilo, most of my problems would be solved...
>
> I'll check that out. The new module parameter thing isn't that good,
> I think I'll revive the old stuff for a while.
The following patch restores the setup function so that radeonfb can be
given options like other fb drivers. There's also a small typo fix
(force_dfp -> panel_yres).
===== drivers/video/fbmem.c 1.71 vs edited =====
--- 1.71/drivers/video/fbmem.c Sun Sep 7 23:07:57 2003
+++ edited/drivers/video/fbmem.c Fri Oct 17 16:37:55 2003
@@ -220,7 +220,7 @@
{ "tdfxfb", tdfxfb_init, tdfxfb_setup },
#endif
#ifdef CONFIG_FB_RADEON
- { "radeonfb", radeonfb_init, NULL },
+ { "radeonfb", radeonfb_init, radeonfb_setup },
#endif
#ifdef CONFIG_FB_CONTROL
{ "controlfb", control_init, control_setup },
===== drivers/video/aty/radeon_base.c 1.11 vs edited =====
--- 1.11/drivers/video/aty/radeon_base.c Mon Oct 13 17:47:12 2003
+++ edited/drivers/video/aty/radeon_base.c Fri Oct 17 16:37:31 2003
@@ -2378,6 +2378,40 @@
pci_unregister_driver (&radeonfb_driver);
}
+int __init radeonfb_setup (char *options)
+{
+ char *this_opt;
+
+ if (!options || !*options)
+ return 0;
+
+ while ((this_opt = strsep (&options, ",")) != NULL) {
+ if (!*this_opt)
+ continue;
+
+ if (!strncmp(this_opt, "noaccel", 7)) {
+ noaccel = 1;
+ } else if (!strncmp(this_opt, "mirror", 6)) {
+ mirror = 1;
+ } else if (!strncmp(this_opt, "force_dfp", 9)) {
+ force_dfp = 1;
+ } else if (!strncmp(this_opt, "panel_yres:", 11)) {
+ panel_yres = simple_strtoul((this_opt+11), NULL, 0);
+ } else if (!strncmp(this_opt, "nomtrr", 6)) {
+ nomtrr = 1;
+ } else if (!strncmp(this_opt, "nomodeset", 9)) {
+ nomodeset = 1;
+ } else if (!strncmp(this_opt, "force_measure_pll", 17)) {
+ force_measure_pll = 1;
+ } else if (!strncmp(this_opt, "ignore_edid", 11)) {
+ ignore_edid = 1;
+ } else
+ mode_option = this_opt;
+ }
+ return 0;
+}
+
+
#ifdef MODULE
module_init(radeonfb_init);
module_exit(radeonfb_exit);
@@ -2405,6 +2439,6 @@
MODULE_PARM_DESC(nomtrr, "bool: disable use of MTRR registers");
#endif
module_param(panel_yres, int, 0);
-MODULE_PARM_DESC(force_dfp, "int: set panel yres");
+MODULE_PARM_DESC(panel_yres, "int: set panel yres");
module_param(mode_option, charp, 0);
MODULE_PARM_DESC(mode_option, "Specify resolution as \"<xres>x<yres>[-<bpp>][@<refresh>]\" ");
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
I went to God just to see
And I was looking at me
Saw heaven and hell were lies
When I'm God everyone dies
next prev parent reply other threads:[~2003-10-17 14:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 22:59 FBDEV 2.6.0-test7 updates James Simmons
2003-10-15 23:17 ` Andrew Morton
2003-10-15 23:22 ` James Simmons
2003-10-15 23:20 ` Andrew Morton
2003-10-15 23:27 ` James Simmons
2003-10-16 9:19 ` Carlo E. Prelz
2003-10-16 9:29 ` Sven Luther
2003-10-17 16:48 ` James Simmons
2003-10-16 10:00 ` Benjamin Herrenschmidt
2003-10-16 10:19 ` Carlo E. Prelz
2003-10-16 10:41 ` Benjamin Herrenschmidt
2003-10-16 10:48 ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-16 10:42 ` Benjamin Herrenschmidt
2003-10-17 10:04 ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-17 10:49 ` Benjamin Herrenschmidt
2003-10-17 11:10 ` Carlo E. Prelz
2003-10-17 11:16 ` Benjamin Herrenschmidt
2003-10-17 14:44 ` Kronos [this message]
2003-10-17 17:29 ` James Simmons
2003-10-18 21:28 ` [Linux-fbdev-devel] " Pavel Machek
2003-10-17 17:40 ` James Simmons
2003-10-17 14:26 ` [Linux-fbdev-devel] " Kronos
2003-10-16 21:06 ` Otto Solares
2003-10-17 10:30 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 16:52 ` James Simmons
2003-10-17 19:34 ` [Linux-fbdev-devel] " Jon Smirl
2003-10-17 19:50 ` Dave Jones
2003-10-17 22:42 ` Jon Smirl
2003-10-16 0:24 ` Michel Dänzer
2003-10-16 8:19 ` Benjamin Herrenschmidt
2003-10-17 16:45 ` [Linux-fbdev-devel] " James Simmons
2003-10-16 5:08 ` Jan De Luyck
2003-10-17 16:44 ` James Simmons
2003-10-16 5:17 ` Jan De Luyck
2003-10-16 10:44 ` Adrian Bunk
2003-10-16 17:48 ` James Simmons
2003-10-16 19:58 ` Geert Uytterhoeven
2003-10-16 20:40 ` [Linux-fbdev-devel] " Sam Ravnborg
2003-10-17 11:18 ` Benjamin Herrenschmidt
2003-10-17 17:25 ` [Linux-fbdev-devel] " James Simmons
2003-10-17 17:45 ` Torrey Hoffman
2003-10-17 17:23 ` [Linux-fbdev-devel] " James Simmons
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=20031017144430.GB463@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=benh@kernel.crashing.org \
--cc=fluido@fluido.as \
--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).