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: Sat, 19 Jul 2003 08:02:41 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0307190801260.26815-100000@vervain.sonytel.be> (raw)
In-Reply-To: <1058562955.19511.65.camel@dhcp22.swansea.linux.org.uk>
On 18 Jul 2003, Alan Cox wrote:
> On Gwe, 2003-07-18 at 21:18, Geert Uytterhoeven wrote:
> > > Then it still needs to be fixed. This works correctly in 2.4
> > Since vesafb can detect whether you booted with a graphics mode, vga16fb should
> > be able to detect you didn't, right?
>
> Equally it knows that the frame buffer in question was allocated providing
> someone is doing the resource handling right
No, that's not so simple, because vesafb requests the linear frame buffer,
while vga16fb requests the VGA region.
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
next prev parent reply other threads:[~2003-07-19 5:48 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 [this message]
2003-07-19 13:07 ` Alan Cox
2003-07-21 20:14 ` Geert Uytterhoeven
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.0307190801260.26815-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 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).