Re: usb device modifying state of another driver on plug/unplug event
bl...@internode.on.net (Brett Lymn) writes: >"Needs Work(tm)" ... at the moment it looks very disk device focuessed: ># drvctl -l >root mainbus0 >root dk0 >root dk1 >root dk2 >root dk3 >root dk4 >root dk5 >root dk6 >root dk7 >root dk8 >root dk9 >root dk10 >root dk11 >root swcrypto0 >root cgd0 >root vnd0 You missed to list all the things hanging of mainbus. You see the disk devices because they all attach at the root of the tree. Here is an example what devpubd sees. # Initial event when devpubd is started device-attach mainbus0 dk0 dk1 dk2 dk3 dk4 dk5 swcrypto0 iscsi0 vnd0 vnd1 vnd2 vnd3 ioapic0 cpu0 cpu1 cpu2 cpu3 acpi0 pci0 acpicpu0 coretemp0 acpicpu1 acpicpu2 coretemp1 acpicpu3 acpiecdt0 hpet0 acpiec0 acpilid0 acpibut0 acpivga0 attimer1 pcppi1 pckbc1 pckbc2 acpibat0 acpiacad0 thinkpad0 acpiwmi0 acpiwmi1 acpitz0 acpiout0 acpiout1 acpiout2 acpiout3 acpiout4 acpiout5 acpiout6 acpiout7 spkr0 midi0 sysbeep0 pckbd0 pms0 wskbd0 wsmouse0 pchb0 i915drmkms0 wm0 ehci0 hdaudio0 ppb0 ppb1 ppb2 ppb3 ehci1 ichlpcib0 ahcisata0 ichsmb0 intelfb0 wsdisplay0 ihphy0 usb0 uhub1 uhub2 ubt0 uvideo0 bthub0 video0 hdafg0 hdafg1 audio0 spkr1 pci1 pci2 iwn0 pci3 pci4 sdhc0 sdmmc0 usb1 uhub0 uhub3 umodem0 umodem1 umodem2 umodem3 ucom0 ucom1 ucom2 ucom3 tco0 isa0 tpm0 atabus0 atabus1 atabus2 atabus3 wd0 atapibus0 cd0 iic0 # Hotplug of a USB ethernet adapter device-attach cdce0 device-detach cdce0 # Or a USB mouse device-attach uhidev0 device-attach ums0 device-attach wsmouse1 device-detach wsmouse1 device-detach ums0 device-detach uhidev0 -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
daily CVS update output
Updating src tree: P src/bin/ps/print.c P src/common/lib/libc/misc/ubsan.c P src/common/lib/libutil/snprintb.c P src/doc/3RDPARTY P src/doc/roadmaps/verification P src/doc/roadmaps/virtualization P src/external/bsd/nvi/dist/docs/vitut/vi.in P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vfsops.c P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vnops.c P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_znode.c P src/external/cddl/osnet/sys/sys/zfs_context.h P src/external/gpl3/gdb/dist/gdb/ppc-nbsd-nat.c P src/external/gpl3/gdb/dist/gdb/sh-nbsd-tdep.c P src/share/misc/acronyms.comp P src/share/misc/bsd-family-tree P src/sys/Makefile P src/sys/arch/amd64/conf/GENERIC P src/sys/arch/amd64/conf/MODULAR P src/sys/arch/arm/cortex/gicv3.c P src/sys/arch/arm/cortex/gicv3.h P src/sys/arch/arm/include/ptrace.h P src/sys/arch/arm/sunxi/sunxi_platform.c P src/sys/arch/i386/conf/GENERIC P src/sys/arch/i386/include/ptrace.h P src/sys/arch/ia64/include/mcontext.h P src/sys/arch/x86/acpi/acpi_wakeup.c P src/sys/arch/x86/pci/msipic.c P src/sys/arch/x86/pci/pci_intr_machdep.c P src/sys/arch/x86/pci/pcib.c P src/sys/arch/x86/x86/idt.c P src/sys/arch/x86/x86/intr.c P src/sys/arch/x86/x86/ioapic.c P src/sys/compat/aoutm68k/aoutm68k_syscall.h P src/sys/compat/aoutm68k/aoutm68k_syscallargs.h P src/sys/compat/aoutm68k/aoutm68k_syscalls.c P src/sys/compat/aoutm68k/aoutm68k_sysent.c P src/sys/compat/aoutm68k/syscalls.master P src/sys/compat/common/vfs_syscalls_50.c P src/sys/compat/freebsd/freebsd_syscall.h P src/sys/compat/freebsd/freebsd_syscallargs.h P src/sys/compat/freebsd/freebsd_syscalls.c P src/sys/compat/freebsd/freebsd_sysent.c P src/sys/compat/freebsd/syscalls.master P src/sys/compat/netbsd32/files.netbsd32 P src/sys/compat/netbsd32/netbsd32_compat_50.c P src/sys/compat/netbsd32/netbsd32_syscall.h P src/sys/compat/netbsd32/netbsd32_syscallargs.h P src/sys/compat/netbsd32/netbsd32_syscalls.c P src/sys/compat/netbsd32/netbsd32_syscalls_autoload.c P src/sys/compat/netbsd32/netbsd32_sysent.c P src/sys/compat/netbsd32/netbsd32_systrace_args.c P src/sys/compat/netbsd32/syscalls.master P src/sys/conf/filesystems.config P src/sys/kern/vfs_trans.c P src/sys/modules/compat_50/Makefile P src/sys/modules/compat_aoutm68k/Makefile P src/sys/modules/compat_freebsd/Makefile P src/sys/modules/compat_netbsd32/Makefile P src/sys/modules/ffs/Makefile P src/sys/ufs/files.ufs P src/sys/ufs/chfs/chfs_malloc.c P src/sys/ufs/chfs/chfs_pool.c P src/sys/ufs/chfs/chfs_scan.c P src/sys/ufs/chfs/chfs_vnops.c P src/usr.sbin/sysinst/Makefile.inc P src/usr.sbin/sysinst/partman.c P src/usr.sbin/sysinst/arch/i386/md.c P src/usr.sbin/sysinst/arch/landisk/md.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43641804 Jun 18 03:04 ls-lRA.gz
Re: usb device modifying state of another driver on plug/unplug event
On Mon, Jun 17, 2019 at 10:32:00AM +1000, matthew green wrote: > > By accident I stumbled on FreeBSD's devd(8) that does just this, they > > even had an example of disabling a synaptics touchpad when a usb mouse > > is plugged in. Now all we need is this facility in NetBSD > > devpubd(8)? > "Needs Work(tm)" ... at the moment it looks very disk device focuessed: # drvctl -l root mainbus0 root dk0 root dk1 root dk2 root dk3 root dk4 root dk5 root dk6 root dk7 root dk8 root dk9 root dk10 root dk11 root swcrypto0 root cgd0 root vnd0 Not to say we cannot extend it to be more generic... -- Brett Lymn -- Sent from my NetBSD device. "We are were wolves", "You mean werewolves?", "No we were wolves, now we are something else entirely", "Oh"
Automated report: NetBSD-current/i386 build success
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2019.06.17.17.01.50 sevan src/sys/Makefile,v 1.84 2019.06.17.17.03.58 christos src/common/lib/libutil/snprintb.c,v 1.21 2019.06.17.17.06.39 christos src/sys/conf/filesystems.config,v 1.13 2019.06.17.17.14.56 ryoon src/sys/ufs/chfs/chfs_malloc.c,v 1.6 2019.06.17.17.14.56 ryoon src/sys/ufs/chfs/chfs_pool.c,v 1.4 2019.06.17.17.14.56 ryoon src/sys/ufs/chfs/chfs_scan.c,v 1.8 2019.06.17.17.14.56 ryoon src/sys/ufs/chfs/chfs_vnops.c,v 1.34 2019.06.17.17.45.18 kamil src/doc/roadmaps/verification,v 1.2 2019.06.17.17.53.22 kamil src/sys/arch/arm/include/ptrace.h,v 1.13 2019.06.17.17.53.41 martin src/usr.sbin/sysinst/partman.c,v 1.33 Log files can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2019.06.html#2019.06.17.17.53.41
Re: Weirdness on (pinebook?) X in -current
On Sat 15 Jun 2019 at 07:29:02 +1000, matthew green wrote: > i don't know about the remapping issue, but.. > > > Similarly, the Emulate3Buttons option doesn't seem to work on the mouse. > > It is really needed since the pinebook touchpad doesn't have a middle > > button and it is required for pasting. > > > > Option "Emulate3Buttons" "On > > > > The setting is recognized and reported in /var/log/Xorg.0.log. > > > > Same question: pinebook specific, or generic X issue? > > this one appears to be a timing issue. i've a handful of times > managed to make double-click do middle-button, but it's only > been a handful of times out of hundreds. I tried increasing the "Emulate3Timeout" time to 500 (ms) and it didn't help at all. With an external USB mouse, pressing left + right worked fine to emulate the middle button. I am starting to suspect that the trackpad simply does not report multiple button presses. While running xev, I could not even see anything happening if I pressed a second button while another was already pressed, no matter if I did anthing slow or fast. > .mrg. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- "What good is a Ring of Power \X/ rhialto/at/falu.nl -- if you're unable...to Speak." - Agent Elrond signature.asc Description: PGP signature
Re: Automated report: NetBSD-current/i386 build failure
Hmmm... With sources from 2019-06-17 at 17:43:48 UTC I have just completed a amd64 'build.sh release' successfully. Does i386 include the chfs file system, but not include flash(4) device? On Mon, 17 Jun 2019, Andreas Gustafsson wrote: The build is still failing as of source date 2019.06.17.16.34.02: -- kern-INSTALL --- /tmp/bracket/build/2019.06.17.16.34.02-i386/tools/bin/i486--netbsdelf-ld: chfs_vfsops.o: in function `chfs_mountfs': chfs_vfsops.c:(.text+0xaef): undefined reference to `flash_cdevsw' -- Andreas Gustafsson, g...@gson.org !DSPAM:5d07dfe481556811919384! ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Automated report: NetBSD-current/i386 build failure
Not any more, I just finished one. On Mon, 17 Jun 2019 at 19:45, Andreas Gustafsson wrote: > > The build is still failing as of source date 2019.06.17.16.34.02: > > -- kern-INSTALL --- > /tmp/bracket/build/2019.06.17.16.34.02-i386/tools/bin/i486--netbsdelf-ld: > chfs_vfsops.o: in function `chfs_mountfs': > chfs_vfsops.c:(.text+0xaef): undefined reference to `flash_cdevsw' > > -- > Andreas Gustafsson, g...@gson.org --
Re: Automated report: NetBSD-current/i386 build failure
The build is still failing as of source date 2019.06.17.16.34.02: -- kern-INSTALL --- /tmp/bracket/build/2019.06.17.16.34.02-i386/tools/bin/i486--netbsdelf-ld: chfs_vfsops.o: in function `chfs_mountfs': chfs_vfsops.c:(.text+0xaef): undefined reference to `flash_cdevsw' -- Andreas Gustafsson, g...@gson.org
Automated report: NetBSD-current/i386 build failure
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.06.17.05.45.46. An extract from the build.sh output follows: ebh.c:(.text+0x2465): undefined reference to `flash_erase' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.c:(.text+0x24b8): undefined reference to `flash_block_markbad' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.o: in function `nand_process_eb': ebh.c:(.text+0x31bf): undefined reference to `flash_block_isbad' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.o: in function `ebh_open': ebh.c:(.text+0x3a95): undefined reference to `flash_get_device' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.c:(.text+0x3aac): undefined reference to `flash_get_interface' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.c:(.text+0x3ac3): undefined reference to `flash_get_size' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.o: in function `ebh_read_leb': ebh.c:(.text+0x40e4): undefined reference to `flash_read' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.o: in function `ebh_write_leb': ebh.c:(.text+0x42e7): undefined reference to `flash_write' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.c:(.text+0x446e): undefined reference to `flash_write' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: ebh.o: in function `ebh_change_leb': ebh.c:(.text+0x48f8): undefined reference to `flash_write' /tmp/bracket/build/2019.06.17.05.45.46-i386/tools/bin/i486--netbsdelf-ld: chfs_vfsops.o: in function `chfs_mountfs': chfs_vfsops.c:(.text+0xaef): undefined reference to `flash_cdevsw' --- kern-LEGACY --- sd/drm2/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/include/drm -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/common/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/include/drm -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/uapi -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist -D__KERNEL__ -DCONFIG_BACKLIGHT_CLASS_DEVICE=0 -DCONFIG_BACKLIGHT_CLASS_DEVICE_MODULE=0 -DCONFIG_DRM_FBDEV_EMULATION=1 -DCONFIG_FB=0 -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/../common/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/libnv/dist -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/i915drm -I/tmp/bracket/build/2019.06.17.05.4 5.46-i386/src/sys/external/bsd/drm2/dist/drm/i915 -DCONFIG_DRM_I915_FBDEV=1 -DCONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT=0 -DCONFIG_DRM_FBDEV_EMULATION=1 -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/include/radeon -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/radeon -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/amd/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/radeon -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/nouveau -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/include -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/include/nvkm -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/nvkm -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/drm2/nouveau -DCONFIG_NOUVEAU_DEBUG=5 -DCONFIG_NOUV EAU_DEBUG_DEFAULT=3 -I/tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/external/bsd/acpica/dist/include -c /tmp/bracket/build/2019.06.17.05.45.46-i386/src/sys/dev/pci/mpt_pci.c -o mpt_pci.o --- kern-INSTALL --- *** [netbsd] Error code 1 nbmake[2]: stopped in /tmp/bracket/build/2019.06.17.05.45.46-i386/obj/sys/arch/i386/compile/INSTALL 1 error The following commits were made between the last successful build and the failed build: 2019.06.17.03.31.57 christos src/sys/arch/amd64/conf/MODULAR,v 1.12 2019.06.17.03.32.14 christos src/sys/modules/ffs/Makefile,v 1.11 2019.06.17.03.32.58 christos src/sys/ufs/files.ufs,v 1.45 2019.06.17.03.34.01 christos src/sys/conf/filesystems.config,v 1.12 2019.06.17.05.27.01 mrg src/sys/arch/arm/sunxi/sunxi_platform.c,v 1.37 2019.06.17.05.45.46 msaitoh src/sys/arch/x86/pci/msipic.c,v 1.14 Log files can be found at:
