Diff for evaluation (WACOM tablet)

Good day, I am currently trying to work on an implementationion of a driver for the WACOM tablet on openBSD I am therefore submiting this diff so that it could potentially be evaluated. Please if you have a moment, could you have a look at this diff? I have tested it with my Wacom tablet and it

Re: ix(4): allocate less memory for tx buffers

On Fri, Jun 09, 2023 at 06:59:57PM +0200, Jan Klemkow wrote: > On Fri, Jun 09, 2023 at 06:11:38PM +0200, Jan Klemkow wrote: > > TSO packets are limited to MAXMCLBYTES (64k). Thus, we don't need to > > allocate IXGBE_TSO_SIZE (256k) per packet for the transmit buffers. > > > > This saves 3/4 of

Re: ix(4): allocate less memory for tx buffers

On Fri, Jun 09, 2023 at 06:11:38PM +0200, Jan Klemkow wrote: > TSO packets are limited to MAXMCLBYTES (64k). Thus, we don't need to > allocate IXGBE_TSO_SIZE (256k) per packet for the transmit buffers. > > This saves 3/4 of the memory and allows me to pack over 8 ix(8) ports > into one machine.

Re: acme-client(8): preliminary support for HiCA

On Fri, 2023-06-09 at 07:25 +0200, Florian Obser wrote: > > OK? > > p.s. I'm currently busy writing an ISC licensed bash in rust to > safely > support HiCA. So this might take a while... > The HiCA project has been shut down due to some security issues.

ix(4): allocate less memory for tx buffers

Hi, TSO packets are limited to MAXMCLBYTES (64k). Thus, we don't need to allocate IXGBE_TSO_SIZE (256k) per packet for the transmit buffers. This saves 3/4 of the memory and allows me to pack over 8 ix(8) ports into one machine. Otherwise I run out of devbuf in malloc(9). ok? bye, Jan

Re: vmd issue with network+derived qcow2 on current

On Fri, 2023-06-09 at 11:25 -0400, Dave Voutila wrote: > > Thanks. This feels like bad fd accounting during the fork/exec dance. > > Sounds like the switch definition and usage isn't required for > reproducing? indeed, you don't need it, a local interface is enough

Re: vmd issue with network+derived qcow2 on current

Solène Rapenne writes: > I'm currently playing with derived qcow2 disks using vmd. While my > setup was working on 7.3 (maybe there is an issue with MAC assignments > in VMs) so I updated to current, but now VMs don't start at all when > they are using a derived qcow2 disk + network interface

Re: acme-client(8): preliminary support for HiCA

Todd C. Miller wrote: > On Fri, 09 Jun 2023 07:25:04 +0200, Florian Obser wrote: > > > OK? > > > > p.s. I'm currently busy writing an ISC licensed bash in rust to safely > > support HiCA. So this might take a while... > > Have you considered implementing wordexp(3) to allow command >

Re: acme-client(8): preliminary support for HiCA

On Fri, 09 Jun 2023 07:25:04 +0200, Florian Obser wrote: > OK? > > p.s. I'm currently busy writing an ISC licensed bash in rust to safely > support HiCA. So this might take a while... Have you considered implementing wordexp(3) to allow command substitution? It may be necessary to add inline

vmd issue with network+derived qcow2 on current

I'm currently playing with derived qcow2 disks using vmd. While my setup was working on 7.3 (maybe there is an issue with MAC assignments in VMs) so I updated to current, but now VMs don't start at all when they are using a derived qcow2 disk + network interface This setup works: