From: Jesse Taube <mr.bossman075@gmail.com>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Cc: u-boot-custodians@lists.denx.de, u-boot-board-maintainers@lists.denx.de
Subject: Re: [ANN] U-Boot v2022.01-rc3 released
Date: Mon, 29 Nov 2021 21:35:52 -0500 [thread overview]
Message-ID: <14fdf0d7-59b5-83b3-b36d-86c529d04f28@gmail.com> (raw)
In-Reply-To: <20211129162831.GR24579@bill-the-cat>
On 11/29/21 11:28, Tom Rini wrote:
> Hey all,
>
> It's been two weeks since v2022.01-rc2, so here's -rc3.
>
> To repeat what I said with -rc2, we've enabled issue tracking on our
> gitlab instance. You can sign up and then be able to file issues at:
> https://source.denx.de/groups/u-boot/-/issues
>
> This is intended for everyone to be able to use, both custodians for
> their own needs (you can see for example Heinrich has filed something
> for UEFI and LMB) as well as users to just report bugs so they don't
> feel like they're lost in the mailing list.
>
> As noted with the last release, the -next branch is open and I'll sync
> in -rc3 shortly. Please feel free to get a PR ready now if you're able.
>
> In terms of a changelog,
> git log --merges v2022.01-rc2..v2022.01-rc3
> contains what I've pulled but as always, better PR messages and tags
> will provide better results here.
>
> So we're now looking at regular releases every other Monday, and with
> final release on January 10th, 2022. Thanks all!
>
Hey tom,
Thank you for the update as always!
I have a question about a recent commit, I hope its okay to ask here.
In commit cd82f199852d88218e1f17f5ec07cdd9112a89c4
In arch/arm/lib/relocate.S:81 on my SBC it returns an invalid value.
My soc is Thumb2 but the instruction `adr r3, relocate_code`
assembles to `subw r3, pc, #3` which is not 32bit aligned. If i change
the instruction to `adr.w r3, relocate_code` it evaluates to `subw r3,
pc, #4`, which is.
There is a slight problem as it seems to work fine on my laptop using
Debian bullseye, but on my Desktop where I found this I'm running sid.
They are both gcc-10. I have yet to find a way to consistently replicate it.
What are your thoughts of this?
Thanks,
Jesse
next prev parent reply other threads:[~2021-11-30 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 16:28 [ANN] U-Boot v2022.01-rc3 released Tom Rini
2021-11-30 2:35 ` Jesse Taube [this message]
2021-11-30 19:36 ` Tom Rini
2022-07-06 14:31 ` Jesse Taube
2022-07-06 14:47 ` Tom Rini
2022-07-06 16:34 ` Jesse Taube
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=14fdf0d7-59b5-83b3-b36d-86c529d04f28@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox