From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] vesafb and *fb
Date: Sun, 25 Apr 2004 16:29:28 +0100 [thread overview]
Message-ID: <1082906968.28039.7.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.58.0404251511320.13613@waterleaf.sonytel.be>
On Sul, 2004-04-25 at 14:13, Geert Uytterhoeven wrote:
> > > if (!request_mem_region(vesafb_fix.smem_start, vesafb_fix.smem_len, "vesafb")) {
> > > printk(KERN_WARNING
> > > "vesafb: abort, cannot reserve video memory at 0x%lx\n",
> > > vesafb_fix.smem_start);
> > > /* We cannot make this fatal. Sometimes this comes from magic
> > > spaces our resource handlers simply don't know about */
Various built-in video systems broke on that test because we didnt
have resources for them so the resources couldnt be allocated. Probably
if vesafb is enabled we should skip any primary video device (ie the one
with VGA_EN at boot)
next prev parent reply other threads:[~2004-04-25 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 7:51 vesafb and *fb Geert Uytterhoeven
2004-04-23 23:31 ` James Simmons
2004-04-25 13:13 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-04-25 15:29 ` Alan Cox [this message]
2004-04-26 9:10 ` 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=1082906968.28039.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).