From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Boszormenyi Zoltan <zboszor@pr.hu>
Cc: linux-kernel@vger.kernel.org,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>
Subject: Re: VESA and VGA16 framebuffer drivers clash sometimes
Date: Fri, 20 Apr 2012 11:12:10 +0000 [thread overview]
Message-ID: <CAMuHMdWCMP8L=k8tWiXv6Mcb5u6iTCx3fb7_mTGVyQSE7V=r_w@mail.gmail.com> (raw)
In-Reply-To: <4F911568.7050601@pr.hu>
2012/4/20 Boszormenyi Zoltan <zboszor@pr.hu>:
> on an embedded x86 board with Intel Atom, text on vesafb
> gets distorted if both vesafb and vga16fb are compiled in.
> The strange thing is that it doesn't happen all the time but
> about once out of 15 boots.
>
> The distortion looks like this:
> http://www.postgresql-support.de/private/IMG_7221.jpg
>
> The relevant kernel messages:
>
> Apr 13 11:14:30 term002 kernel: vesafb: mode is 800x600x16, linelength\x1600,
> pages=7
> Apr 13 11:14:30 term002 kernel: vesafb: scrolling: redraw
> Apr 13 11:14:30 term002 kernel: vesafb: Truecolor: size=0:5:6:5,
> shift=0:11:5:0
> Apr 13 11:14:30 term002 kernel: vesafb: framebuffer at 0xa0000000, mapped to
> 0xdf580000, using 1875k, total 8128k
> Apr 13 11:14:30 term002 kernel: Console: switching to colour frame buffer
> device 100x37
> Apr 13 11:14:30 term002 kernel: fb0: VESA VGA frame buffer device
> Apr 13 11:14:30 term002 BOOTLOG: Terminal startup
> Apr 13 11:14:30 term002 kernel: vga16fb: mapped to 0xc00a0000
> Apr 13 11:14:30 term002 kernel: fbcon: VGA16 VGA (fb1) is primary device
> Apr 13 11:14:30 term002 kernel: fbcon: Remapping primary device, fb1, to tty
> 1-63
> Apr 13 11:14:30 term002 kernel: fb1: VGA16 VGA frame buffer device
>
> It's strange that vga16fb is always detected as primary
> and vesafb gets remapped to fb1 even when there is no
> screen distortion. The kernel is compiled for SMP.
IIRC, the request_region()/request_mem_region() calls in vga16fb.c that would
avoid this were removed several years ago. Unfortunately I don't remember
anymore why. Google or full-history-linux may help you...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2012-04-20 11:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4F911568.7050601@pr.hu>]
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='CAMuHMdWCMP8L=k8tWiXv6Mcb5u6iTCx3fb7_mTGVyQSE7V=r_w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@pr.hu \
/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).