Updating src tree:
P src/build.sh
P src/distrib/sets/lists/man/mi
P src/lib/libnvmm/libnvmm.c
P src/share/man/man4/man4.amiga/Makefile
U src/share/man/man4/man4.amiga/a2kbbc.4
U src/share/man/man4/man4.amiga/a34kbbc.4
U src/share/man/man4/man4.amiga/drbbc.4
P src/sys/arch/amd64/amd64/cpufunc.S
U
On 02.05.2019 01:54, NetBSD Test Fixture wrote:
> This is an automatically generated notice of a new failure of the
> NetBSD test suite.
>
> The newly failing test case is:
>
> usr.bin/gdb/t_regress:pie
>
Addressed in sys_ptrace_common.c 1.5
It looks like a bug in GDB, but for now I will
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
usr.bin/gdb/t_regress:pie
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The following commits were made
Thanks - that got me beyond screen initialization.
but
bootm 8200 - $fdt_addr_r root=ld0a console=fb
asked for the root device, swap, fs tape and init - so the parameters
probably did not reach the kernel at all.
starting X didn't show anything on the 4K screen, X seemed to be running
Remove the following devices from your kernel config and the kernel should
use simplefb instead: sunxidebe, sunxitcon, sunxihdmi, sunxidep
I just peeked at the code quickly and it looks like the DE drivers are
blindly using the display's advertised preferred mode without taking its
own
I tried -current with my Bananapi an had limited success:
Using the first steps copying the image armv7 and the 2018.05 u-boot I
found the u-boot load attempting to perform a dhcp boot as nothing was
found on the mmc drive in autoboot. Did I miss somethnig to set up there ?
I finally got a
