On Freitag, 11. September 2015 10:23:45 Alan Stern wrote:
> On Fri, 11 Sep 2015, Hans-Peter Jansen wrote:
> >
> > I still have trouble with storage devices on xhci ports, that disappear as
> > soon as I change to an ehci port.
> >
> > My current kernel version is 4.1.6.
> > Device is a Transcend
On Samstag, 20. Juni 2015 11:48:15 Stéphane Lavergne wrote:
> Hans-Peter Jansen writes:
> > just a heads up: retesting with 4.0.4 revealed, that this issue isn't
>
> fixed
>
> Thanks for the heads up; I'll stop trying to figure out the "clean" way to
> upgrade my Debian box that far ahead of the
The I2C core always reports the MODALIAS uevent as "i2c:
---
Hello,
This is another resend of this patch. The first post was on July 30 [0]
as a part of a set and then the patch was resent again on August 25 [1].
It is a really trivial patch that fixes a bug (module auto loading not
working) so
Hi Alan,
I'm sending a "Reply to all" on this mail. Should I continue to keep
Mathias and Bjorn on copy and cross-posting to linux-pci@ (I'm not
yet subscribed there, so that post probably won't get through anyway)?
> [Roland, what happens if you try unbinding xhci-hcd before ehci-hcd?
> Note t
>> Should these files be consolidated? And if so how?
> if you can find an easy way, that would be a very, very welcome patch.
Is the ideal solution to consolidate both fusbh200-hcd.c and
fotg210-hcd.c in a single module? If this is the case, how to detect
at run time which version of the hw is pr
Hi Alan,
> was added recently; a table of devices that ehci-pci should ignore. If
> you add your device to that list, ehci-pci won't bind to it. See
> bypass_pci_id_table in drivers/usb/host/ehci-pci.c. Of course, that
> also will involve rebuilding part of the kernel...
Yes, that works! Wi
David Ward writes:
> An earlier e-mail from Reinhard contained a patch that did this for the
> MC7304. That patch could be modified as shown below so that the control
> request is enabled or disabled from qcprobe() instead. This way, it is
> straightforward to enable it for specific interface(s)
On Sat, 12 Sep 2015, Roland Weber wrote:
> Hi Alan,
>
> I'm sending a "Reply to all" on this mail. Should I continue to keep
> Mathias and Bjorn on copy and cross-posting to linux-pci@ (I'm not
> yet subscribed there, so that post probably won't get through anyway)?
Most kernel lists don't requi
On Sat, 12 Sep 2015, Roland Weber wrote:
> Hi Alan,
>
> > was added recently; a table of devices that ehci-pci should ignore. If
> > you add your device to that list, ehci-pci won't bind to it. See
> > bypass_pci_id_table in drivers/usb/host/ehci-pci.c. Of course, that
> > also will involve
On Sat, 12 Sep 2015, Hans-Peter Jansen wrote:
> On Freitag, 11. September 2015 10:23:45 Alan Stern wrote:
> > On Fri, 11 Sep 2015, Hans-Peter Jansen wrote:
> > >
> > > I still have trouble with storage devices on xhci ports, that disappear as
> > > soon as I change to an ehci port.
> > >
> > > M
> +static DEVICE_ATTR_RO(usb3_hardware_lpm);
Is my understanding correct that this sysfs entry is going to be read-only and
there is currently no way to disable hardware LPM manually?
I'm currently experiencing random disconnects of a ASMedia1051-based HDD
enclosure. The issue is most probably
11 matches
Mail list logo
