All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: krzysztof.h1@poczta.fm, spock@gentoo.org,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] fbdev: don't allow to set a video mode via vga= if FB doesn't support it
Date: Mon, 22 Sep 2008 13:28:30 -0700	[thread overview]
Message-ID: <20080922132830.359bc001.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080922220054.4e74c099@neptune.home>

On Mon, 22 Sep 2008 22:00:54 +0200
Bruno Prémont <bonbons@linux-vserver.org> wrote:

> From: Michal Januszewski <spock@gentoo.org>
> > Currently, it is possible to set a VESA graphics mode at boot time
> > via the vga= parameter even when no framebuffer driver supporting
> > this is configured.  This could lead to the system booting with a
> > black screen, without a usable console.
> > 
> This looks pretty much the same as what I requested some time ago:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=8062
> 
> Would need to check -mm archives for the actual patch.
> 
> Don't remember why it did not make it to mainline...

If someone can give me some idea of what that patch looked
like then I can go hunt it down, find out why it didn't make it.

  reply	other threads:[~2008-09-22 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 21:02 [PATCH] fbdev: don't allow to set a video mode via vga= if FB doesn't support it Michal Januszewski
2008-09-22 19:47 ` Krzysztof Helt
2008-09-22 20:00   ` [Linux-fbdev-devel] " Bruno Prémont
2008-09-22 20:28     ` Andrew Morton [this message]
2008-09-22 20:32     ` Michal Januszewski
2008-09-22 20:32       ` Michal Januszewski
2008-09-22 20:54       ` Andrew Morton
2008-09-22 20:34   ` Michal Januszewski

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=20080922132830.359bc001.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=krzysztof.h1@poczta.fm \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spock@gentoo.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 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.