On Sun, Aug 30, 2015 at 12:32:24PM +0200, Martin Pieuchot stated:
> That's good but the original design of allocating an xfer for every
> usbd_transfer(9) call does not make much sense.
>
> You could allocate two xfers (one for read and one for write) at the
> same time the pipes are opened and
fixes panic on attach/detach due to free list corruption, also use
after usbd_free_xfer(), tested on i386
~~~
Index: uow.c
===
RCS file: /cvs/src/sys/dev/usb/uow.c,v
retrieving revision 1.33
diff -u -p -s -r1.33 uow.c
--- uow.c
- just use a buffer and make onewire_crc16() operate like onewire_crc()
- some style cleanups
- build for i386 GENERIC (only arch tested)
Index: onewire_subr.c
===
RCS file: /cvs/src/sys/dev/onewire/onewire_subr.c,v
retrieving revisi
This changes the dmesg on one acpi enabled machine:
acpiprt3 at acpi0: bus -1 (MPCI)
-acpicpu0 at acpi0acpicpu0: struck PSS entry, core frequency equals last
-acpicpu0: struck PSS entry, core frequency equals last
+acpicpu0 at acpi0
+acpicpu0: struck PSS entry, core frequency equals last
+acpic