Re: [PATCH] sh: intc: sort the prio and sense lists after filling them

[Karl Mehltretter <kmehltretter@gmail.com>]

On Mon, Sep 28, 2026 at 09:02:55PM +0100, John Paul Adrian Glaubitz wrote:
> On Mon, 2026-09-28 at 20:34 +0200, Geert Uytterhoeven wrote:
> > > usb reset ; fatload usb 0:1 0x89000000 uImage-git.gz ; pmb ; bootm
> > 
> > Do you have a config for that kernel?
> 
> Here are some known configs:
> 
> https://people.debian.org/~glaubitz/sh7785lcr/configs/

I think it's the config. Your new image loads at 0x8c010000, the working
one at 0x80001000.

0x8c010000 is what an R2D config gives, and config-SH7785LCR-6.5 is one:
CPU_SUBTYPE_SH7751R and SH_RTS7751R2D, 29BIT, MEMORY_START 0x0c000000.
config-SH7785LCR-2024 still has SH7785LCR, 32BIT/PMB and MEMORY_START
0x40000000, which gives 0x80001000.

I tried both on my QEMU model of the SH7785LCR with 7.3: the 2024 config
boots up to the root mount, the 6.5 one prints nothing at all.

So I'd start from config-SH7785LCR-2024 (or sh7785lcr_32bit_defconfig):

  cp config-SH7785LCR-2024 .config make ARCH=sh olddefconfig

and check for "Load Address: 80001000". Keep the intc patch applied, the
overflow crashed v6.5 and v6.6 with SLUB on my QEMU model.

With the right config the kernel may then really be too large: 7.3-rc5
with config-SH7785LCR-2024 uncompresses to 8.2 MiB, and U-Boot's default
CONFIG_SYS_BOOTM_LEN is 8 MiB. U-Boot then prints "Image too large:
increase CONFIG_SYS_BOOTM_LEN". With CONFIG_CC_OPTIMIZE_FOR_SIZE=y it is
7.3 MiB and boots through U-Boot on the model.

On the model I use U-Boot 2019.04 (sh7785lcr_32bit_defconfig, the last
release with the board), with a few local fixes it needs to start at
all. 

Which U-Boot version does your board run ("version" at the
prompt)? Its limit may differ from the 8 MiB default.

Karl