linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ley Foon Tan <ley.foon.tan@intel.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: vgacon: disable vgacon on nios2
Date: Wed, 07 Dec 2016 05:13:10 +0000	[thread overview]
Message-ID: <1481087590.2638.2.camel@intel.com> (raw)
In-Reply-To: <20161128124850.14383-1-tklauser@distanz.ch>

On Sel, 2016-12-06 at 08:04 +0100, Tobias Klauser wrote:
> On 2016-12-06 at 04:29:12 +0100, Ley Foon Tan <ley.foon.tan@intel.com
> > wrote:
> > 
> > On Isn, 2016-11-28 at 13:48 +0100, Tobias Klauser wrote:
> > > 
> > > The allyesconfig/allmodconfig build currently fails on nios2 with
> > > the
> > > following linker error:
> > > 
> > > drivers/built-in.o: In function `vgacon_switch':
> > > vgacon.c:(.text+0x34750): undefined reference to `screen_info'
> > > vgacon.c:(.text+0x34758): undefined reference to `screen_info'
> > > drivers/built-in.o: In function `vgacon_resize':
> > > vgacon.c:(.text+0x349b4): undefined reference to `screen_info'
> > > vgacon.c:(.text+0x349b8): undefined reference to `screen_info'
> > > drivers/built-in.o: In function `vgacon_save_screen':
> > > vgacon.c:(.text+0x34ae8): undefined reference to `screen_info'
> > > drivers/built-in.o:vgacon.c:(.text+0x34aec): more undefined
> > > references to `screen_info' follow
> > > 
> > > Since the nios2 architecture doesn't define the screen_info
> > > symbol.
> > > 
> > > Fix it by disabling VGA console for nios2.
> > > 
> > > Cc: Ley Foon Tan <lftan@altera.com>
> > > Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> > Sudip sent this patch in early November before to add screen_info
> > in
> > nios2. However, I don't have hardware to test the settings used in
> > this
> > patch is working or not. We only need either one of these 2
> > patches. Do
> > you have any comment?
> > https://patchwork.kernel.org/patch/9420315/
> I don't have any hardware to test this on either, so I thought this
> was
> the safest fix.
> 
> If we're going to define screen_info, I'd suggest to do it in a
> similar
> manner as e.g. tile, sh, score, ia64, hexagon, cris, c6x and
> unicore32.
> They all just define an struct screen_info screen_info; without any
> of
> the members set explicitely. I think they should only be set, once
> they
> actually have been tested on hardware.
> 
> In any case, I'd propose to apply either one of the solutions for 4.9
> in
> order to fix the build breakage.
Okay, I will follow other architectures approach. Just add the
declaration for screen_info:

struct screen_info screen_info;

Thanks.
Ley Foon


      parent reply	other threads:[~2016-12-07  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 12:48 [PATCH] video: vgacon: disable vgacon on nios2 Tobias Klauser
2016-12-06  3:29 ` Ley Foon Tan
2016-12-06  7:04 ` Tobias Klauser
2016-12-07  5:13 ` Ley Foon Tan [this message]

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=1481087590.2638.2.camel@intel.com \
    --to=ley.foon.tan@intel.com \
    --cc=linux-fbdev@vger.kernel.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 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).