Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-Id: <202109222050.18MKoNUh007272@valdese.nms.ulrich-teichert.org>
Subject: Re: [PATCH v2 0/4] Introduce and use absolute_pointer macro
To:     torvalds@linux-foundation.org (Linus Torvalds)
Date:   Wed, 22 Sep 2021 22:50:23 +0200 (CEST)
Cc:     krypton@ulrich-teichert.org (Ulrich Teichert),
        mcree@orcon.net.nz (Michael Cree),
        linux@roeck-us.net (Guenter Roeck),
        rth@twiddle.net (Richard Henderson),
        ink@jurassic.park.msu.ru (Ivan Kokshaysky),
        mattst88@gmail.com (Matt Turner),
        James.Bottomley@hansenpartnership.com (James E . J . Bottomley),
        deller@gmx.de (Helge Deller),
        davem@davemloft.net (David S . Miller),
        kuba@kernel.org (Jakub Kicinski),
        linux-alpha@vger.kernel.org (alpha),
        geert@linux-m68k.org (Geert Uytterhoeven),
        linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
        linux-parisc@vger.kernel.org (linux-parisc),
        netdev@vger.kernel.org (Netdev),
        linux-sparse@vger.kernel.org (Sparse Mailing-list)
In-Reply-To: <CAHk-=whwreptD=WByMRNsv-gfqR3oUu4v33i5Swd2dyeLObyRw@mail.gmail.com>
From:   Ulrich Teichert <krypton@ulrich-teichert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

> > I would try the SRM bootimage (make bootimage), but the build is broken:
> 
> The attached patch is too ugly for words, and there's no way I will
> commit anything like this.
> 
> But it at least builds for and seems to successfully make an alpha
> bootimage even when cross-compiling on x86-64.
> 
> So something to test, perhaps..

Sure, I burned it to a CDROM and booted from that per SRM. The screen
went black for a second, then the SRM console came back with:

?05 HLT INSTR
PC=00000000.20000014 PSL= 00000000.00000007

I wonder if we would be able to see more on a serial line - I can try
that perhaps tomorrow or at the weekend. To find out to what code the
PC is pointing to, I would need to understand to what point in memory SRM
loads the image into.... But this way, the process of loading the kernel
definitely worked - I still don't understand why aboot can load the
old kernel but not the new one. I'll have a look at the aboot sources,
perhaps there's a certain limit on kernel size?

I'm not sure if we can call this progress,
CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de | Listening to:
Stormweg 24               |Eat Lipstick: Dirty Little Secret, The Baboon Show:
24539 Neumuenster, Germany|Work Work Work, The Bellrays: Bad Reaction