[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201113232839.GA6117@piout.net>
Date: Sat, 14 Nov 2020 00:28:39 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: kernel test robot <lkp@...el.com>, Arnd Bergmann <arnd@...db.de>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Olof Johansson <olof@...om.net>, kbuild-all@...ts.01.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Russell King <rmk+kernel@...linux.org.uk>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Claudiu Beznea <claudiu.beznea@...rochip.com>,
Ludovic Desroches <ludovic.desroches@...rochip.com>
Subject: Re: ./include/generated/autoconf.h:1601:33: fatal error:
mach/debug-macro.S: No such file or directory
On 11/11/2020 09:51:26+0100, Linus Walleij wrote:
> On Wed, Nov 11, 2020 at 7:18 AM kernel test robot <lkp@...el.com> wrote:
>
> > In file included from include/linux/kconfig.h:7,
> > from <command-line>:
> > >> ./include/generated/autoconf.h:1601:33: fatal error: mach/debug-macro.S: No such file or directory
> > 1601 | #define CONFIG_DEBUG_LL_INCLUDE "mach/debug-macro.S"
> > | ^~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
>
> This is an interesting one!
>
> It happens when CONFIG_DEBUG_LL_INCLUDE does not have a custom
> debug header for the platform under arch/arm/include/debug and the
> KConfig falls through to the default value, which is <mach/debug-macro.S>.
>
> Only that the majority is not using <mach/*> anymore.
>
> I feel a bit like setting the default to debug/8250.S or something.
>
> Suggestions?
>
> Then the actual bug exposed:
>
> The config tested by the robot is using
> CONFIG_ARCH_AT91=y
> CONFIG_SOC_SAMV7=y
>
> When I look into Kconfig.debug it seems that this will define
> DEBUG_AT91_SAMV7_USART1 but only a physical address,
> no virtual address and and actually no debug header. It seems
> LL_DEBUG is broken on SAMV7 and never really worked
> so now that crops up.
>
> Nicolas, something that should be fixed, I think?
>
This is what the platforms without an MMU are doing. I don't think there
is anything platform specific to fix.
Powered by blists - more mailing lists