Re: EVFILT_USER?

2019-02-17 Thread coypu
On Mon, Feb 18, 2019 at 01:03:03AM +0100, Christoph Badura wrote: > On Sun, Feb 17, 2019 at 01:48:52PM -0800, Jason Thorpe wrote: > > > On Feb 17, 2019, at 1:32 PM, co...@sdf.org wrote: > > > the linux equivalent code seems to be using futex_wait/wake. > > > > I’m working on integrating a new Linu

Re: EVFILT_USER?

2019-02-17 Thread Jason Thorpe
> On Feb 17, 2019, at 3:33 PM, Kamil Rytarowski wrote: > > 1. POSIX robus pthread(3) mutexes > 2. pshared support in pthread(3) Yes. I may or may not be able to look at that in the near future… my first priority will be to convert POSIX semaphores to use futexes. Futexes have the potentia

Re: EVFILT_USER?

2019-02-17 Thread Jason Thorpe
> On Feb 17, 2019, at 4:03 PM, Christoph Badura wrote: > > On Sun, Feb 17, 2019 at 01:48:52PM -0800, Jason Thorpe wrote: >>> On Feb 17, 2019, at 1:32 PM, co...@sdf.org wrote: >>> the linux equivalent code seems to be using futex_wait/wake. >> >> I’m working on integrating a new Linux-compatib

Re: EVFILT_USER?

2019-02-17 Thread Christoph Badura
On Sun, Feb 17, 2019 at 01:48:52PM -0800, Jason Thorpe wrote: > > On Feb 17, 2019, at 1:32 PM, co...@sdf.org wrote: > > the linux equivalent code seems to be using futex_wait/wake. > > I’m working on integrating a new Linux-compatible futex > implementation written by Taylor (that led me down the

Re: EVFILT_USER?

2019-02-17 Thread Kamil Rytarowski
On 17.02.2019 22:48, Jason Thorpe wrote: > > >> On Feb 17, 2019, at 1:32 PM, co...@sdf.org wrote: >> >> the linux equivalent code seems to be using futex_wait/wake. > > I’m working on integrating a new Linux-compatible futex implementation > written by Taylor (that led me down the rabbit hole o

Re: Reserve device major numbers for pkgsrc

2019-02-17 Thread David Holland
On Sat, Feb 16, 2019 at 09:02:05PM -0800, John Nemeth wrote: > Of course, the real ideal thing would be to get a devfs and > get rid of the concept of major numbers. Here I go again, starting > contriversies. :-> A more viable approach: use strings instead of major numbers. Even in ufs1

Re: EVFILT_USER?

2019-02-17 Thread Jason Thorpe
> On Feb 17, 2019, at 1:32 PM, co...@sdf.org wrote: > > the linux equivalent code seems to be using futex_wait/wake. I’m working on integrating a new Linux-compatible futex implementation written by Taylor (that led me down the rabbit hole of needing to fix issues with fetch(9) / store(9) fi

EVFILT_USER?

2019-02-17 Thread coypu
Hi folks, Do we have anything that resembles EVFILT_USER? Apparently, it makes it possible for userland to send events around. This came up in a programming language port. https://github.com/ziglang/zig/blob/master/std/event/loop.zig I assume (based on a superficial reading) that I would like to

Re: Reserve device major numbers for pkgsrc

2019-02-17 Thread Christoph Badura
On Sat, Feb 16, 2019 at 09:02:05PM -0800, John Nemeth wrote: > On Feb 16, 11:25pm, Kamil Rytarowski wrote: > } Where and how to reserve these major numbers? > > The ideal thing is to not reserve numbers at all and have them > allocated dynamically. This requires the module reporting the > nu

Re: Reserve device major numbers for pkgsrc

2019-02-17 Thread Mouse
> Of course, the real ideal thing would be to get a devfs and get rid > of the concept of major numbers. For many purposes. But, if it's not possible to hand-build a /dev with only a few entries, that will cripple usefulness a number of possible locked-down uses, from chroot() to unusual setups l

Re: atf for atomic_ops(3)

2019-02-17 Thread Martin Husemann
On Sun, Feb 17, 2019 at 06:45:31PM +0900, Tetsuya Isaki wrote: > Well then, I add atomic_ops part this time. And I will > prepare sync_* tests and add them in tests/lib/libc/atomic > (in order to replace tests/lib/libc/sync). Thanks a lot! Martin

Re: atf for atomic_ops(3)

2019-02-17 Thread Tetsuya Isaki
At Sun, 17 Feb 2019 08:48:01 +0100, Martin Husemann wrote: > > I wrote atf tests for atomic_ops(3). > > These does not test the atomicity but can find a easy bug. > > Is this ok to commit? > > (I know there is a similar path tests/lib/libc/sync but > > I think it's better to not merge) > > Why not

DisplayLink

2019-02-17 Thread BERTRAND Joël
Hello, I'm trying to connect a DisplayLink device to NetBSD 8. This product returns : port 3 addr 1: full speed, power 500 mA, config 1, USB Audio(0x8915), vendor 10ae(0x10ae), rev 1.00(0x0100) port 1 addr 3: high speed, self powered, config 1, AB105 5inch(0x01c4), DisplayLink(0