From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
linux-cris-kernel <linux-cris-kernel@axis.com>
Subject: Re: Build regressions/improvements in v3.10-rc1 (cris)
Date: Tue, 14 May 2013 16:33:18 +0000 [thread overview]
Message-ID: <20130514163318.GQ8853@axis.com> (raw)
In-Reply-To: <CAMuHMdW6p6tP=wwBNV9uAAbwwgpyzMiPxsBSJNOUazhznYC4iQ@mail.gmail.com>
On Tue, May 14, 2013 at 02:06:51PM +0200, Geert Uytterhoeven wrote:
> On Sun, May 12, 2013 at 10:44 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > drivers/video/console/fonts.c:71:2: error: #error No fonts configured.: 2 errors in 2 logs
> > v3.10-rc1/cris/cris-allmodconfig v3.10-rc1/cris/cris-allyesconfig
> >
> > Fbdev issue?
>
> This is caused by cris not using the generic drivers/Kconfig, and thus not
> traversing drivers/video/console/Kconfig.
> As the build system does traverse drivers/video/console/Makefile, fonts.c
> is compiled with an inconsistent configuration.
>
> Two solutions:
> 1. Add drivers/video/console/Kconfig to arch/cris/Kconfig,
> 2. Switch cris to drivers/Kconfig,
>
> I prefer two, as this is what's done by all (except h8300) other
> architectures. This will seriously broaden the scope of allmodconfig,
> though, and require more fixes (e.g. missing <asm/vga.h>).
I would have no objections a conversion of CRIS to use the
drivers/Kconfig, though it feels a bit strange to compile
video drivers for SoCs that don't have any video out hardware.
> Note: The decision logic for compiling drivers/video/console/fonts.c is
> overly complicated, and seems to be buggy for some stuff living
> outside drivers drivers/video (drivers/media/platform/vivi.c and
> drivers/staging/media/solo6x10/solo6x10-enc.c). I think this should
> be resolved in Kconfig logic, using a new FONT_SUPPORT
> symbol (FONTS is already taken).
>
> 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
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2013-05-14 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1305122130270.3789@ayla.of.borg>
[not found] ` <alpine.DEB.2.00.1305122239040.5463@ayla.of.borg>
[not found] ` <alpine.DEB.2.00.1305122242430.5463@ayla.of.borg>
2013-05-14 12:06 ` Build regressions/improvements in v3.10-rc1 (cris) Geert Uytterhoeven
2013-05-14 16:33 ` Jesper Nilsson [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=20130514163318.GQ8853@axis.com \
--to=jesper.nilsson@axis.com \
--cc=geert@linux-m68k.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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