Re: u-boot-marsboard package naming issue
Rui-Xiang Guo <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.arm,gmane.os.netbsd.devel.pkgsrc.user |
|---|---|
| Message-ID | <Z6U8ce85niK8E8MT@picohive> |
On Tue, Jan 21, 2025 at 01:10:43PM +0800, Rui-Xiang Guo wrote: > On Mon, Jan 20, 2025 at 02:27:24PM +1100, matthew green wrote: > > Rui-Xiang Guo writes: > > > Hi, > > > I am going to create a u-boot package for the Embest MarS Board i.MX6Dual, > > > but not sure if the naming is appropriate. > > > There are another MarsBoard series with different SoCs from HAOYU. > > > Should it follow the UBOOT_CONFIG (marsboard_defconfig), or add the suffix > > > -imx6dl (although its FDT file is imx6q-marsboard.dtb)? > > > > i think i would rather have the -imx6dl suffix in the pkgsrc. > > most seem to be in the form of "board-cpu", vs "cpu-board", > > and it seems better to me for "u-boot-foo*" to match all the > > "foo" boards, than having to glob before and after. (only > > the "olinuxino" ones put the cpu before the board.) > > Thanks for the advice. > In some special cases, such as Google's Coral Dev Board, do we need to use > u-boot-coral-dev-board as the package name instead of > u-boot-phanbell-imx8mq according to its configs - imx8mq_phanbell_defconfig? It seems there are two options: a. Following its u-boot configs name b. Using our own rule I propose option a and leave the issue to u-boot himself. BTW, when creating arm-trusted-firmware-imx, I noted arm-trusted-firmware-sun50i-h6 and arm-trusted-firmware-sun50i_a64 Was one of them a typo? -rxg