All of lore.kernel.org
 help / color / mirror / Atom feed
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

WARNING: multiple messages have this Message-ID (diff)
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 18:33:18 +0200	[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

  reply	other threads:[~2013-05-14 16:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 19:30 Build regressions/improvements in v3.10-rc1 Geert Uytterhoeven
2013-05-12 20:41 ` Geert Uytterhoeven
2013-05-12 20:42   ` Build regressions/improvements in v3.10-rc1 (sh) Geert Uytterhoeven
2013-05-12 20:42     ` Geert Uytterhoeven
2013-05-12 20:44   ` Build regressions/improvements in v3.10-rc1 (cris) Geert Uytterhoeven
2013-05-14 12:06     ` Geert Uytterhoeven
2013-05-14 12:06       ` Geert Uytterhoeven
2013-05-14 16:33       ` Jesper Nilsson [this message]
2013-05-14 16:33         ` Jesper Nilsson
2013-05-12 20:45   ` Build regressions/improvements in v3.10-rc1 (avr) Geert Uytterhoeven
2013-05-13 12:54     ` Hans-Christian Egtvedt
2013-05-13 13:00       ` Geert Uytterhoeven
2013-05-12 20:45   ` Build regressions/improvements in v3.10-rc1 (h8300) Geert Uytterhoeven
2013-05-12 20:46   ` Build regressions/improvements in v3.10-rc1 (mips) Geert Uytterhoeven
2013-06-11 13:37     ` Markos Chandras
2013-05-12 20:47   ` Build regressions/improvements in v3.10-rc1 (powerpc) Geert Uytterhoeven
2013-05-12 20:47   ` Build regressions/improvements in v3.10-rc1 (um) Geert Uytterhoeven
2013-05-12 21:17     ` richard -rw- weinberger
2013-05-13  8:18       ` Geert Uytterhoeven
2013-05-13  9:54         ` Michael Ellerman
2013-05-13 10:02           ` Geert Uytterhoeven
2013-05-13 10:07           ` richard -rw- weinberger
2013-05-13 10:18             ` Geert Uytterhoeven
2013-05-13 10:20               ` richard -rw- weinberger
2013-05-15  2:48                 ` Stephen Rothwell
2013-05-13 12:15             ` Michael Ellerman
2013-05-15  2:57               ` Stephen Rothwell
2013-05-15  6:50                 ` Geert Uytterhoeven
2013-05-12 20:49   ` Build regressions/improvements in v3.10-rc1 (crypto/parisc) Geert Uytterhoeven
2013-05-12 20:50   ` Build regressions/improvements in v3.10-rc1 (staging) Geert Uytterhoeven
2013-05-12 21:43     ` Greg KH
2013-05-12 20:50   ` Build regressions/improvements in v3.10-rc1 (s390) Geert Uytterhoeven
2013-05-13  7:41     ` Heiko Carstens
2013-05-13 16:41       ` Ben Hutchings
2013-05-12 22:13 ` Build regressions/improvements in v3.10-rc1 Randy Dunlap
2013-05-13  8:37   ` Geert Uytterhoeven

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.