Fix WWW in parent/child ports

Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
 a) just using the pkg-descr from the parents
 b) or had their own separate pkg-descr with custom WWW

Use WWW?= in parents when the child's WWW is different.

Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.

Approved by:	portmgr (implicit)

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

u-boot-*: Remove U_BOOT_SLAVE_PORTREVISION_2021.04

This is not needed anymore as we have 2921.07 now.

sysutils/u-boot-*: Remove ubldr support

We have been using loader.efi on armv7 for a long time now.
Remove support for booting with ubldr and the needed patches that were
never upstreamed.
While here add CONFIG_EFI_GRUB_ARM32_WORKAROUND=y in the Fragment as it's
needed to have the cache flushed for us when loader.efi is started.

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

sysutils/u-boot-*: Update to 2021.04

Remove # $FreeBSD$ from Makefiles.

sysutils/u-boot-beaglebone: Fix eMMC boot

Due to rename of CONFIG_NAND -> CONFIG_MTD_RAW_NAND the BBB will not boot from
eMMC.

https://github.com/u-boot/u-boot/commit/88718be3001055fa2801a44ab10570279b3f2cb7

https://github.com/u-boot/u-boot/commit/d4c2f6b7e3e2bfd297367d292aa641095c7a18e2

Submitted by:	 Oskar Holmund (oskar.holmlund@ohdata.se)
Differential Revision:	https://reviews.freebsd.org/D25190

Use HTTPS as possible

u-boot: Update to v2019.10

Update u-boot to its latest version.
For RK3399 we now use SPL+TPL from u-boot, no need for RockChip blob.
Remove one efi related patch that isn't needed anymore.

Tested-on: Pine64-LTS, Rock64, Rockpro64, BBB, RPI2, OrangePi One

u-boot-beaglebone: Add some fragment data to disable NAND

Since u-boot merged the beaglebone defconfig with the am335x_evm ones
eMMC support is seriously broken.
Disabling NAND support (which isn't present on BBB) make this works again
as they share some pins.
Also remove the legacy_mmc targets as it is Linux centric.

Clean up trailing spaces

Approved by:	manu
Sponsored by:	The FreeBSD Foundation

sysutils/u-boot: Update to 2019.04

Beaglebone slave port change its defconfig.
ZYNC related u-boot are broken.

sysutils/u-boot-master etc.: u-boot Improvement for 2018.07

 - Add metadata for IMX6 family
 - While here rename the riotboard family to IMX6 as it should have been
 - Remove the cache patches, they aren't needed anymore.
   I should have checked that with the 2018.07 update
 - beaglebone use a custom bootcmd that calls envboot, this command will try
   to load and source the file boot.scr (u-boot script) from the mmc.
   For some reason it seems to corrupts some memory or something because
   loading and executing ubldr.bin after running this command will either
   hang or cause an exception on undefined instruction.
   I'll check with upstream but in the meantime use a special fragment
   that redefine the bootcmd.
   Note that since u-boot will load the environment from the eMMC, one need
   to 'env default -f -a; saveenv' to have the bootcmd variable correctly
redefined.

Reviewed by:	imp
Approved by:	imp
Differential Revision:	https://reviews.freebsd.org/D16599

Consolidate maintainership of various u-boot ports under u-boot@.

Submitted by:		manu
Differential Revision:	D15884

Update the instruction and description of the u-boot ports which use
u-boot-master.

Submitted by:		manu
Differential Revision:	D15883

Roll forward to u-boot v2017.01. Many thanks to manu@ for cleaning up
our patches to u-boot and getting them upstreamed.

Future commits will roll other families over to this as testing on
them is completed.

Remove the files added as a stupid workaround for git svn.

Create a new u-boot-master port to consolidate all different u-boot
ports.  Switch to using my github branch for grabbing ports.  Convert
the Beaglebone family of ports over to using the new setup.

Fix hardcoded package description path

Submitted by:	mat

Fix few style violations in u-boot ports:

- GMAKE -> MAKE_CMD, MAKE_CMD is always set to required make implementation
- CP -> INSTALL_DATA, INSTALL_DATA makes sure files are always installed
  with proper permissions
- sysutils/u-boot-rpi: include missed files installed in STAGEDIR in PLIST_FILES

PR:		210982
Submitted by:	myself
Approved by:	maintainers timeout

Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight

Use gcc 4.9.2 to cross-compile u-boot for beaglebone.

Approved by:	rpaulo

Leave caches enabled when launching u-boot, it speeds up loader(8) and
the kernel can tolerate being entered with caches enabled as of r276445.

Approved by:	imp

Changes to allow booting from eMMC on a Beaglebone Black.  Using the
right config (am335x_boneblack_defconfig) is a big part of that.  The
u-boot environment is also pretty extensively changed, both to support
eMMC (choosing which device to load freebsd from) and to further trim
and clean up the environment so it's easier to read and understand.

In an ideal world, the 'mmc 0' device would always be the one u-boot was
loaded from and 'mmc 1' would be 'the other' device.  That's what the
Wandboard u-boot does, and it would be easy enough to do on Beaglebone too
except I couldn't find a way to pass the load device number from MLO which
knows it to the main u-boot.  So for now the removable sdcard is device 0
and the onboard eMMC is device 1, and it prefers to boot from sdcard if
it's present and has ubldr on it (unless the user has set the 'fatdev' env
var, in which case it is used).

Approved by:	imp

Cleanup plist

FreeBSD customized Beagle Bone Black u-boot boot loader.