On Tuesday 18 December 2012 21:32:46 Warner Losh wrote:
On Dec 18, 2012, at 12:44 PM, Hans Petter Selasky wrote:
On Tuesday 18 December 2012 20:12:29 Andrew Turner wrote:
On Tue, 18 Dec 2012 13:06:44 +0100
Hans Petter Selasky hsela...@c2i.net wrote:
Hi Andrew,
The BUS_DMA_COHERENT
Hi again,
Different vendors use different naming conventions about sync operations.
Maybe we should start defining some names and agree about that first?
usb_pc_cpu_flush:
This function is a system abstraction which is supposed to ensure that all CPU
cached data for the given buffer is
Number: 174575
Category: usb
Synopsis: Interrupt storm error on startup
Confidential: no
Severity: non-critical
Priority: low
Responsible:freebsd-usb
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id:
Synopsis: [usb] [libusb] usb_reset() behavior different between GNU/Linux and
FreeBSD
State-Changed-From-To: open-closed
State-Changed-By: eadler
State-Changed-When: Wed Dec 19 16:00:54 UTC 2012
State-Changed-Why:
Per submitter request
http://www.freebsd.org/cgi/query-pr.cgi?pr=173666
On Dec 19, 2012, at 1:56 AM, Hans Petter Selasky wrote:
Hi again,
Different vendors use different naming conventions about sync operations.
The different names are often for subtly different types of cache flushing.
Maybe we should start defining some names and agree about that first?
BTW:
This commit looks exactly like my X-mas present :-)
http://svnweb.freebsd.org/changeset/base/244471
--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to
On Wednesday 19 December 2012 20:12:55 Warner Losh wrote:
On Dec 19, 2012, at 1:56 AM, Hans Petter Selasky wrote:
Hi again,
Different vendors use different naming conventions about sync operations.
The different names are often for subtly different types of cache flushing.
Maybe we
