From: Michal Simek <monstr@monstr.eu>
To: Chen Gang <gang.chen.5i5j@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <rob.herring@calxeda.com>,
Paul Bolle <pebolle@tiscali.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [PATCH] arch/microblaze/kernel/setup.c: Add default 'screen_info" for fixing compiling break
Date: Tue, 16 Sep 2014 11:23:42 +0200 [thread overview]
Message-ID: <5418019E.1010202@monstr.eu> (raw)
In-Reply-To: <541559C2.8070703@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]
On 09/14/2014 11:02 AM, Chen Gang wrote:
> On 09/14/2014 04:45 PM, Geert Uytterhoeven wrote:
>> Hi Chen,
>>
>> On Sun, Sep 14, 2014 at 10:32 AM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>> Add default one just like other architectures have done (e.g. cris,
>>> score, sh ...), the related error with allmodconfig:
>>>
>>> LD init/built-in.o
>>> drivers/built-in.o: In function `vgacon_save_screen':
>>> drivers/video/console/.tmp_vgacon.o:(.text+0x834d0): undefined reference to `screen_info'
>>> drivers/video/console/.tmp_vgacon.o:(.text+0x834ec): undefined reference to `screen_info'
>>> drivers/built-in.o: In function `vgacon_resize':
>>> drivers/video/console/.tmp_vgacon.o:(.text+0x83cdc): undefined reference to `screen_info'
>>> drivers/video/console/.tmp_vgacon.o:(.text+0x83d38): undefined reference to `screen_info'
>>> drivers/built-in.o: In function `vgacon_switch':
>>> drivers/video/console/.tmp_vgacon.o:(.text+0x83f50): undefined reference to `screen_info'
>>> drivers/built-in.o:drivers/video/console/.tmp_vgacon.o:(.text+0x8407c): more undefined references to `screen_info' follow
>>> make: *** [vmlinux] Error 1
>>
>> Can microblaze actually have VGA?
>>
>> If not, it's better to disable it.
>>
>
> Welcome the related microblaze maintainers ideas for it
Is this is just about VGA or video console in general?
There is xilinx FB driver and other FB are around too.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-09-16 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 8:32 [PATCH] arch/microblaze/kernel/setup.c: Add default 'screen_info" for fixing compiling break Chen Gang
2014-09-14 8:45 ` Geert Uytterhoeven
2014-09-14 9:02 ` Chen Gang
2014-09-16 9:23 ` Michal Simek [this message]
2014-09-16 10:04 ` Geert Uytterhoeven
2014-09-16 10:59 ` Michal Simek
2014-09-16 14:34 ` Chen Gang
2014-09-15 8:50 ` Jesper Nilsson
2014-09-15 11:10 ` Chen Gang
2014-09-20 4:08 ` 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=5418019E.1010202@monstr.eu \
--to=monstr@monstr.eu \
--cc=gang.chen.5i5j@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rob.herring@calxeda.com \
--cc=starvik@axis.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).