From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: James Simmons <jsimmons@infradead.org>,
Amit Shah <shahamit@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1: Framebuffer problem
Date: Mon, 21 Jul 2003 22:14:17 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0307212205550.27306-100000@vervain.sonytel.be> (raw)
In-Reply-To: <1058620026.22005.0.camel@dhcp22.swansea.linux.org.uk>
On 19 Jul 2003, Alan Cox wrote:
> On Sad, 2003-07-19 at 07:02, Geert Uytterhoeven wrote:
> > No, that's not so simple, because vesafb requests the linear frame buffer,
> > while vga16fb requests the VGA region.
Correction:
- vesafb uses
o request_mem_region() on the linear frame buffer
o request_region() on the 32 VGA registers (but the return code is
ignored because of vgacon)
- vga16fb doesn't use resource management (ugh)
- vgacon uses
o request_region() on the MDA/CGA/EGA/VGA registers
> In standard usage mode both of them use the vga registers for palette control..
Vesafb may use a protected mode BIOS call instead.
An additional complexity is that not only vesafb/vga16fb may claim the VGA
registers, but also vgacon. And it's allowed for vesafb/vga16fb to take over
vgacon.
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
prev parent reply other threads:[~2003-07-21 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 5:47 2.6.0-test1: Framebuffer problem Amit Shah
2003-07-16 5:37 ` Amit Shah
2003-07-17 17:05 ` James Simmons
2003-07-17 17:21 ` Alan Cox
2003-07-17 17:34 ` James Simmons
2003-07-18 9:53 ` Amit Shah
2003-07-18 12:57 ` Alan Cox
2003-07-18 20:18 ` Geert Uytterhoeven
2003-07-18 21:15 ` Alan Cox
2003-07-19 6:02 ` Geert Uytterhoeven
2003-07-19 13:07 ` Alan Cox
2003-07-21 20:14 ` Geert Uytterhoeven [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=Pine.GSO.4.21.0307212205550.27306-100000@vervain.sonytel.be \
--to=geert@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shahamit@gmx.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.