Re: wsmouse(4): multi-touch buttons again

2023-06-27 Thread Jason McIntyre
On Wed, Jun 28, 2023 at 12:03:41AM +0200, Ulf Brosziewski wrote: > This version of the diff adds a wsconsctl field, named "mouse.tp. > mtbuttons", and an update to the wsmouse.4 page. Apart from that, it > contains only stylistic changes. > > The new wsconsctl field is just a boolean, I don't thi

mg.1: add no-tab-mode to set-default-mode description

2023-06-27 Thread Simon Branch
Hello! I've been enjoying the resurrection of no-tab-mode in mg(1). It is simple to enable by default: set-default-mode notab The manual page says that "built in modes include fill, indent and overwrite". This patch makes the list more complete by adding notab, and adds "can be set globally

Re: wsmouse(4): multi-touch buttons again

2023-06-27 Thread Ulf Brosziewski
This version of the diff adds a wsconsctl field, named "mouse.tp. mtbuttons", and an update to the wsmouse.4 page. Apart from that, it contains only stylistic changes. The new wsconsctl field is just a boolean, I don't think that it would make sense to include the distance filter in the configura

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Mark Kettenis
> Date: Tue, 27 Jun 2023 17:52:44 +0200 > From: Alexander Bluhm > > On Tue, Jun 27, 2023 at 01:55:23PM +0200, Mark Kettenis wrote: > > > Date: Tue, 27 Jun 2023 11:09:32 + > > > From: Klemens Nanni > > > > > > On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > > > > M_TEMP s

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Alexander Bluhm
On Tue, Jun 27, 2023 at 01:55:23PM +0200, Mark Kettenis wrote: > > Date: Tue, 27 Jun 2023 11:09:32 + > > From: Klemens Nanni > > > > On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > > > M_TEMP seems unreasonable for interface groups data allocations. > > > > After claudio

Re: btrace(8) allow to store kstack in a map

2023-06-27 Thread Klemens Nanni
On Tue, Jun 27, 2023 at 03:27:55PM +0200, Claudio Jeker wrote: > On Mon, Jun 26, 2023 at 08:58:47PM +, Klemens Nanni wrote: > > On Mon, Jun 26, 2023 at 10:52:20PM +0200, Claudio Jeker wrote: > > > count() is strange since it only works on maps (at least from what I > > > figured out). I need to

Re: btrace(8) allow to store kstack in a map

2023-06-27 Thread Claudio Jeker
On Mon, Jun 26, 2023 at 08:58:47PM +, Klemens Nanni wrote: > On Mon, Jun 26, 2023 at 10:52:20PM +0200, Claudio Jeker wrote: > > count() is strange since it only works on maps (at least from what I > > figured out). I need to double check how min() and max() work. Since the > > usage also seems

Re: Add Intel Wi-Fi 6 AX211 0x51f1 device

2023-06-27 Thread Reyk Floeter
On Tue, Jun 27, 2023 at 11:55:15AM +0200, Stefan Sperling wrote: > On Tue, Jun 27, 2023 at 10:55:04AM +0200, Reyk Floeter wrote: > > Hi, > > > > the following diff adds the Intel Wi-Fi 6 0x51f1 device, found in a > > new Thinkpad X1 Carbon Gen 11. > > > > iwx0 at pci0 dev 20 function 3 "Intel Wi-

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Claudio Jeker
On Tue, Jun 27, 2023 at 11:09:32AM +, Klemens Nanni wrote: > On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > > M_TEMP seems unreasonable for interface groups data allocations. > > After claudio pointed out the wrong type, I thought of the same name, > no other malloc(9) ty

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Mark Kettenis
> Date: Tue, 27 Jun 2023 11:09:32 + > From: Klemens Nanni > > On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > > M_TEMP seems unreasonable for interface groups data allocations. > > After claudio pointed out the wrong type, I thought of the same name, > no other malloc(9)

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Vitaliy Makkoveev
On Tue, Jun 27, 2023 at 11:09:32AM +, Klemens Nanni wrote: > On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > > M_TEMP seems unreasonable for interface groups data allocations. > > After claudio pointed out the wrong type, I thought of the same name, > no other malloc(9) ty

Re: Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Klemens Nanni
On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote: > M_TEMP seems unreasonable for interface groups data allocations. After claudio pointed out the wrong type, I thought of the same name, no other malloc(9) type fits. FWIW OK kn, but please wait for other to chime in. > > Don't

Introduce M_IFGROUP type of memory allocation

2023-06-27 Thread Vitaliy Makkoveev
M_TEMP seems unreasonable for interface groups data allocations. Don't forget to recompile systat(1) and vmstat(8) with new sys/malloc.h. Index: sys/net/if.c === RCS file: /cvs/src/sys/net/if.c,v retrieving revision 1.700 diff -u -p

Re: Add Intel Wi-Fi 6 AX211 0x51f1 device

2023-06-27 Thread Stuart Henderson
On 2023/06/27 10:55, Stuart Henderson wrote: > I have this (AP is mikrotik hapax2 > 0x0001, country 'GB ', channel 36 limit 23dB, channel 40 limit > 23dB, channel 44 limit 23dB, channel 48 limit 23dB, channel 52 limit > 23dB, channel 56 limit 23dB, channel 60 limit 23dB, channel 64 limit > 23d

bgpd: rewrite code to send UPDATE messages

2023-06-27 Thread Claudio Jeker
Sorry this diff is a monster but it kind of turned into a all or nothing situation. For a long time bgpd used a static 4k buffer plus a len argument to build updates. The result was ok but was also very fragile. With the new ibuf API all of this can be rewritten and the result is IMO already a lot

Re: Add Intel Wi-Fi 6 AX211 0x51f1 device

2023-06-27 Thread Stuart Henderson
On 2023/06/27 10:55, Reyk Floeter wrote: > This works fine with my 11ac setup and performance seems OK (around > 200Mbps - what can I expect on OpenBSD these days?). I don't know if > the device supports UHB channels. That seems a little on the low side but in the right ballpark, I have this (AP

Re: Add Intel Wi-Fi 6 AX211 0x51f1 device

2023-06-27 Thread Stefan Sperling
On Tue, Jun 27, 2023 at 10:55:04AM +0200, Reyk Floeter wrote: > Hi, > > the following diff adds the Intel Wi-Fi 6 0x51f1 device, found in a > new Thinkpad X1 Carbon Gen 11. > > iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX211" rev 0x01, msix > iwx0: hw rev 0x370, fw 77.f92b5fed.0, pnvm e4a4953

Add Intel Wi-Fi 6 AX211 0x51f1 device

2023-06-27 Thread Reyk Floeter
Hi, the following diff adds the Intel Wi-Fi 6 0x51f1 device, found in a new Thinkpad X1 Carbon Gen 11. iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX211" rev 0x01, msix iwx0: hw rev 0x370, fw 77.f92b5fed.0, pnvm e4a49534, address ... I looked at the Linux code for the values for 0x51f1 and 0x7