[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
Steve Langasek
2072490 at bugs.launchpad.net
Fri Jul 12 15:23:36 UTC 2024
arch/riscv/cpu/mpfs/cpu.c, arch/riscv/cpu/mpfs/dram.c,
arch/riscv/cpu/pic64gx/cpu.c, arch/riscv/cpu/pic64gx/dram.c are new
files in u-boot-pic64gx-20240624 listed as 'Copyright (C) 2018, Bin Meng
<bmeng.cn at gmail.com>'. Please include this in debian/copyright.
arch/riscv/dts/mpfs-tysom-m.dts lists Copyright (C) 2020-2022 - Aldec
which is not in debian/copyright. (It also lists Copyright (C) 2022-2023
- Conor Dooley <conor.dooley at microchip.com> but we can presume this is
incorrect and should be Microchip, which is listed in debian/copyright.)
I also see that this source builds an Arch: all binary package. The
convention is that the u-boot binary packages declare the architectures
that they are used on (riscv64); we don't want to install u-boot-pic64gx
on an amd64 system.
Ok to leave drivers/dma/MCD_tasks.c in the source.
And diffing debian/copyright against the Debian v2023.07 package instead
of the latest looks sensible, so no changes needed there.
That leaves the above three issues, plus the upstream version problem.
--
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2072490
Title:
[needs-packaging] U-Boot for Microchip PIC64GX
Status in Ubuntu:
New
Bug description:
We want to support the upcoming Microchip PIC64GX board. Unfortunately
upstreaming of U-Boot has not started yet. Due to the number of
differences between our U-Boot 2024.01 and the vendor U-Boot it is not
trivial to add board support to our existing U-Boot. The best interim
solution is packaging the vendor U-Boot. Once upstreaming has occurred
we can sun-set the vendor U-Boot package and replace it by the u-boot-
microchip package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions
More information about the Ubuntu-sponsors
mailing list