Age | Commit message (Collapse) | Author |
|
with Allwinner SoCs and the presence of this particular miniroot is making
it hard to update U-Boot.
ok jsg@
|
|
|
|
confusing users with FFS attributes that only experts should
fiddle with. Actual use has withered away with functionality
rendered moot or moved elsewhere.
'-e' remains for the truly obscure corner cases.
Simply excise the code for now to see if hidden users/uses are
exposed. Further simplifications are possible if no such
users/uses surface.
ok with sthen@ millert@ kn@ otto@
|
|
Tested with Comfast CF-WU710N v4.
"go ahead" deraadt@
OK stsp@
|
|
No functional change.
ok patrick@
|
|
and the block devices work just fine.
|
|
All other dd invocations in installer code, INSTALL.* instructions and
dd(1) EXAMPLES use the disk's "raw device".
|
|
`_disk' (and related variables) hold disk names as "sd0" so that all else
can be constructed from it.
Fix the only two offenders across distrib/ which put start the variable
with "/dev/"; no functional change.
|
|
Same as done for arm64 already
|
|
root partition.
Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.
It also eliminates the extraneous output of -E that required
">/dev/null".
ok kn@
|
|
OK kettenis@ deraadt@
|
|
Build, boot and install tested by visa@
ok visa@
|
|
|
|
ok deraadt@
|
|
of running newfs_msdos, so fsck_msdos gets run behind the scenes. A few
architectures were missing this binary on their install media
noticed by sthen
|
|
Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.
Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.
Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)
This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.
OK deraadt
|
|
is required because of TLS servername for contacting ftp.openbsd.org, and
there is no point doing that in resolv.conf.tail because it is no longer used.
ok florian kn
|
|
OK deraadt who also helped making some space.
|
|
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@
|
|
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn
|
|
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.
tested by deraadt@
|
|
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).
ok kettenis@ patrick@
|
|
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..
|
|
moving progress bar during auto upgrade/install and a clean log
afterwards. ok deraadt@
|
|
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)
|
|
|
|
|
|
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..
|
|
|
|
the sme.
|
|
having two mysterious names, let's settle on one.
|
|
|
|
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.
|
|
|
|
repository and will not be in the next major release.
Switch to the am335x_evm target a FIT image for multiple am335x boards
including the BeagleBone Black.
u-boot-arm >= 2019.01p2 is now required to build armv7 releases.
ok deraadt@ phessler@
|
|
tracked that permission. Make the copy in $RELEASEDIR a+r
ok deraadt@
|
|
the hardware is detected. Add this to the miniroot/ramdisk.
requires dtb 4.18
U-Boot 2018.09 and later will load a dtb for 'SanCloud BeagleBone
Enhanced' if required which will be in dtb 4.19 after linux 4.19 is
released and can be added then.
|
|
script doesn't need support for the 3rd choice.
|
|
DESTDIR rather than reaching around in src. ok deraadt
|
|
As of U-Boot 2018.03 the mx6cuboxi U-Boot image will attempt to load
hummingboard2 dtbs automatically when hummingboard2 is detected.
Detection of som rev 1.5 will come in a later version of U-Boot.
These dtbs are included in dtb 4.16rc5 and later.
|
|
Requires U-Boot >= 2017.11 and dtb >= 4.15-rc1.
|
|
Some resizing scenarios can be done from within single user mode, but
resizing the root partition required you to bring your own growfs(8)
binary into the ramdisk environment. This commit adds growfs(8) to the
ramdisks (the ones that don't have space constraints) to simplify such
operations.
OK deraadt@
|
|
is found.
|
|
USB isn't supported. The installer turns out to have been broken on
BeagleBoard for over a year and no one noticed. The existing support
for OMAP3 in the kernel remains though it isn't clear if anyone has
tried it after the fdt changes went in.
ok patrick@ tom@ kettenis@ matthieu@
|
|
the hw.product sysctl to avoid the problem.
ok deraadt@ rpe@ kettenis@
|
|
according to the same logic for all architectures but sgi.
Consolidate setting them in one place in install.sub and incorporate
the sgi specific MDSETS and MDSANESETS.
Introduce MDSANESETS complementing MDSETS which makes the construction
of DEFAULTSETS, THESETS and SANESETS clearer in install.sub.
While here, adjust the comment about how MDSETS used now.
OK deraadt@
|
|
|
|
move forward deraadt@
|
|
boards. mx6qsabrelite (which sets fdt_addr) and nitrogen6q
(which sets fdtaddr). The difference seems to be the mx6qsabrelite
target uses a small loader in SPI connected flash which will load
the rest of u-boot from an SD card. The nitrogen6q target normally
loads all of u-boot from an image in flash and then searches for a
6x_bootscript file with u-boot commands on MMC and SATA.
While neither of them supports "Generic Distro Configuration" which
would automatically search for an EFI image, if they did fdt_addr
is intended to be used for a DTB in ROM, while fdt_addr_r is intended
to be used for a DTB in RAM.
Change the 6x_bootscript u-boot commands to load the DTB to
fdtaddr instead of fdt_addr as matthieu@ reported fdt_addr was not
present in the u-boot environment on his system.
|
|
|