From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Carlo E. Prelz" <fluido@fluido.as>
Cc: 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 12:49:38 +0200 [thread overview]
Message-ID: <1066387778.661.226.camel@gaston> (raw)
In-Reply-To: <20031017100412.GA1639@casa.fluido.as>
> Ok. I got the code (it is mvista, not mivsta...). My card is
> recognized without modifications:
Good.
> Then, when changing to 1280x1024, with command
>
> /usr/sbin/fbset -depth 32 1280x1024-60
>
> the actual console changes correctly, but when switching to other VCs,
> the monitor again complains saying it gets bad frequencies: 103.1 kHz
> horizontal and 197.8 Hz vertical.
Not sure what's up here. The driver is quite passive regarding
the mode for other VCs, it sort of expect the fbcon layer do pick up
the default mode and use it for other consoles. I'm not sure what's
wrong here.
In a more general way, I really lack the ability to change the console
size with fbset like I could do with 2.4. I don't know if James revived
that feature in his latest patches though. The stty thing isn't very
reliable imho. Especially on monitors that don't like the standard
modedb.
> And on a similar topic, could you write a couple of examples about how
> to use the parameters included in radeon_base.c? I am thinking
> especially of the "mirror" and "monitor_layout" parameters, that I
> believe would allow me to use the two or three video outputs of the
> card independently. I currently read
I have to see what I'll do of these parameters first. For now, the
driver only really use the first head. I haven't yet implemented support
for the second one, though it's on my list of things to do.
> 0 ATI Radeon Yd
>
> in /proc/fb. I should read two or three lines there, I believe...
Well... /proc is evil :)
next prev parent reply other threads:[~2003-10-17 10:49 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 [this message]
2003-10-17 11:10 ` Carlo E. Prelz
2003-10-17 11:16 ` Benjamin Herrenschmidt
2003-10-17 14:44 ` [Linux-fbdev-devel] " Kronos
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=1066387778.661.226.camel@gaston \
--to=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).