Re: hpcarm/NETBOOKPRO failed

2019-04-13 Thread Tetsuya Isaki
At Sun, 14 Apr 2019 13:56:40 +1000, matthew green wrote: > > config hpcarm/conf/NETBOOKPRO failed. > > Does someone look this? > > > > % /var/obj/current/hpcarm/tools/bin/nbconfig -s /autobuild/current/src/sys > > -b /var/obj/current/hpcarm/obj/sys/arch/hpcarm/compile/NETBOOKPRO NETBOOKPRO > > NE

re: hpcarm/NETBOOKPRO failed

2019-04-13 Thread matthew green
Tetsuya Isaki writes: > config hpcarm/conf/NETBOOKPRO failed. > Does someone look this? > > % /var/obj/current/hpcarm/tools/bin/nbconfig -s /autobuild/current/src/sys -b > /var/obj/current/hpcarm/obj/sys/arch/hpcarm/compile/NETBOOKPRO NETBOOKPRO > NETBOOKPRO:180: seeprom*: extraneous locator: siz

hpcarm/NETBOOKPRO failed

2019-04-13 Thread Tetsuya Isaki
config hpcarm/conf/NETBOOKPRO failed. Does someone look this? % /var/obj/current/hpcarm/tools/bin/nbconfig -s /autobuild/current/src/sys -b /var/obj/current/hpcarm/obj/sys/arch/hpcarm/compile/NETBOOKPRO NETBOOKPRO NETBOOKPRO:180: seeprom*: extraneous locator: size *** Stop. % Thanks, --- Tetsuya

daily CVS update output

2019-04-13 Thread NetBSD source update
Updating src tree: P src/distrib/utils/embedded/conf/armv7.conf P src/external/gpl3/gcc/dist/gcc/config/riscv/netbsd.h P src/external/gpl3/gcc/lib/libgcc/arch/riscv64/defs.mk P src/external/gpl3/gdb/dist/gdb/arm-bsd-tdep.c P src/external/gpl3/gdb/dist/gdb/arm-nbsd-nat.c P src/external/gpl3/gdb/di

Re: Funky Display Output:

2019-04-13 Thread John D. Baker
I suppose as an outlier data point, the intel driver works fine on an ancient i82810e-based system with no DRM/KMS nor UMS at all. The machine does need an "xorg.conf", but only to define the limits of the CRT monitor--no "Device" section. I did have to tweak the "Display" subsection to keep it f

Re: com(4) dialout device behavior change?

2019-04-13 Thread Greg Troxel
"John D. Baker" writes: > On a netbsd-8/amd64 system I have no problem using 'cu' to connect to > the serial console of another system (sparc, netbsd-8.99.37) with a > "three-wire" serial cable: > > Excerpt from "dmesg.boot": > > com0 at acpi0 (UAR1, PNP0501-1): io 0x3f8-0x3ff irq 4 > com0: n

Re: com(4) dialout device behavior change?

2019-04-13 Thread John D. Baker
On Sat, 13 Apr 2019, John D. Baker wrote: > I seem to recall a change with some of the signals now required before > dialout devices work. I'll need to check my adapter to make sure > everything that I need to loop back is correct. The adapter I'm using is a DB25->RJ11 (6P6C) wired to pass TX/RX

com(4) dialout device behavior change?

2019-04-13 Thread John D. Baker
On a netbsd-8/amd64 system I have no problem using 'cu' to connect to the serial console of another system (sparc, netbsd-8.99.37) with a "three-wire" serial cable: Excerpt from "dmesg.boot": com0 at acpi0 (UAR1, PNP0501-1): io 0x3f8-0x3ff irq 4 com0: ns16550a, working fifo $ cu -9600 -l

Re: Funky Display Output

2019-04-13 Thread maya
I think it's the kernel too. I have a reduced way of reproducing it. env LIBGL_ALWAYS_SOFTWARE=1 glmark2 (from pkgsrc) will be visibly corrupt. env LIBGL_ALWAYS_SOFTWARE=1 ktruss -i glmark2 > /dev/null or a second glmark2 instance seemed to make it go away. I think this difference means it might