All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: krzysztof.h1@poczta.fm
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: bug #13249 - problem with intelfb on i845gm
Date: Mon, 18 May 2009 15:29:03 +0200 (CEST)	[thread overview]
Message-ID: <20090518.152903.193209423.wl@gnu.org> (raw)
In-Reply-To: <20090518145125.f975ae2b.krzysztof.h1@poczta.fm>


> What I see here is that for 2.6.27 you use the VESA framebuffer
> while you do not use it for the 2.6.28
> 
> Compare your configs:
> 2.6.27 : CONFIG_FB_VESA=y
> 2.6.28: # CONFIG_FB_VESA is not set

This is intentional.  Reason is that in 2.6.28 option
`CONFIG_FB_BOOT_VESA_SUPPORT' has been added, and it seems that this
change introduced a bug.

> My advice is try using the Intel framebuffer (change it to Y not 'M'
> like module).  It should be faster than VESA on your hardware.
> Unselect VESA.

I'm doing a git bisect right now to find out why
CONFIG_FB_BOOT_VESA_SUPPORT doesn't work as advertised.


    Werner

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects

  reply	other threads:[~2009-05-18 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090517140249.d3a1888c.krzysztof.h1@poczta.fm>
     [not found] ` <20090518.124818.237161585.wl@gnu.org>
2009-05-18 12:51   ` bug #13249 - problem with intelfb on i845gm Krzysztof Helt
2009-05-18 13:29     ` Werner LEMBERG [this message]
2009-05-20  5:51       ` Krzysztof Helt
2009-05-20  6:25         ` Werner LEMBERG
2009-05-20  8:44           ` Krzysztof Helt
2009-05-20  9:26             ` Werner LEMBERG
2009-05-20  8:50           ` Krzysztof Helt

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=20090518.152903.193209423.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=krzysztof.h1@poczta.fm \
    --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.