Updating src tree:
P src/common/lib/libutil/snprintb.c
P src/doc/TODO.nvmm
P src/lib/libnvmm/libnvmm.3
P src/lib/libnvmm/libnvmm.c
P src/lib/libpthread/thrd.c
P src/lib/libutil/snprintb.3
P src/sys/arch/arm/acpi/gtmr_acpi.c
P src/sys/arch/ia64/acpi/madt.c
P src/sys/arch/ia64/ia64/mainbus.c
P src/
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.04.29.18.54.25 maxv src/doc/TODO.nvmm,v 1.3
2019.04.29.18.54.25 maxv src/lib/libnvmm/libnvmm.3,v 1.15
2019.04.29.18.54.25 maxv src/sys/dev/nvmm/
На 2019-04-29 в 18:34, John D. Baker написа:
> I managed to fire up another machine w/intel graphics I have. It uses:
>
> [...]
> i915drmkms0 at pci0 dev 2 function 0: Intel 82946GZ Integrated Graphics
> Device (rev. 0x02)
> [...]
> kern info: [drm] Memory usable by graphics device = 512M
> ker
The NetBSD Test Fixture wrote:
> This is an automatically generated notice of a NetBSD-current/i386
> build failure.
More relevant error messages, pointing to roy's commit:
--- dependall-tests ---
In file included from
/tmp/bracket/build/2019.04.29.16.39.58-i386/src/tests/sys/net/t_print.c:3
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2019.04.29.16.39.58.
An extract from the build.sh output follows:
--- dependall-net ---
cat
/tmp/bracket/build/
I managed to fire up another machine w/intel graphics I have. It uses:
[...]
i915drmkms0 at pci0 dev 2 function 0: Intel 82946GZ Integrated Graphics Device
(rev. 0x02)
[...]
kern info: [drm] Memory usable by graphics device = 512M
kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2
Date:Mon, 29 Apr 2019 12:02:10 +0300
From:Valery Ushakov
Message-ID: <20190429090210.gd11...@pony.stderr.spb.ru>
| E.g. in sys/arch/sh3/include/adcreg.h
Yes, I noticed many uses in arch/* ... I sampled a bunch of them,
and was mostly finding "old" style uses... So
> On Apr 29, 2019, at 5:34 PM, John D. Baker wrote:
>
> On my machines with i82G41 and i82Q45 devices w/video, the only thing
> that works is to use the "modesetting" driver for Xorg. On my machines
> with i82915 (drmkms) and i82810e (no drm at all) devices, no workarounds
> are needed.
Hi Joh
On Mon, 29 Apr 2019 16:19:41 +0800, Travis Paul wrote:
> Is anyone else seeing artifacts when using X in base, with i915 Intel
> graphics? [1][2][3]
Yes, a number of people have (myself included). See the threads
starting here:
http://mail-index.netbsd.org/current-users/2019/04/10/msg035540.
Is anyone else seeing artifacts when using X in base, with i915 Intel graphics?
[1][2][3]
I have 2 identical machines that experience this behavior, the artifacts never
stop appearing so X is fairly unusable. The artifacts are even worse with
fluxbox. I also see the following kernel errors oft
On Mon, Apr 29, 2019 at 10:29:43 +0700, Robert Elz wrote:
> I've done some searching (not exhaustive for sure) and the only
> thing I can find that uses 'F' in our tree that I can find is
> (which provided the newly added example in snprintb.3)
> which is missing that final NUL after the F field
11 matches
Mail list logo
