On Sat, Jun 30, 2018 at 08:43:18PM +0200, Mark Kettenis wrote:
> The pointer to the DSDT may be 64-bit as well. In that case the
> 32-bit field will be zero and we have to use the 64-bit field.
>
> ok?
>
>
> Index: acpidump.c
> ===
> Note that your diff doesn't apply. You have tab vs spaces issues.
Sorry about that, it seems like I need to setup a proper mail-client.
> I don't understand what you're talking about. Can you give example of
> the 3 scenarios you're talking about.
If you look inside /usr/share/misc/usb_hid_usa
The pointer to the DSDT may be 64-bit as well. In that case the
32-bit field will be zero and we have to use the 64-bit field.
ok?
Index: acpidump.c
===
RCS file: /cvs/src/usr.sbin/acpidump/acpidump.c,v
retrieving revision 1.18
dif
Hi, I bought a LG AN-WF500 wifi adapter and I'm trying to use it on
OpenBSD with the driver bwfm. The driver supports the chipset BCM43242
but doesn't have the IDs for the adapter.
I tried to add the IDs to the driver (patch at the end of the mail) but
the kernel detects three devices and panics w
I recently committed a piece of BER code synchronizing in the wrong direction
(i.e. from the ldap instances to the snmpd instance). sthen@ noticed a break
in SNMPv3 authentication and reverted that part of the change. Thanks Stuart!
I just fixed some typos in the snmpd regression test which preven
On Sat, Jun 30, 2018 at 02:41:02PM +0200, Mark Kettenis wrote:
> Diff below adds support for the com(4) driver to attach to acpi(4).
> This is needed to support serial console on arm64 ACPI machines. This
> diff is fairly complete. It looks at the SPCR table if present to
> determine if the seria
Diff below adds support for the com(4) driver to attach to acpi(4).
This is needed to support serial console on arm64 ACPI machines. This
diff is fairly complete. It looks at the SPCR table if present to
determine if the serial port in question is the console. It also uses
"Device Properties" to
