Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Marcelo Ramos <mramos@montevideo.com.uy>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: pm2fb fixes
Date: Wed, 21 Apr 2004 13:26:39 -0300	[thread overview]
Message-ID: <20040421132639.1d87ba1b@zerocool> (raw)
In-Reply-To: <XFMail.20040421111442.jim.hague@acm.org>

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

El (On) Wed, 21 Apr 2004 11:14:42 +0100 (BST)
Jim Hague <jim.hague@acm.org> escribió (wrote):

[...]
> 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

That line didn't work but using @70 instead of -70 worked like a charm. Thanks
very much for you info! :)

Now i'm a happy framebuffer user again.

Keep the excellent work.

Regards.

-- 
 _____________________________________________________________
                                        _____  ____________
  Marcelo Ramos                        |     \/      __    |
  Fedora Core 1 | Linux 2.6.5          |            |_/    /
  Socio UYLUG Nro 125                  |                   \
  Linux registered user #118109        |____|\/|____|\______\

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-21 16:59 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
2004-04-21 16:26     ` Marcelo Ramos [this message]
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=20040421132639.1d87ba1b@zerocool \
    --to=mramos@montevideo.com.uy \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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