All of lore.kernel.org
 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 01:51:18 -0300	[thread overview]
Message-ID: <20040421015118.2caa6e99@zerocool> (raw)
In-Reply-To: <XFMail.20040421004644.jim.hague@acm.org>

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

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

> The conversion of pm2fb to using framebuffer_alloc() introduced a null pointer
> dereference bug.
> 
> This patch fixes this bug, and a silly problem in pm2fb_blank(). There's also
> some minor tidying.
> 
> The patch is against 2.6.6-rc1.

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?

TIA

-- 
 _____________________________________________________________
                                        _____  ____________
  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  4:55 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 [this message]
2004-04-21 10:14   ` Jim Hague
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=20040421015118.2caa6e99@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.