From: Jonas Karlman <jonas@kwiboo.se>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: linux-rockchip@lists.infradead.org
Subject: Re: Thinking about firmware and hardware description for latest Rockchip platforms
Date: Tue, 22 Oct 2024 21:28:24 +0200 [thread overview]
Message-ID: <0953a331-9d2e-4094-a524-defa7a009a71@kwiboo.se> (raw)
In-Reply-To: <9539aec2-09d2-4da8-9fbb-9914881a493d@linaro.org>
Hi Marcin,
On 2024-10-22 20:47, Marcin Juszkiewicz wrote:
> W dniu 22.10.2024 o 19:43, Jonas Karlman pisze:
>
>
>> and be sure to leave around 16 MiB of space on SD-card/eMMC before
>> first partition to not overwrite any existing bootloader.
> Let pretend that we are nice people and use on-board SPI flash for
> firmware parts.
Hehe, use of SPI flash or eMMC boot hw partitions would be optimal :-)
However, lots of boards does not have SPI flash, and RK BootROM does not
load initial playload from eMMC boot hw partitions.
At least second stage bootloader can be made to support reading next
stage from eMMC boot hw partition, for U-Boot I sent [1] as an RFC.
But I fear that may cause more/different problems/issues for end-users.
[1] https://lore.kernel.org/r/20240202001129.530825-1-jonas@kwiboo.se/
Regards,
Jonas
>
> Please (with cherry on top).
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-10-22 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 16:53 Thinking about firmware and hardware description for latest Rockchip platforms Shimrra Shai
2024-10-22 17:43 ` Jonas Karlman
2024-10-22 18:47 ` Marcin Juszkiewicz
2024-10-22 19:28 ` Jonas Karlman [this message]
2024-10-23 2:46 ` Dragan Simic
2024-10-23 17:35 ` Shimrra Shai
2024-10-24 18:00 ` Dragan Simic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0953a331-9d2e-4094-a524-defa7a009a71@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcin.juszkiewicz@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox