mbox series

[PULL,SUBSYSTEM,qemu-pseries] pseries: Update SLOF firmware image

Message ID 20220719075930.315237-1-aik@ozlabs.ru
State New
Headers show
Series [PULL,SUBSYSTEM,qemu-pseries] pseries: Update SLOF firmware image | expand

Pull-request

git@github.com:aik/qemu.git tags/qemu-slof-20220719

Message

Alexey Kardashevskiy July 19, 2022, 7:59 a.m. UTC
The following changes since commit d2066bc50d690a6605307eaf0e72a9cf51e6fc25:

  target/ppc: Check page dir/table base alignment (2022-07-18 13:59:43 -0300)

are available in the Git repository at:

  git@github.com:aik/qemu.git tags/qemu-slof-20220719

for you to fetch changes up to 17c1ad657904787b1d986fb4c85431fee006a6ea:

  pseries: Update SLOF firmware image (2022-07-19 17:50:46 +1000)

----------------------------------------------------------------
Alexey Kardashevskiy (1):
      pseries: Update SLOF firmware image

 docs/system/ppc/pseries.rst |   2 +-
 pc-bios/README              |   2 +-
 pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
 roms/SLOF                   |   2 +-
 4 files changed, 3 insertions(+), 3 deletions(-)


*** Note: this is not for master, this is for pseries
*** Note2: this has not sync'd to git.qemu.org but softfreeze is
too soon so I am posting it anyway.


The image grew in size because of change of the toolchain from
native PPC to cross on x86.


The only change is that now SLOF can also boot big endian zImage
but kernel-addr=0 is still required.

Comments

Alexey Kardashevskiy July 19, 2022, 8 a.m. UTC | #1
oops wrong maintainer :)



On 19/07/2022 17:59, Alexey Kardashevskiy wrote:
> The following changes since commit d2066bc50d690a6605307eaf0e72a9cf51e6fc25:
> 
>    target/ppc: Check page dir/table base alignment (2022-07-18 13:59:43 -0300)
> 
> are available in the Git repository at:
> 
>    git@github.com:aik/qemu.git tags/qemu-slof-20220719
> 
> for you to fetch changes up to 17c1ad657904787b1d986fb4c85431fee006a6ea:
> 
>    pseries: Update SLOF firmware image (2022-07-19 17:50:46 +1000)
> 
> ----------------------------------------------------------------
> Alexey Kardashevskiy (1):
>        pseries: Update SLOF firmware image
> 
>   docs/system/ppc/pseries.rst |   2 +-
>   pc-bios/README              |   2 +-
>   pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
>   roms/SLOF                   |   2 +-
>   4 files changed, 3 insertions(+), 3 deletions(-)
> 
> 
> *** Note: this is not for master, this is for pseries
> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
> too soon so I am posting it anyway.
> 
> 
> The image grew in size because of change of the toolchain from
> native PPC to cross on x86.
> 
> 
> The only change is that now SLOF can also boot big endian zImage
> but kernel-addr=0 is still required.
>
Daniel Henrique Barboza July 20, 2022, 4:08 p.m. UTC | #2
Hey,

On 7/19/22 04:59, Alexey Kardashevskiy wrote:
> The following changes since commit d2066bc50d690a6605307eaf0e72a9cf51e6fc25:
> 
>    target/ppc: Check page dir/table base alignment (2022-07-18 13:59:43 -0300)
> 
> are available in the Git repository at:
> 
>    git@github.com:aik/qemu.git tags/qemu-slof-20220719
> 
> for you to fetch changes up to 17c1ad657904787b1d986fb4c85431fee006a6ea:
> 
>    pseries: Update SLOF firmware image (2022-07-19 17:50:46 +1000)
> 
> ----------------------------------------------------------------
> Alexey Kardashevskiy (1):
>        pseries: Update SLOF firmware image
> 
>   docs/system/ppc/pseries.rst |   2 +-
>   pc-bios/README              |   2 +-
>   pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
>   roms/SLOF                   |   2 +-
>   4 files changed, 3 insertions(+), 3 deletions(-)
> 
> 
> *** Note: this is not for master, this is for pseries
> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
> too soon so I am posting it anyway.

I forgot to send a reply yesterday, sorry.

Don't worry about rushing this SLOF pull. Given that this build doesn't
have bug fixes we can wait to pull it in 7.2. You'll have the time to
sync it up with git.qemu.org and so on.


Thanks,


Daniel

> 
> 
> The image grew in size because of change of the toolchain from
> native PPC to cross on x86.
> 
> 
> The only change is that now SLOF can also boot big endian zImage
> but kernel-addr=0 is still required.
> 
>
Alexey Kardashevskiy July 21, 2022, 8:14 a.m. UTC | #3
On 21/07/2022 02:08, Daniel Henrique Barboza wrote:
> Hey,
> 
> On 7/19/22 04:59, Alexey Kardashevskiy wrote:
>> The following changes since commit 
>> d2066bc50d690a6605307eaf0e72a9cf51e6fc25:
>>
>>    target/ppc: Check page dir/table base alignment (2022-07-18 
>> 13:59:43 -0300)
>>
>> are available in the Git repository at:
>>
>>    git@github.com:aik/qemu.git tags/qemu-slof-20220719
>>
>> for you to fetch changes up to 17c1ad657904787b1d986fb4c85431fee006a6ea:
>>
>>    pseries: Update SLOF firmware image (2022-07-19 17:50:46 +1000)
>>
>> ----------------------------------------------------------------
>> Alexey Kardashevskiy (1):
>>        pseries: Update SLOF firmware image
>>
>>   docs/system/ppc/pseries.rst |   2 +-
>>   pc-bios/README              |   2 +-
>>   pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
>>   roms/SLOF                   |   2 +-
>>   4 files changed, 3 insertions(+), 3 deletions(-)
>>
>>
>> *** Note: this is not for master, this is for pseries
>> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
>> too soon so I am posting it anyway.
> 
> I forgot to send a reply yesterday, sorry.
> 
> Don't worry about rushing this SLOF pull. Given that this build doesn't
> have bug fixes we can wait to pull it in 7.2. You'll have the time to
> sync it up with git.qemu.org and so on.


Well, the git.qemu.org is still not updated, and I have no control over 
this process anyway, who manages it?


> 
> Thanks,
> 
> 
> Daniel
> 
>>
>>
>> The image grew in size because of change of the toolchain from
>> native PPC to cross on x86.
>>
>>
>> The only change is that now SLOF can also boot big endian zImage
>> but kernel-addr=0 is still required.
>>
>>
Peter Maydell July 21, 2022, 8:48 a.m. UTC | #4
On Thu, 21 Jul 2022 at 09:19, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 21/07/2022 02:08, Daniel Henrique Barboza wrote:
> > Hey,
> >
> > On 7/19/22 04:59, Alexey Kardashevskiy wrote:
> >> Alexey Kardashevskiy (1):
> >>        pseries: Update SLOF firmware image
> >>
> >>   docs/system/ppc/pseries.rst |   2 +-
> >>   pc-bios/README              |   2 +-
> >>   pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
> >>   roms/SLOF                   |   2 +-
> >>   4 files changed, 3 insertions(+), 3 deletions(-)
> >>
> >>
> >> *** Note: this is not for master, this is for pseries
> >> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
> >> too soon so I am posting it anyway.
> >
> > I forgot to send a reply yesterday, sorry.
> >
> > Don't worry about rushing this SLOF pull. Given that this build doesn't
> > have bug fixes we can wait to pull it in 7.2. You'll have the time to
> > sync it up with git.qemu.org and so on.
>
>
> Well, the git.qemu.org is still not updated, and I have no control over
> this process anyway, who manages it?

Syncing of those git repos is supposed to be automatic, but
occasionally something falls over. Stefan, who looks after
the sync process ?

Alexey, which specific repo is not syncing ?

thanks
-- PMM
Alexey Kardashevskiy July 21, 2022, 9:03 a.m. UTC | #5
On 21/07/2022 18:48, Peter Maydell wrote:
> On Thu, 21 Jul 2022 at 09:19, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>> On 21/07/2022 02:08, Daniel Henrique Barboza wrote:
>>> Hey,
>>>
>>> On 7/19/22 04:59, Alexey Kardashevskiy wrote:
>>>> Alexey Kardashevskiy (1):
>>>>         pseries: Update SLOF firmware image
>>>>
>>>>    docs/system/ppc/pseries.rst |   2 +-
>>>>    pc-bios/README              |   2 +-
>>>>    pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
>>>>    roms/SLOF                   |   2 +-
>>>>    4 files changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>>
>>>> *** Note: this is not for master, this is for pseries
>>>> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
>>>> too soon so I am posting it anyway.
>>>
>>> I forgot to send a reply yesterday, sorry.
>>>
>>> Don't worry about rushing this SLOF pull. Given that this build doesn't
>>> have bug fixes we can wait to pull it in 7.2. You'll have the time to
>>> sync it up with git.qemu.org and so on.
>>
>>
>> Well, the git.qemu.org is still not updated, and I have no control over
>> this process anyway, who manages it?
> 
> Syncing of those git repos is supposed to be automatic, but
> occasionally something falls over. Stefan, who looks after
> the sync process ?
> 
> Alexey, which specific repo is not syncing ?


https://git.qemu.org/git/SLOF.git from git@github.com:aik/SLOF.git

For example, the latest is:
https://github.com/aik/SLOF/releases/tag/qemu-slof-20220719

But it has not made it to where git.qemu.org redirects to:
https://gitlab.com/qemu-project/SLOF
Stefan Hajnoczi July 21, 2022, 6:40 p.m. UTC | #6
On Thu, 21 Jul 2022 at 04:49, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Thu, 21 Jul 2022 at 09:19, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> > On 21/07/2022 02:08, Daniel Henrique Barboza wrote:
> > > Hey,
> > >
> > > On 7/19/22 04:59, Alexey Kardashevskiy wrote:
> > >> Alexey Kardashevskiy (1):
> > >>        pseries: Update SLOF firmware image
> > >>
> > >>   docs/system/ppc/pseries.rst |   2 +-
> > >>   pc-bios/README              |   2 +-
> > >>   pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
> > >>   roms/SLOF                   |   2 +-
> > >>   4 files changed, 3 insertions(+), 3 deletions(-)
> > >>
> > >>
> > >> *** Note: this is not for master, this is for pseries
> > >> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
> > >> too soon so I am posting it anyway.
> > >
> > > I forgot to send a reply yesterday, sorry.
> > >
> > > Don't worry about rushing this SLOF pull. Given that this build doesn't
> > > have bug fixes we can wait to pull it in 7.2. You'll have the time to
> > > sync it up with git.qemu.org and so on.
> >
> >
> > Well, the git.qemu.org is still not updated, and I have no control over
> > this process anyway, who manages it?
>
> Syncing of those git repos is supposed to be automatic, but
> occasionally something falls over. Stefan, who looks after
> the sync process ?

I can help out with GitLab repo syncing. It should work for existing
qemu-project group repos. We currently cannot set up syncing for new
repos because qemu-project is in the GitLab Free tier.

The SLOF repo was last synced automatically 6 days ago. I'm unable to
start a new sync operation and maybe the current one is stuck (the web
interface claims the sync is currently updating...).

Peter: are you able to fetch https://github.com/aik/SLOF and push to
https://gitlab.com/qemu-project/SLOF to manually sync the repo?

I currently don't have easy access to my ssh key but let me know if
you can't and I'll see what I can do. Tomorrow I should have access
again.

Thanks,
Stefan


Stefan
Peter Maydell July 21, 2022, 6:51 p.m. UTC | #7
On Thu, 21 Jul 2022 at 19:41, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> The SLOF repo was last synced automatically 6 days ago. I'm unable to
> start a new sync operation and maybe the current one is stuck (the web
> interface claims the sync is currently updating...).
>
> Peter: are you able to fetch https://github.com/aik/SLOF and push to
> https://gitlab.com/qemu-project/SLOF to manually sync the repo?

End-of-week for me, but I can look at it on Monday...

thanks
-- PMM
Stefan Hajnoczi July 21, 2022, 10:30 p.m. UTC | #8
On Thu, Jul 21, 2022, 14:52 Peter Maydell <peter.maydell@linaro.org> wrote:

> On Thu, 21 Jul 2022 at 19:41, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > The SLOF repo was last synced automatically 6 days ago. I'm unable to
> > start a new sync operation and maybe the current one is stuck (the web
> > interface claims the sync is currently updating...).
> >
> > Peter: are you able to fetch https://github.com/aik/SLOF and push to
> > https://gitlab.com/qemu-project/SLOF to manually sync the repo?
>
> End-of-week for me, but I can look at it on Monday...
>

I will sync it manually tomorrow.

Have a nice weekend!

Stefan

>
> thanks
> -- PMM
>
Stefan Hajnoczi July 22, 2022, 12:35 a.m. UTC | #9
On Thu, 21 Jul 2022 at 05:06, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 21/07/2022 18:48, Peter Maydell wrote:
> > On Thu, 21 Jul 2022 at 09:19, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> >> On 21/07/2022 02:08, Daniel Henrique Barboza wrote:
> >>> Hey,
> >>>
> >>> On 7/19/22 04:59, Alexey Kardashevskiy wrote:
> >>>> Alexey Kardashevskiy (1):
> >>>>         pseries: Update SLOF firmware image
> >>>>
> >>>>    docs/system/ppc/pseries.rst |   2 +-
> >>>>    pc-bios/README              |   2 +-
> >>>>    pc-bios/slof.bin            | Bin 992384 -> 995176 bytes
> >>>>    roms/SLOF                   |   2 +-
> >>>>    4 files changed, 3 insertions(+), 3 deletions(-)
> >>>>
> >>>>
> >>>> *** Note: this is not for master, this is for pseries
> >>>> *** Note2: this has not sync'd to git.qemu.org but softfreeze is
> >>>> too soon so I am posting it anyway.
> >>>
> >>> I forgot to send a reply yesterday, sorry.
> >>>
> >>> Don't worry about rushing this SLOF pull. Given that this build doesn't
> >>> have bug fixes we can wait to pull it in 7.2. You'll have the time to
> >>> sync it up with git.qemu.org and so on.
> >>
> >>
> >> Well, the git.qemu.org is still not updated, and I have no control over
> >> this process anyway, who manages it?
> >
> > Syncing of those git repos is supposed to be automatic, but
> > occasionally something falls over. Stefan, who looks after
> > the sync process ?
> >
> > Alexey, which specific repo is not syncing ?
>
>
> https://git.qemu.org/git/SLOF.git from git@github.com:aik/SLOF.git
>
> For example, the latest is:
> https://github.com/aik/SLOF/releases/tag/qemu-slof-20220719
>
> But it has not made it to where git.qemu.org redirects to:
> https://gitlab.com/qemu-project/SLOF

Hi Alexey,
I have manually pushed the qemu-slof-20220719 tag and latest master to
QEMU's GitLab mirror.

The automatic GitLab mirror job should work. We just don't have much
control over it and maybe it got stuck ~6 days ago and couldn't pick
up your latest changes. Please let me know if you have mirroring
issues again in the future.

Thanks,
Stefan