Re: ttycreate from FreeBSD equivalent

2023-02-27 Thread jon
Ok well I have been using puc_cardbus as a starting point and in fact in the beginning I was hoping to just the interrupt handler and so on to it, but I belive com(4) cannot be used for the serial ports this card presents. I'm confused as to how things interact with the device tree: I see for

[Diff] Keyboard backlight support for late powerbooks, plus keybindings

2023-02-27 Thread jon
Hello. Following up on my previous post https://marc.info/?l=openbsd-ppc=166150553627054=2 I actually implemented support for fn-keys controls of the keyboard backlight as outlined there, seems to work fairly ok, would appreciate any feedback Index: arch/macppc/dev/adb.c

Re: kernel: don't jump ticks, jiffies during boot

2023-02-27 Thread Scott Cheloha
On Tue, Feb 28, 2023 at 01:01:32PM +1100, Jonathan Gray wrote: > On Mon, Feb 27, 2023 at 06:26:00PM -0600, Scott Cheloha wrote: > > On Tue, Feb 28, 2023 at 10:18:16AM +1100, Jonathan Gray wrote: > > > On Mon, Feb 27, 2023 at 04:57:04PM -0600, Scott Cheloha wrote: > > > > ticks and jiffies start at

Re: kernel: don't jump ticks, jiffies during boot

2023-02-27 Thread Jonathan Gray
On Mon, Feb 27, 2023 at 06:26:00PM -0600, Scott Cheloha wrote: > On Tue, Feb 28, 2023 at 10:18:16AM +1100, Jonathan Gray wrote: > > On Mon, Feb 27, 2023 at 04:57:04PM -0600, Scott Cheloha wrote: > > > ticks and jiffies start at zero. During boot in initclocks(), we > > > reset them: > > > > > >

Re: kernel: don't jump ticks, jiffies during boot

2023-02-27 Thread Scott Cheloha
On Tue, Feb 28, 2023 at 10:18:16AM +1100, Jonathan Gray wrote: > On Mon, Feb 27, 2023 at 04:57:04PM -0600, Scott Cheloha wrote: > > ticks and jiffies start at zero. During boot in initclocks(), we > > reset them: > > > > /* sys/kern/kern_clock.c */ > > > > 89 int ticks; > >

Re: kernel: don't jump ticks, jiffies during boot

2023-02-27 Thread Jonathan Gray
On Mon, Feb 27, 2023 at 04:57:04PM -0600, Scott Cheloha wrote: > ticks and jiffies start at zero. During boot in initclocks(), we > reset them: > > /* sys/kern/kern_clock.c */ > > 89int ticks; > 90static int psdiv, pscnt;/* prof => stat divider

kernel: don't jump ticks, jiffies during boot

2023-02-27 Thread Scott Cheloha
ticks and jiffies start at zero. During boot in initclocks(), we reset them: /* sys/kern/kern_clock.c */ 89 int ticks; 90 static int psdiv, pscnt;/* prof => stat divider */ 91 int psratio;/* ratio: prof / stat */ 92

update: xf86-video-amdgpu 23.0.0

2023-02-27 Thread Matthieu Herrb
Hi, the patch below update the amdgpu(4) X.Org driver to version 23.0.0 To test (on machines with an AMD / Radeon GPU) # cd /usr/xenocara/driver/xf86-video-amdgpu # patch -p0 -E < /path/to/this/file # make -f Makefile.bsd-wrapper obj # make -f Makefile.bsd-wrapper build and restart xenodm(1)

Re: running UDP input in parallel

2023-02-27 Thread Hrvoje Popovski
On 22.8.2022. 15:07, Alexander Bluhm wrote: > On Sun, Aug 21, 2022 at 07:07:29PM +0200, Alexander Bluhm wrote: >> On Fri, Aug 19, 2022 at 10:54:42PM +0200, Alexander Bluhm wrote: >>> This diff allows to run udp_input() in parallel. > > Diff rebased to -current. Hi, is this diff still active? I

Fix sndiod(8) dropping randomly connections

2023-02-27 Thread Alexandre Ratchov
Sometimes sndiod closes the device sponteneously and, unless -F is used, programs need to be restarted. If -F is used, sndiod will switch to another device (ex. from usb headphones to internal speakers), which might be a privacy problem. The cause is that libsndio uses the kernel underrun

Re: freeradius denies to authentocate with eap-tls

2023-02-27 Thread Stuart Henderson
(moving to ports#, reply-to is set, although this is unlikely to be OpenBSD-specific) On 2023/02/25 02:18, Mikhael Lialin wrote: > Trying to setup witi with radius eap-tls authentication. > > And getting time out while authenticated. > > Tried with custome setup, and default setup with

nd6_resolve: sync some bits with arpresolve

2023-02-27 Thread Klemens Nanni
Three things to make comparison easier: - hoist duplicate addr[] declaration - defer failure into `bad' label These seem sensible on their own. - set/use getuptime() identically This is purely for sync; nd6_resolve() uses getuptime() just once, while arpresolve() has multiple `uptime' usages.