Re: [PATCH] sh: intc: sort the prio and sense lists after filling them
From: Geert Uytterhoeven
Date: Mon Sep 28 2026 - 12:06:55 EST
Hi Adrian,
On Mon, 28 Sept 2026 at 17:10, John Paul Adrian Glaubitz
<glaubitz@xxxxxxxxxxxxxxxxxxx> wrote:
> => usb reset; fatload usb 0:1 0x89000000 uImage-7.3.0.gz ; pmb ; bootm
> (Re)start USB...
> USB0: scanning bus 0 for devices... 2 USB Device(s) found
> scanning usb for storage devices... 1 Storage Device(s) found
> reading uImage-7.3.0.gz
> 3649306 bytes read in 2074 ms (1.7 MiB/s)
> ## Booting kernel from Legacy Image at 89000000 ...
> Image Name: Linux-7.3.0-rc5-00001-g8cd915e93
> Image Type: SuperH Linux Kernel Image (gzip compressed)
> Data Size: 3649242 Bytes = 3.5 MiB
> Load Address: 8c010000
> Entry Point: 8c011000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
>
> I also never understood why the load address I used at the u-boot prompt
> differed from the one that the uImage build process showed at the end of
> the kernel build:
>
> GZIP arch/sh/boot/vmlinux.bin.gz
> UIMAGE arch/sh/boot/uImage.gz
> Image Name: Linux-7.3.0-rc5-00002-g02d53450e
> Created: Mon Sep 28 14:56:15 2026
> Image Type: SuperH Linux Kernel Image (gzip compressed)
> Data Size: 3649249 Bytes = 3563.72 KiB = 3.48 MiB
> Load Address: 8c010000
> Entry Point: 8c011000
> Image arch/sh/boot/uImage is ready
>
> Any idea?
0x89000000 is the address where you load the uImage.
0x8c010000 is the address where the unpacked kernel image will be
stored.
The latter comes from your kernel config:
arch/sh/boot/Makefile:UIMAGE_LOADADDR = $(KERNEL_LOAD)
arch/sh/boot/Makefile:UIMAGE_ENTRYADDR = $(KERNEL_ENTRY)
It's similar on ARM platforms that (still) use uImage.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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