From: Will Deacon <will.deacon@arm.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: kernel: need extern variable 'screen_info' for related driver using.
Date: Mon, 20 May 2013 10:10:08 +0100 [thread overview]
Message-ID: <20130520091008.GB31359@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <5199B7D6.40907@asianux.com>
Hi Chen,
On Mon, May 20, 2013 at 06:42:46AM +0100, Chen Gang wrote:
>
> Add the extern variable 'screen_info' according to arm32 has done.
>
> The related error:
> drivers/video/console/vgacon.c:1305: undefined reference to `screen_info'
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> arch/arm64/kernel/setup.c | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> index add6ea6..1055992 100644
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -374,3 +374,14 @@ const struct seq_operations cpuinfo_op = {
> .stop = c_stop,
> .show = c_show
> };
> +
> +#if defined(CONFIG_VGA_CONSOLE) || defined(CONFIG_DUMMY_CONSOLE)
> +struct screen_info screen_info = {
> + .orig_video_lines = 30,
> + .orig_video_cols = 80,
> + .orig_video_mode = 0,
> + .orig_video_ega_bx = 0,
> + .orig_video_isVGA = 1,
> + .orig_video_points = 8
> +};
> +#endif
I think it would be better if we added a something like
CONFIG_HAVE_VGA_CONSOLE, which VGA_CONSOLE can then depend on. Architectures
like x86 can then select the former, and we can remove the long list of
architectures from the current option.
Will
next prev parent reply other threads:[~2013-05-20 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 5:42 Chen Gang
2013-05-20 9:10 ` Will Deacon [this message]
2013-05-21 3:15 ` Chen Gang
2013-05-21 6:57 ` Geert Uytterhoeven
2013-05-21 7:51 ` Chen Gang
2013-05-21 9:03 ` Will Deacon
2013-05-21 10:13 ` Chen Gang
2013-05-21 13:15 ` Catalin Marinas
2013-05-22 0:50 ` Chen Gang
2013-05-21 11:07 ` Geert Uytterhoeven
2013-05-21 11:40 ` 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=20130520091008.GB31359@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=arnd@arndb.de \
--cc=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®