daily CVS update output

2019-01-15 Thread NetBSD source update
Updating src tree: P src/bin/sh/input.c P src/bin/sh/parser.c P src/lib/libc/gen/ctype.3 P src/sys/kern/init_sysctl.c P src/sys/kern/uipc_mbuf.c P src/tests/net/if_ipsec/t_ipsec.sh P src/usr.sbin/sysinst/msg.mi.pl Updating xsrc tree: Killing core files: Updating release-7 src tree (netbsd-7

Zero unexpected ATF test failures

2019-01-15 Thread Andreas Gustafsson
Hi all, I'm happy to report that today my amd64 bare metal testbed completed an ATF test run with zero unexpected failures, produding a line of all green in the monthly report: http://www.gson.org/netbsd/bugs/build/amd64-baremetal/commits-2019.01.html#2019.01.15.03.43.15 That's a first for th

Re: What happened to lmc

2019-01-15 Thread Martin Husemann
On Tue, Jan 15, 2019 at 02:28:20PM +0100, Riccardo Mottola wrote: > Hi, > > I updated and am compiling a new kernel... > > /usr/src/sys/arch/amd64/conf/HP620:791: lmc*: unknown device `lmc' > *** Stop. The code has been removed, just drop that line from your kernel config. Martin

What happened to lmc

2019-01-15 Thread Riccardo Mottola
Hi, I updated and am compiling a new kernel... /usr/src/sys/arch/amd64/conf/HP620:791: lmc*: unknown device `lmc' *** Stop. ERROR: nbconfig failed for HP620 do I need to regenerate my configure or is something unclean? Thanks Riccardo

correction (Re: PCI_PRODUCT(pa->pa_id) is wrong (Re: kern info: [drm] failed to find VBIOS tables

2019-01-15 Thread 藤原 誠 Makoto Fujiwara
I was probably wrong. I have several Let's Note CF, the model LCD works may have unmatched number: rom_product PCI_PRODCUT(pa->pa_id) LCD works J10 46 46OK SX2106 166-- SX3406 a16OK N10106