From: Stefan Wahren <wahrenst@gmx.net>
To: Jens Maus <mail@jens-maus.de>, "Ivan T. Ivanov" <iivanov@suse.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v4 0/6] rpi5: initial support
Date: Tue, 23 Jan 2024 13:09:51 +0100 [thread overview]
Message-ID: <5ba843cd-eae7-46a2-88a5-d704556bf91b@gmx.net> (raw)
In-Reply-To: <36C77701-6838-4ACC-B6B0-62286CD0F7D1@jens-maus.de>
Hi Jens,
Am 23.01.24 um 12:11 schrieb Jens Maus:
> Hi,
>
>> Am 22.01.2024 um 15:16 schrieb Ivan T. Ivanov <iivanov@suse.de>:
>>
>> On 01-22 13:57, Ivan T. Ivanov wrote:
>>> I was able to enable early debug UART in U-Boot and I will try to
>>> find what is happening, once I get some free cycles.
>> Ok, this was relatively easy to find :-)
>>
>> New versions of EEPROM firmware change “kernel”/U-Boot load address
>> from 0x80000 to 0x200000. And because on RPi’s CONFIG_TEXT_BASE is
>> hardcoded to 0x80000 code run through the fields.
>>
>> Hopefully simple patch like bellow make it work fine in older and
>> newer EEPROM firmware versions.
> Thanks for this tiny but important fix on your patchset. In fact, I was able to verify that now with your latest v5 patchset for the initial rpi5 support even newer/latest rpi-eeprom versions work as expected and u-boot is chain loaded by the rpi boot loader.
thank you for testing. Could you please give your Tested-by to v5 or at
least parts of them?
>
> So thanks again for that fix and I am looking forward to seeing your patchset integrated and hopefully also maintained in future so that USB boot and GPIO support will be added in the near future.
>
> regards,
> jens
next prev parent reply other threads:[~2024-01-23 12:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 13:10 [PATCH v4 0/6] rpi5: initial support Jens Maus
2024-01-17 15:07 ` Ivan T. Ivanov
2024-01-17 15:13 ` Jens Maus
2024-01-17 15:23 ` Ivan T. Ivanov
2024-01-17 15:30 ` Jens Maus
2024-01-17 16:45 ` Ivan T. Ivanov
2024-01-17 23:06 ` Jens Maus
2024-01-18 8:33 ` Ivan T. Ivanov
2024-01-18 17:18 ` Jens Maus
2024-01-19 5:29 ` Ivan T. Ivanov
2024-01-19 7:21 ` Jens Maus
2024-01-19 9:20 ` Stefan Wahren
2024-01-19 10:49 ` Jens Maus
[not found] ` <sjmi6dftbgx56isfyjtaryehzq2iollwxm2etlspiygehh3n6v@k4ws56nsbgfn>
[not found] ` <6C9E5E0C-9C27-45A4-886F-8B8C641EF7A3@jens-maus.de>
2024-01-19 13:46 ` Ivan T. Ivanov
2024-01-19 13:54 ` Jens Maus
2024-01-19 14:06 ` Ivan T. Ivanov
2024-01-19 14:08 ` Jens Maus
2024-01-19 14:24 ` Ivan T. Ivanov
2024-01-19 16:12 ` Jens Maus
2024-01-19 16:29 ` Ivan T. Ivanov
2024-01-19 16:53 ` Jens Maus
2024-01-19 21:26 ` Jens Maus
2024-01-20 9:22 ` Stefan Wahren
2024-01-20 9:48 ` Jens Maus
2024-01-20 10:50 ` Stefan Wahren
2024-01-22 11:57 ` Ivan T. Ivanov
2024-01-22 14:16 ` Ivan T. Ivanov
2024-01-22 14:30 ` Mark Kettenis
2024-01-22 18:01 ` Tom Rini
2024-01-23 11:11 ` Jens Maus
2024-01-23 12:09 ` Stefan Wahren [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-10 12:29 Ivan T. Ivanov
2024-01-22 13:46 ` Matthias Brugger
2024-09-19 9:36 ` Stefan Agner
2024-09-19 9:52 ` Ivan T. Ivanov
2024-09-19 14:01 ` Stefan Agner
2024-09-19 14:22 ` Ivan T. Ivanov
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=5ba843cd-eae7-46a2-88a5-d704556bf91b@gmx.net \
--to=wahrenst@gmx.net \
--cc=iivanov@suse.de \
--cc=mail@jens-maus.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.