Re: [RFC] acpi: add acpitimer_delay(), acpihpet_delay()

2022-09-07 Thread Pavel Korovin
On 09/07, Scott Cheloha wrote: > Just to make sure that my changes to acpihpet(4) actually caused > the problem, I have a few more questions: > > 1. When did you change the OS type? 03 August, after that, there was a local snpashot built from sources fetched on 17 Aug 2022 22:12:57 +0300 which

Re: [RFC] acpi: add acpitimer_delay(), acpihpet_delay()

2022-09-07 Thread Pavel Korovin
Oh no, sorry, that was too early. Double-checked once again, no, this problem still exists if Guest OS Version is set to "FreeBSD Pre-11 versions (32-bit)". If I set Guest OS Version to "FreeBSD 11 (32-bit)", the problem disappears. On 09/08, Pavel Korovin wrote: > Hi Scott, > > Thank you for

Re: [RFC] acpi: add acpitimer_delay(), acpihpet_delay()

2022-09-07 Thread Scott Cheloha
On Thu, Sep 08, 2022 at 05:01:33AM +0300, Pavel Korovin wrote: > Hi Scott, > > Thank you for the fix! > > I found what triggered this behaviour: it was the change in Guest OS > Version in VM Options. > > I deploy VMs with sysutils/packer, some time ago I noticed that VM type in > my templates

Re: [RFC] acpi: add acpitimer_delay(), acpihpet_delay()

2022-09-07 Thread Pavel Korovin
Hi Scott, Thank you for the fix! I found what triggered this behaviour: it was the change in Guest OS Version in VM Options. I deploy VMs with sysutils/packer, some time ago I noticed that VM type in my templates is specified as freebsd11_64Guest, which isn't consistent with vmt(4), as it

Re: Recognize Realtek ALC245 Audio Codec

2022-09-07 Thread Jonathan Gray
On Wed, Sep 07, 2022 at 03:17:23PM -0700, Neel Chauhan wrote: > Index: dev/pci/azalia_codec.c > === > RCS file: /cvs/src/sys/dev/pci/azalia_codec.c,v > retrieving revision 1.188 > diff -u -p -u -p -r1.188 azalia_codec.c > ---

Re: Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Jonathan Gray
On Wed, Sep 07, 2022 at 05:50:35PM -0700, Neel Chauhan wrote: > On 2022-09-07 17:45, Jonathan Gray wrote: > > so the subclass shows as "Audio" not "HD Audio" > > in pcidump -v? > > > > 7:0:1: ATI Renoir HD Audio > > 0x: Vendor ID: 1002, Product ID: 1637 > > 0x0004: Command:

Re: Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Neel Chauhan
On 2022-09-07 17:45, Jonathan Gray wrote: so the subclass shows as "Audio" not "HD Audio" in pcidump -v? 7:0:1: ATI Renoir HD Audio 0x: Vendor ID: 1002, Product ID: 1637 0x0004: Command: 0006, Status: 0010 0x0008: Class: 04 Multimedia, Subclass: 03 HD Audio,

Re: Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Jonathan Gray
On Wed, Sep 07, 2022 at 05:33:56PM -0700, Neel Chauhan wrote: > I technically own a HP Spectre x360 16-f0013dx which uses the 0x51c8 ID, but > it seems we already included that. > > I based the original patch off my FreeBSD patch which does the same thing > (but includes all the IDs), hence all

Re: Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Neel Chauhan
I technically own a HP Spectre x360 16-f0013dx which uses the 0x51c8 ID, but it seems we already included that. I based the original patch off my FreeBSD patch which does the same thing (but includes all the IDs), hence all the IDs. My Spectre requires the match table, otherwise I'd have no

Re: Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Jonathan Gray
Some of these are Raptor Lake not Alder Lake. Do you have a machine with any of the added ids? The match table is added to when we find machines with an unexpected subclass. On Wed, Sep 07, 2022 at 04:35:32PM -0700, Neel Chauhan wrote: > Index: dev/pci/azalia.c >

Recognize Realtek ALC245 Audio Codec

2022-09-07 Thread Neel Chauhan
Index: dev/pci/azalia_codec.c === RCS file: /cvs/src/sys/dev/pci/azalia_codec.c,v retrieving revision 1.188 diff -u -p -u -p -r1.188 azalia_codec.c --- dev/pci/azalia_codec.c 3 Aug 2022 05:54:50 - 1.188 +++

Fully enable Intel AlderLake HD Audio

2022-09-07 Thread Neel Chauhan
Index: dev/pci/azalia.c === RCS file: /cvs/src/sys/dev/pci/azalia.c,v retrieving revision 1.275 diff -u -p -u -p -r1.275 azalia.c --- dev/pci/azalia.c24 Aug 2022 11:21:12 - 1.275 +++ dev/pci/azalia.c7 Sep 2022

Re: rpki-client http client make header parser more RFC compliant

2022-09-07 Thread Theo Buehler
On Wed, Sep 07, 2022 at 03:56:31PM +0200, Claudio Jeker wrote: > The HTTP RFC defines a header as: > message-header = field-name ":" [ field-value ] >field-name = token >field-value= *( field-content | LWS ) > >The field-content does not include any leading or trailing

ftp follow RFC 9112 more closely

2022-09-07 Thread Claudio Jeker
When parsing header lines ftp (as does rpki-client) is a bit too strict in what it accepts. In short the field values can have leading and trailing whitespace which needs to be ignored. See RFC9112 Section 5. ftp only allows exactly a single leading space which is not in spec. This is a very

Re: ifconfig, wireguard output less verbose, unless -A or

2022-09-07 Thread Stuart Henderson
On 2022/09/07 15:25, Mikolaj Kucharski wrote: > Hi. > > I didn't get a lof of feedback on this on the code level, however > got some intput on manual page changes. At the end of the email is > ifconfig.8 change from jmc@ and ifconfig.c from me. > > > On Sat, Sep 03, 2022 at 04:51:03PM +0100,

Re: ifconfig, wireguard output less verbose, unless -A or

2022-09-07 Thread Mikolaj Kucharski
Hi. I didn't get a lof of feedback on this on the code level, however got some intput on manual page changes. At the end of the email is ifconfig.8 change from jmc@ and ifconfig.c from me. On Sat, Sep 03, 2022 at 04:51:03PM +0100, Jason McIntyre wrote: > On Sat, Sep 03, 2022 at 08:55:51AM

rpki-client http client make header parser more RFC compliant

2022-09-07 Thread Claudio Jeker
The HTTP RFC defines a header as: message-header = field-name ":" [ field-value ] field-name = token field-value= *( field-content | LWS ) The field-content does not include any leading or trailing LWS: linear white space occurring before the first non-whitespace

Re: Rename global ifnet TAILQ

2022-09-07 Thread Alexander Bluhm
On Fri, Aug 26, 2022 at 06:14:44PM +, Klemens Nanni wrote: > Naming the list like the struct itself makes for awful grepping. > Distinguish the list name; no functional change. > > Builds/runs fine on and64 and sparc64. > > Feedback? Objection? OK? > Naming bikeshed (ifnet_tailq,