From: Jim Hague <jim.hague@acm.org>
To: Marcelo Ramos <mramos@montevideo.com.uy>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: pm2fb fixes
Date: Wed, 21 Apr 2004 11:14:42 +0100 (BST) [thread overview]
Message-ID: <XFMail.20040421111442.jim.hague@acm.org> (raw)
In-Reply-To: <20040421015118.2caa6e99@zerocool>
On 21-Apr-2004 Marcelo Ramos wrote:
>> This patch fixes this bug, and a silly problem in pm2fb_blank(). There's
>> also some minor tidying.
>
> I applied the patch and now the kernel oops is gone. How can I change the
> resolution? If I don't specify the mode then i get 640x480-60 but if i use
> video=pm2fb:mode:1024x768 (or any other resolution) I get 640x400-70. am I
> passing the driver the argument with a wrong format?
The 2.6 version of pm2fb currently only has three possible arguments, 'mode',
'lowvsync' and 'lowhsync'. I think I'm the only person needing the last two.
When compiled in to the kernel, the argument syntax imitates other 2.6 drivers.
Arguments are comma separated, and any argument that isn't 'lowvsync' or
'lowhsync' is assumed to be a modedb specification,'<hres>x<vres>-<refresh>'.
You probably want:
video=pm2fb:1024x768-70
--
Jim Hague - jim.hague@acm.org Never trust a computer you can't lift.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-21 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 23:46 pm2fb fixes Jim Hague
2004-04-21 4:51 ` Marcelo Ramos
2004-04-21 10:14 ` Jim Hague [this message]
2004-04-21 16:26 ` Marcelo Ramos
2004-04-21 18:21 ` Jim Hague
2004-04-21 20:22 ` Marcelo Ramos
2004-04-22 13:43 ` Marcelo Ramos
2004-04-22 15:36 ` Jim Hague
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=XFMail.20040421111442.jim.hague@acm.org \
--to=jim.hague@acm.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=mramos@montevideo.com.uy \
/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).