linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Morton <akpm@osdl.org>, linux-fbdev-devel@lists.sourceforge.net
Cc: pluto@pld-linux.org
Subject: Re: Fw: [framebuffer] broken again :/
Date: Thu, 22 Jul 2004 14:51:35 +0800	[thread overview]
Message-ID: <200407221451.37004.adaplas@hotpop.com> (raw)
In-Reply-To: <20040721224515.1b76193e.akpm@osdl.org>

On Thursday 22 July 2004 13:45, Andrew Morton wrote:
> Begin forwarded message:
>
> Date: Wed, 21 Jul 2004 16:00:44 +0200
> From: Pawe³ Sikora <pluto@pld-linux.org>
> To: Andrew Morton <akpm@osdl.org>
> Subject: [framebuffer] broken again :/
>
>
> Hi,
>
> # vanilla 2.8.8rc2...
>
> I switch *all* consoles to 1024x768(75Hz,32bpp) (rivafb) mode.
> (http://149.156.124.14/~pluto/tmp/kernel/step1.png)
> Even without launching a bootsplash while switching
> to another console I observe below effect:
> (strange resolution and horrible aspect ratio)

The problem is that the bootsplash code uses vc_resize() to create a 'box' 
effect (small viewport within the display).  Calling vc_resize() has no 
effect in 2.4 as fbcon does not have a con_resize hook, but in 2.6, calling 
vc_resize() is equivalent to doing an fbset.  This produces the unusual 
aspect ratio and resolution.
 
> http://149.156.124.14/~pluto/tmp/kernel/step2.png
> I switch consoles again to 1024x768(75Hz,32bpp) mode
> and get an oops:
> http://149.156.124.14/~pluto/tmp/kernel/step3.png

The oops here is from the bootsplash code, perhaps brought about  by the 
unexpected mode change.

>
> # vanilla 2.6.7...
>
> I switch *all* consoles to 1024x768(75Hz,32bpp) (rivafb) mode.
> While switching to another console everything is all right.
> (no resolution/aspect changes, no oops).

Yes, fbset calls are ignored in pre 2.6.7-mm1 kernels, so this is expected.  
Latest kernel snapshots already handle fbset requests.

One solution for the bootsplash code in 2.6 is for it to disable the 
con_resize/fbcon_resize hook in fbcon.c. You should let the bootsplash 
developers know about this complication. 

For rivafb, enable DDC/I2C support in your kernel config and try booting with 
the 'strictmode' option. If you do not have a GTF capable display and 
assuming your monitor can do DDC and has a valid EDID block, the 'strictmode' 
option will force rivafb to restrict itself to using video modes creaed from 
the EDID block. This, hopefully, avoids the unusual aspect ratio and 
resolution change.

> Framebuffer in 2.6.8-xx is broken (again) :/
> Writing to lkml == Writing to /dev/null :/

Next time, write to fbdev-devel list for any fbdev/fbcon related problems.

Tony




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click

      reply	other threads:[~2004-07-22  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22  5:45 Fw: [framebuffer] broken again :/ Andrew Morton
2004-07-22  6:51 ` Antonino A. Daplas [this message]

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=200407221451.37004.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=pluto@pld-linux.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).