From: Florian Fainelli <f.fainelli@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org, Paul Burton <paulburton@kernel.org>,
Maxime Bizon <mbizon@freebox.fr>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [RFC PATCH] mips: BCM63XX: select CPU_SUPPORTS_32BIT_KERNEL
Date: Fri, 5 Nov 2021 20:31:56 -0700 [thread overview]
Message-ID: <249707d6-660f-99ce-b7d3-c48dc7209bbe@gmail.com> (raw)
In-Reply-To: <20211106025823.32437-1-rdunlap@infradead.org>
On 11/5/2021 7:58 PM, Randy Dunlap wrote:
>
> Several header files need info on CONFIG_32BIT or CONFIG_64BIT,
> but kconfig symbol BCM63XX does not provide that info. This leads
> to many build errors, e.g.:
>
> arch/mips/include/asm/page.h:196:13: error: use of undeclared identifier 'CAC_BASE'
> return x - PAGE_OFFSET + PHYS_OFFSET;
> arch/mips/include/asm/mach-generic/spaces.h:91:23: note: expanded from macro 'PAGE_OFFSET'
> #define PAGE_OFFSET (CAC_BASE + PHYS_OFFSET)
> arch/mips/include/asm/io.h:134:28: error: use of undeclared identifier 'CAC_BASE'
> return (void *)(address + PAGE_OFFSET - PHYS_OFFSET);
> arch/mips/include/asm/mach-generic/spaces.h:91:23: note: expanded from macro 'PAGE_OFFSET'
> #define PAGE_OFFSET (CAC_BASE + PHYS_OFFSET)
>
> arch/mips/include/asm/uaccess.h:82:10: error: use of undeclared identifier '__UA_LIMIT'
> return (__UA_LIMIT & (addr | (addr + size) | __ua_size(size))) == 0;
>
>
> Fixes: e7300d04bd08 ("MIPS: BCM63xx: Add support for the Broadcom BCM63xx family of SOCs.")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: bcm-kernel-feedback-list@broadcom.com
> Cc: linux-mips@vger.kernel.org
> Cc: Paul Burton <paulburton@kernel.org>
> Cc: Maxime Bizon <mbizon@freebox.fr>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> ---
> Note: I did see a bunch of build errors like this one:
> ../arch/mips/kernel/r4k_fpu.S:217: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f24,192($4)'
> but I'm hoping/guessing that this is due to not having a proper compiler
> for the BCM63xx target.
>
> arch/mips/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20211105.orig/arch/mips/Kconfig
> +++ linux-next-20211105/arch/mips/Kconfig
> @@ -329,6 +329,7 @@ config BCM63XX
> select SYNC_R4K
> select DMA_NONCOHERENT
> select IRQ_MIPS_CPU
> + select CPU_SUPPORTS_32BIT_KERNEL
That's one option, the other could be to add:
select SYS_HAS_CPU_BMIPS32_3300
select SYS_HAS_CPU_BMIPS4350
select SYS_HAS_CPU_BMIPS4380
Which would ensure that CPU_SUPPORTS_32BIT_KERNEL is selected AFAICT.
Can you try that? What config file did you use to produce that build
error BTW?
--
Florian
next prev parent reply other threads:[~2021-11-06 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 2:58 [RFC PATCH] mips: BCM63XX: select CPU_SUPPORTS_32BIT_KERNEL Randy Dunlap
2021-11-06 3:31 ` Florian Fainelli [this message]
2021-11-06 4:44 ` Randy Dunlap
2021-11-06 15:18 ` Randy Dunlap
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=249707d6-660f-99ce-b7d3-c48dc7209bbe@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mbizon@freebox.fr \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=rdunlap@infradead.org \
--cc=tsbogend@alpha.franken.de \
/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