The following changes since commit 1652a83fa494b12e20fc02a2cc3ddbcd75d53170:
Merge 4.19-rc4 into usb-next (2018-09-16 22:44:14 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git/
tags/usb-ci-v4.20-rc1
for you to fetch changes up
Hi,
I'm the author of a userspace library that makes use of the usbfs
zerocopy-feature via libusb-1.0, and recently received a bug report that
garbage data is received with bulk transfers on ARM-based systems.
When I debugged the issue, I found out that the Kernel maps seemingly
random memory to
On Sun, 7 Oct 2018, Klaus Kusche wrote:
> Hello,
>
> On 03/10/2018 16:02, Alan Stern wrote:
> > Well, what happens if you add only US_FL_BROKEN_FUA without
> > US_FL_IGNORE_UAS? Does it work?
>
> Tried all four combinations with gentoo 4.18.12.
> Just US_FL_IGNORE_UAS fails with the error
Hello,
On 03/10/2018 16:02, Alan Stern wrote:
Well, what happens if you add only US_FL_BROKEN_FUA without
US_FL_IGNORE_UAS? Does it work?
Tried all four combinations with gentoo 4.18.12.
Just US_FL_IGNORE_UAS fails with the error message in the original bug report.
The other three
On Fri, 5 Oct 2018, Christoph Groth wrote:
> Dear Linux USB experts,
>
> I noticed that a device (Garmin Foretrex 601, firmware version 2.80)
> that is supposed to present itself as USB mass storage, does not work on
> Linux. After being connected, the device does show up in the output of
>
