From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=DATE_IN_PAST_12_24 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 32092 invoked from network); 12 Apr 2021 10:14:02 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 12 Apr 2021 10:14:02 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Sun Apr 11 08:11:34 -0400 2021 Message-ID: <4608706F7F1E10EEF1B37976ED3A971F@felloff.net> Date: Sun, 11 Apr 2021 14:11:22 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: standard cloud WEB2.0 singleton API controller Subject: Re: [9front] PXE booting Rpi Reply-To: 9front@9front.org Precedence: bulk > What if we always try dtree first and fallback to atags for the bcm > kernel only? I’ll take care of it if it sounds good to you! ok, i just tried the 32 bit pi2 kernel with a raspberry pi 3B+ pxeboot and the R2 register appears to be zero on entry. this is with the latest bootcode.bin and start_cd*.elf: term% sha1sum bootcode.bin fixup_cd.dat start_cd.elf 76b71ff97ace39d9900c27f761f7548c4c6f49a5 bootcode.bin 1585386a20cfc42b541f3ed1439d90e8c5b4529e fixup_cd.dat e08d5b453ad1203f85cc5421b96ed6ebcc2f2299 start_cd.elf and the following settings in config.txt: [pi3] kernel=../../sys/src/9/bcm/9pi2 [all] gpu_mem=16 enable_uart=1 boot_delay=1 note that atags worked just fine for me, without any special setting. so can you tell me exactly what you are doing? because i can't reproduce anything you described. -- cinap