From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A220CC433F5 for ; Fri, 8 Apr 2022 12:11:26 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 833A983D96; Fri, 8 Apr 2022 14:11:23 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=kojedz.in Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (4096-bit key; secure) header.d=kojedz.in header.i=@kojedz.in header.b="gZwfjgoY"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 0824F83C35; Fri, 8 Apr 2022 09:44:29 +0200 (CEST) Received: from pi.kojedz.in (pi.kojedz.in [109.61.102.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 3F71D80269 for ; Fri, 8 Apr 2022 09:44:26 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=kojedz.in Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=richard@kojedz.in Received: from webmail.srv.kojedz.in (BC9CDDBA.catv.pool.telekom.hu [188.156.221.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) (Authenticated sender: richard@kojedz.in) by pi.kojedz.in (Postfix) with ESMTPSA id 8928DE66E for ; Fri, 8 Apr 2022 09:44:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kojedz.in; s=mail; t=1649403865; bh=J+qgRh1AOcoalvP+32lO6nmBdbMKfw7ikee5Yk4wmus=; h=Date:From:To:Subject; b=gZwfjgoYfMXtIXA80uM0rvCAvNWqZW7MuGlfz+tB4/8iUxES9Sl/jmLNcd6fQyMjC k+7FB8rfhaSFGoe8s5JbWleWW/y6g4AMMCk9lZX55sVPEFFefJJ6/G7Jh/+UloRK98 XfQTetawi4crHGgktTU9ZJiMCmIjGR5OF3Ag6oZYc2pX9Apw/cnyj6GEMyCy3oVYOt WbdOV1K8q+SwxQzfb8OWal3h7PH2g3YXoAnvnWewAFQcJ05exctaDtl8pOi1Q8PCy5 2Pdibgvo8WGV6Vew/LHI2NKnBj5NxNPtMJDDpc67ISir6MJQ7dEFY6MWQ6BH+dr8ab IuB4jWZFq1QE7RUNkfwY4BvrA14WEw504Uh2Aiv0ev/MgDEPExulq1BdOvPqbRv3Gh 04waAVK2Dl3pp7Gw4W/Yo0S01HlYBgt6FuQN5vsXlFmqwR0GtYrrvhhHJDoZxSuJeX 7MojRoA0tPsBJM0qLPlF7FNJ7KG3gghVr7u8qS14/BZUCzLL32l0gwnwA5V4O1qHpU IZxadP/8nXfYhFIYLfprO121pw4+NrA0zndNUzQF7Dy3Dg/hGo0y/gtVTv+5Pn3jC+ rA2LKu1uQJxceBf5cIl98reliCRQ4pPTHCi9f2q/N2g50YR9tNgwjHmH9Dwf+/0o5m ENc1RqoWa4sJXDkvElUna+D0= MIME-Version: 1.0 Date: Fri, 08 Apr 2022 09:44:25 +0200 From: Richard Kojedzinszky To: u-boot@lists.denx.de Subject: Radxa rock-pi-3a Message-ID: <774b3ce33306097071e79a6b9bb3b092@kojedz.in> X-Sender: richard@kojedz.in Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 08 Apr 2022 14:11:22 +0200 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean Dear community, I own a rock-pi-3a board with 8G ram. Right now, radxa's u-boot is capable of detecting the whole amount during boot. Upstream u-boot shows 1G of dram installed. I've started with evb-rk3568_defconfig. What I would like to achieve is that u-boot load grub-efi, to finally boot the operating system. Howewer, with radxa uboot, and using grub-efi, the kernel sees 4G only. If I boot the kernel image directly from radxa u-boot, the whole 8G is visible. I assume that efi is broken somehow, as I get multiple warnings from kernel regarding EFI firmware. Reading radxa's u-boot, it seems that it uses ATAGs do detect memory size. Am I in the right way? Would it be beneficial to port some of that code to upstream u-boot, or are there other solutions to detect correct memory size? Thanks in advance, Richard