From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Arnd Bergmann <arnd@arndb.de>,
"sachin.kamat@linaro.org" <sachin.kamat@linaro.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
James Hogan <james.hogan@imgtec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCH] arc: kernel: add default extern variable 'screen_info' in "setup.c"
Date: Sat, 26 Oct 2013 10:13:03 +0800 [thread overview]
Message-ID: <526B252F.2050506@asianux.com> (raw)
In-Reply-To: <CAMuHMdWCrLaAiOtgKtH5yb82XvoDJ15BEUB8gyQS2-CkjQqHTw@mail.gmail.com>
On 10/24/2013 07:51 PM, Geert Uytterhoeven wrote:
> Hi Chen,
>
> On Thu, Oct 24, 2013 at 1:23 PM, Chen Gang <gang.chen@asianux.com> wrote:
>>> Lot's of negative dependencies are missing for VGA_CONSOLE.
>>> I think only alpha, some arm, ia64, some mips, some powerpc, and x86
>>> may use it.
>>>
>>
>> in "arch" sub-directory, contents 13/30 (43.3%) architectures contents
>> VGA_CONSOLE.
>>
>> 1 alpha/kernel/setup.c:137:struct screen_info screen_info = {
>> 2 arm/kernel/setup.c:743:struct screen_info screen_info = {
>> 3 cris/kernel/setup.c:28:struct screen_info screen_info;
>> 4 ia64/kernel/setup.c:79:struct screen_info screen_info;
>> 5 m32r/kernel/setup.c:55:struct screen_info screen_info = {
>> 6 mips/kernel/setup.c:43:struct screen_info screen_info;
>> 7 powerpc/kernel/setup-common.c:88:struct screen_info screen_info = {
>> 8 score/kernel/setup.c:37:struct screen_info screen_info;
>> 9 sh/kernel/setup.c:68:struct screen_info screen_info;
>> 10 sparc/kernel/setup_64.c:66:struct screen_info screen_info = {
>> 11 sparc/kernel/setup_32.c:53:struct screen_info screen_info = {
>> 12 tile/kernel/setup.c:54:struct screen_info screen_info;
>> 13 x86/kernel/setup.c:220:struct screen_info screen_info;
>> 14 xtensa/kernel/setup.c:55:struct screen_info screen_info = { 0, 24, 0, 0, 0, 80, 0, 0, 0, 24, 1, 16};
>>
>> It seems most of pc and servers support VGA_CONSOLE.
>
> I'm quite sure many of these just provide a screen_info to make vgacon compile.
>
Thank you for your confirmation.
>>> Compare this to a shiny new feature that available on all new architectures,
>>> but not on a few old one. There it makes sense to have the negative
>>> dependencies on the old architectures, that will never have the new feature.
>>> While new architectures have enabled it by default.
>>>
>>
>> Excuse me, my English is not quite well, I do not quite understand your
>> meaning, but it seems not quite important for our discussing, so I just
>> skip it, now.
>
> Sorry, I should stop writing complex sentences.
> For now, nevermind. There aren't that many real cases like this.
>
And I should be still improving my English. :-)
> 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
>
>
Thanks.
--
Chen Gang
next prev parent reply other threads:[~2013-10-26 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 11:09 [PATCH] arc: kernel: add default extern variable 'screen_info' in "setup.c" Chen Gang
2013-10-23 13:47 ` Vineet Gupta
2013-10-24 2:56 ` Chen Gang
2013-10-24 8:30 ` Geert Uytterhoeven
2013-10-24 11:23 ` Chen Gang
2013-10-24 11:50 ` Vineet Gupta
2013-10-26 2:11 ` Chen Gang
2013-10-24 11:51 ` Geert Uytterhoeven
2013-10-26 2:13 ` Chen Gang [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-28 9:07 Chen Gang
2013-12-06 0:58 ` rkuo
2013-12-06 2:03 ` Chen Gang
2013-12-24 3:18 ` Chen Gang
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=526B252F.2050506@asianux.com \
--to=gang.chen@asianux.com \
--cc=Catalin.Marinas@arm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sachin.kamat@linaro.org \
--cc=will.deacon@arm.com \
/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).