From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] Add ARCH_MIGHT_HAVE_VGA_CONSOLE
Date: Mon, 2 Feb 2015 09:10:06 +0100 [thread overview]
Message-ID: <CAMuHMdV8hyDWwz8V5rvrthcV8NyNk4J+9Opmxt3opqi5rtQoJw@mail.gmail.com> (raw)
In-Reply-To: <877fw093oa.wl-ysato@users.sourceforge.jp>
Hi Sato-san,
On Mon, Feb 2, 2015 at 8:24 AM, Yoshinori Sato
<ysato@users.sourceforge.jp> wrote:
> The dependence of VGA_CONSOLE is complicated.
> We need clean up.
Thanks!
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
>
> ---
> arch/alpha/Kconfig | 1 +
> arch/arc/Kconfig | 1 +
> arch/arm/Kconfig | 1 +
> arch/c6x/Kconfig | 1 +
> arch/hexagon/Kconfig | 1 +
> arch/ia64/Kconfig | 1 +
> arch/m32r/Kconfig | 1 +
> arch/metag/Kconfig | 1 +
> arch/microblaze/Kconfig | 1 +
> arch/mips/Kconfig | 1 +
> arch/nios2/Kconfig | 1 +
> arch/openrisc/Kconfig | 1 +
> arch/powerpc/Kconfig | 1 +
> arch/s390/Kconfig | 1 +
> arch/score/Kconfig | 1 +
> arch/tile/Kconfig | 1 +
> arch/um/Kconfig.common | 1 +
> arch/unicore32/Kconfig | 1 +
> arch/x86/Kconfig | 1 +
> arch/xtensa/Kconfig | 1 +
While I know you just kept the existing logic from
drivers/video/console/kconfig,
I doubt all of the architectures listed above do support VGA.
I guest most of them were just too lazy to update the dependency list.
I think only alpha, arm, ia64, mips, powerpc, and x86 can have VGA.
> --- a/drivers/video/console/Kconfig
> +++ b/drivers/video/console/rconfig
> @@ -2,14 +2,14 @@
> # Video configuration
> #
>
> +config ARCH_MIGHT_HAVE_VGA_CONSOLE
> + bool
> +
> menu "Console display driver support"
>
> config VGA_CONSOLE
> bool "VGA text console" if EXPERT || !X86
> - depends on !4xx && !8xx && !SPARC && !M68K && !PARISC && !FRV && \
> - !SUPERH && !BLACKFIN && !AVR32 && !MN10300 && !CRIS && \
> - (!ARM || ARCH_FOOTBRIDGE || ARCH_INTEGRATOR || ARCH_NETWINDER) && \
> - !ARM64
> + depends on ARCH_MIGHT_HAVE_VGA_CONSOLE
> default y
> help
> Saying Y here will allow you to use Linux in text mode through a
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 parent reply other threads:[~2015-02-02 8:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877fw093oa.wl-ysato@users.sourceforge.jp>
2015-02-02 8:10 ` Geert Uytterhoeven [this message]
2015-02-02 15:48 ` [PATCH] Add ARCH_MIGHT_HAVE_VGA_CONSOLE Yoshinori Sato
2015-02-02 15:48 ` Yoshinori Sato
2015-02-02 20:11 ` Arnd Bergmann
2015-02-03 0:08 ` Stephen Rothwell
2015-02-03 4:42 ` Yoshinori Sato
2015-02-02 21:07 ` Geert Uytterhoeven
2015-02-02 21:07 ` Geert Uytterhoeven
2015-02-03 4:42 ` Yoshinori Sato
2015-02-04 6:03 ` [PATCH v3] " Yoshinori Sato
2015-02-04 7:37 ` Arnd Bergmann
2015-02-07 7:42 ` Yoshinori Sato
2015-02-15 7:22 ` [PATCH v4] " Yoshinori Sato
2015-02-15 9:03 ` 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=CAMuHMdV8hyDWwz8V5rvrthcV8NyNk4J+9Opmxt3opqi5rtQoJw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).