Re: Did you see my qemu r2d memory patch?

Hi Rob,

On Mon, 2026-02-23 at 10:44 -0600, Rob Landley wrote:
> It was in 
> https://lists.gnu.org/archive/html/qemu-devel/2026-01/msg06318.html and 
> probably needs to be reposted as a separate thing, but with it I booted 
> an sh4 kernel with over 200 megs of memory, enough to act as a 
> reasonable native build node (especially using the distcc trick). No 
> kernel patch required, just a .config change setting two symbols it's 
> already got to different values.

No, I haven't seen that. I got too many things to do at the moment, also
at my regular job such that I don't have too much time for SH at the moment.

I will catch up with it the next weeks though.

> I need to port the r2d target over to device tree (well, extend the 
> turtle device tree stuff to support r2d and its devices) and teach qemu 
> to supply a device tree overlay with the current memory map so you don't 
> have to match kernel with qemu -m layout (the only way to get the extra 
> memory in one contiguous block is to move the START of the memory range, 
> which means moving the initrd and command line string locations which 
> are relative to start of memory, so the kernel needs to know where to 
> expect start of memory and thus needs to be recompiled for the different 
> memory amount rather than just autodetecting. Device tree blob location 
> is loaded into a register before kernel init...)
> 
> Anyway, thought I'd ask what you thought,

I think we should pick up Yoshinori's series for device tree support [1]
and get it into a mergable state.

Adrian

> [1] https://patchwork.kernel.org/project/linux-sh/patch/[email protected]/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913