Separate the ST OHCI SPEAr host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Signed-off-by:
Separate the Samsung OHCI S3C24xx/S3C64xx host controller driver
from ohci-hcd host code so that it can be built as a separate
driver module.This work is part of enabling multi-platform
kernels on ARM;it would be nice to have in 3.12.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Separate the TI OHCI Atmel host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.12.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Signed-off-by:
Hi,
Tejun Heo wrote:
This avoids the described deadlock because iosched module doesn't use
async and thus wouldn't invoke async_synchronize_full(). This is
hacky and incomplete. It will deadlock if async module loading nests;
however, this works around the known problem case and seems to
Hi Peter,
On Mon, Aug 12, 2013 at 09:28:28AM +0800, Peter Chen wrote:
On Sun, Aug 11, 2013 at 01:00:49PM +0200, Luka Perkov wrote:
USB_CHIPIDEA_HOST does not need to depend on USB=y, USB_CHIPIDEA_HOST will
work
just fine even if USB=m is used. The depends line can be safely removed
Hi Paul,
Add the NAK holdoff patch from the downstream Raspberry Pi kernel.
This allows the transfer scheduler to better handle cheeky devices
that just hold off using NAKs.
@@ -365,6 +366,7 @@ struct dwc2_hsotg {
u8 otg_port;
u32 *frame_list;
dma_addr_t frame_list_dma;
Hi Paul Dom,
I haven't got time to look closely right now, but at first glance most
of my comments have been resolved. One thing that is still in there, is
this piece of code for which I'm not sure if it is really related to the
topic of the patch:
@@ -780,6 +784,10 @@ static void
Hi Paul,
Matthijs' concern about periodic endpoints with bInterval=1 seems
to be unfounded. I tried a webcam, which uses a bInterval=1 isoc
endpoint, on my PCI-based dev board, and it still works fine with
this patch applied.
For the record, I still think this concern actually exists, but you
Hey Paul,
OK, I'm kind of on the fence about this one, so if you prefer it this way
I guess it's OK with me.
Acked-by: Paul Zimmerman pa...@synopsys.com
Thanks.
What platforms have you tested this on, BTW? You said you have a Raspberry
Pi, so I'd like you to test these patches there
Am 10.08.2013 13:57, schrieb Alan Stern:
On Sat, 10 Aug 2013, Oleksij Rempel wrote:
usb reset do not affect behaviour of firmware. At least after i remove
all attempts to reboot FW from driver.
If adapter will got reset signal, FW will be notified about it. Then FW
will remove reset flag and
On Sun, Aug 11, 2013 at 12:50:19PM -0700, Paul Zimmerman wrote:
+static int dwc2_find_single_uframe(struct dwc2_hsotg *hsotg, struct dwc2_qh
*qh)
+{
+ unsigned short utime = qh-usecs;
+ int done = 0;
+ int i = 0;
+ int ret = -1;
+
+ while (!done) {
I don't care for
Hi,
On Mon, 2013-07-29 at 15:25 +0300, Felipe Balbi wrote:
Hi,
On Mon, Jul 29, 2013 at 10:04:21AM +0300, Ivan T. Ivanov wrote:
motg-irq = platform_get_irq(pdev, 0);
- if (!motg-irq) {
+ if (motg-irq 0) {
looks like this particular hunk isn't part of $subject.
Indeed.
On Sun, Aug 11, 2013 at 09:53:01PM -0400, Alan Stern wrote:
On Sun, 11 Aug 2013, Mark Brown wrote:
One example that's bugging me right now is that on the Insignal Arndale
platform there's a USB hub connected to one of the USB ports on the SoC
(not as a PHY, it seems we also need the
The chipidea i.MX driver is split into two drivers. The ci_hdrc_imx driver
handles the chipidea cores and the usbmisc_imx driver handles the noncore
registers common to all chipidea cores (but SoC specific). Current flow is:
- usbmisc sets an ops pointer in the ci_hdrc_imx driver during probe
-
The Chipidea i.MX driver has some issues with module loading dependencies.
This fixes this. It is an alternative approach to the one Peter Chen
suggested that does without changing the dt binding.
Sascha
changes since v1:
- make usbmisc optional when fsl,usbmisc property is not present.
Needed
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
drivers/usb/chipidea/ci_hdrc_imx.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
b/drivers/usb/chipidea/ci_hdrc_imx.c
index 14362c0..11ed423 100644
--- a/drivers/usb/chipidea/ci_hdrc_imx.c
+++
[Adding Olof]
On Mon, Aug 12, 2013 at 10:51:36AM +0100, Mark Brown wrote:
On Sun, Aug 11, 2013 at 09:53:01PM -0400, Alan Stern wrote:
On Sun, 11 Aug 2013, Mark Brown wrote:
One example that's bugging me right now is that on the Insignal Arndale
platform there's a USB hub connected to
On Sun, Aug 11, 2013 at 07:02:57PM -0700, Greg Kroah-Hartman wrote:
On Sun, Aug 11, 2013 at 08:08:26PM +0100, Mark Brown wrote:
I know there's been some discussion of this topic but do we have any
general consensus on how to handle such things both from a Linux driver
model point of view
On Mon, Aug 12, 2013 at 12:07:14PM +0100, Mark Rutland wrote:
As I understand it, the wifi chip on the Snow Chromebook has a similar
issue -- it hangs off of a probeable SDIO bus, but needs a regulator
poked for it to turn on and become probeable (see
exynos_wifi_bt_set_power in [1]).
Yes,
When communicating with AT90USB1287, at random intervals (1/25 boots) the linux
hid_output_field Oopses and kills the communicating thread. The AT90USB1287
microcontroller uses LUFA library for usb/hid communication. It is trigged by a
ioctl call from userspace and fails in a kernel paging
At Sat, 10 Aug 2013 12:20:02 +0400,
Maksim A. Boyko wrote:
Add the volume control quirk for avoiding the kernel warning
for the Logitech HD Webcam C525
as in the similar commit 36691e1be6ec551eef4a5225f126a281f8c051c2
for the Logitech HD Webcam C310.
Reported-by: Maksim Boyko
The Tegra30 TRM recommends configuration of certain PHY parameters for
optimal quality. Program the following registers based on device tree
parameters:
- UTMIP_XCVR_HSSLEW: HS slew rate control.
- UTMIP_HSSQUELCH_LEVEL: HS squelch detector level
- UTMIP_HSDISCON_LEVEL: HS disconnect detector
The Tegra30 EHCI controller is mostly compatible with the Tegra20
controller, except Tegra30 includes the HOSTPC register extension.
The has_hostpc capability bit must be set in the ehci_hcd structure if
the controller has such extensions. The new tegra_ehci_soc_config
structure is added to
Document the new device tree parameters for Tegra30 USB PHY.
Signed-off-by: Tuomas Tynkkynen ttynkky...@nvidia.com
Tested-by: Stephen Warren swar...@nvidia.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
.../devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt| 15 ---
1
Some of the PHY parameters are not set according to the TRMs:
- UTMIP_FS_PREABMLE_J should be set, not cleared
- UTMIP_XCVR_LSBIAS_SEL should be cleared, not set
- UTMIP_PD_CHRG should be set in host mode and cleared in device mode
- UTMIP_XCVR_SETUP is a two-part field; the upper bits were not
Hi all,
Here are the patches for the USB tree to enable USB Host support on Tegra30 and
Tegra114. These are based on my and Mikko's cleanup patches that just got
merged to Felipe's tree.
The first one touches the core hub code to prevent certain (non-standard) clock
disable features as our
The has_hostpc capability bit indicates that the host controller has the
HOSTPC register extensions, but at the same time enables clock disabling
power saving features with the PHY Low Power Clock Disable (PHCD) bit.
However, some host controllers have the HOSTPC extensions but don't
support the
The Tegra30 USB PHY is a bit different than the Tegra20 PHY:
- The EHCI controller supports the HOSTPC register extension, and some
of the fields that the PHY needs to modify (PHCD and PTS) have moved
to the new HOSTPC register.
- Some of the UTMI PLL configuration registers have moved from
On Wed, Aug 07, 2013 at 08:51:27AM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Using SIMPLE_DEV_PM_OPS can make the code simpler and cleaner.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
Reviewed-by: Mark Brown broo...@linaro.org
signature.asc
Hi,
I got a bug report about an enclosure that mishandles READ_CAPACITY10.
I don't want to introduce yet another quirk. So what about basing this
on USB version?
Regards
Oliver
From 58cb3cd4b8a58d986b74e0a41d52de989dbe64bc Mon Sep 17 00:00:00 2001
From: Oliver Neukum
At Thu, 1 Aug 2013 13:37:45 -0400 (EDT),
Alan Stern wrote:
On Mon, 29 Jul 2013, Clemens Ladisch wrote:
Alan Stern wrote:
Clemens remarked some time ago that keeping the queue full would be
trivial, if only he knew how full it needed to be. The answer to that
is given above. I
On Mon, Aug 12, 2013 at 12:29:41PM +0200, Sascha Hauer wrote:
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
drivers/usb/chipidea/ci_hdrc_imx.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
b/drivers/usb/chipidea/ci_hdrc_imx.c
index
On Mon, Aug 12, 2013 at 12:29:42PM +0200, Sascha Hauer wrote:
The chipidea i.MX driver is split into two drivers. The ci_hdrc_imx driver
handles the chipidea cores and the usbmisc_imx driver handles the noncore
registers common to all chipidea cores (but SoC specific). Current flow is:
-
On 01/08/2013 08:18, Boris BREZILLON :
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to 48Mhz.
This configuration was formely done in mach-at91/clock.c,
On 01/08/2013 19:09, Boris BREZILLON :
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to 48Mhz.
This configuration was formely done in mach-at91/clock.c,
On Mon, 12 Aug 2013, Oliver Neukum wrote:
Hi,
I got a bug report about an enclosure that mishandles READ_CAPACITY10.
I don't want to introduce yet another quirk. So what about basing this
on USB version?
@@ -211,8 +212,12 @@ static int slave_configure(struct scsi_device *sdev)
On Mon, 2013-08-12 at 10:36 -0400, Alan Stern wrote:
On Mon, 12 Aug 2013, Oliver Neukum wrote:
Hi,
I got a bug report about an enclosure that mishandles READ_CAPACITY10.
I don't want to introduce yet another quirk. So what about basing this
on USB version?
@@ -211,8 +212,12 @@
On Mon, 12 Aug 2013, Takashi Iwai wrote:
Here's what I've got. In turns out the predicting the optimum number
of URBs needed is extremely difficult. I decided it would be better to
make an overestimate and then to submit URBs as needed, rather than
keeping all of them active all the
At Mon, 12 Aug 2013 10:53:36 -0400 (EDT),
Alan Stern wrote:
On Mon, 12 Aug 2013, Takashi Iwai wrote:
Here's what I've got. In turns out the predicting the optimum number
of URBs needed is extremely difficult. I decided it would be better to
make an overestimate and then to submit
Hello, Jonathan.
On Mon, Aug 12, 2013 at 12:04:11AM -0700, Jonathan Nieder wrote:
My laptop fails to boot[1] with the message 'Volume group data not
found'. Bisects to v3.8-rc4~17 (the above commit). Reverting that
commit on top of current master (d92581fcad18, 2013-08-10) produces
a
wa_urb_enqueue_run locks and unlocks its list lock as it traverses the
list of queued transfers. This was done to prevent deadlocking due to
acquiring locks in reverse order in different places. The problem is that
releasing the lock during the list traversal could allow the dequeue
routine
Hi Sarah,
I will resubmit the patch with these changes shortly.
On Fri, Aug 9, 2013 at 10:22 AM, Sarah Sharp
sarah.a.sh...@linux.intel.com wrote:
Hi Shawn,
I noticed that the ChromeOS kernel tree is still using this particular
patch, and thought it was probably time to revisit it.
On Sat,
On Mon, 12 Aug 2013, Takashi Iwai wrote:
So... Clemens, Daniel, Eldad, could you guys review the latest version
of Alan's patch? I'd love to sort this out for 3.12.
Here's a revised version of the patch (still untested). The difference
is that this version tries always to keep a period's
This fixes an issue where the bulk-in urb used for incoming data transfer
is not resubmitted if the packet recieved contains an error status. This
results in the driver locking until the port is closed and re-opened.
Tested on a custom board with a Cinterion GSM module.
Signed-off-by: Matt
On Mon, Aug 12, 2013 at 10:11:39AM -0700, Matt Burtch wrote:
This fixes an issue where the bulk-in urb used for incoming data transfer
is not resubmitted if the packet recieved contains an error status. This
results in the driver locking until the port is closed and re-opened.
Tested on a
Hi,
On Fri, Aug 09, 2013 at 11:04:48AM -0400, Alan Stern wrote:
heh, it doesn't need to be entirely in the core. Core could have the
generic calls and HCDs could implement some callbacks, but I think quite
a bit of the code will be similar if we implement the same thing on all
On Fri, Aug 09, 2013 at 03:16:20PM +, Wang, Yu Y wrote:
On Fri, Aug 09, 2013 at 01:34:09PM +, Wang, Yu Y wrote:
On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
Hi Balbi,
Because dwc3 driver request_threaded_irq with flags IRQF_ONESHOT
and IRQF_SHARED.
On Fri, Aug 09, 2013 at 10:31:58AM -0500, Kumar Gala wrote:
On Aug 9, 2013, at 4:53 AM, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
MSM USB3.0 core wrapper consist of USB3.0 IP (SNPS)
probably good to spell out Synopsys rather than SNPS
Synopsys (the company) has
On Fri, Aug 09, 2013 at 01:42:15PM -0500, Kumar Gala wrote:
On Aug 9, 2013, at 11:28 AM, Mark Rutland wrote:
On Fri, Aug 09, 2013 at 04:40:32PM +0100, Kumar Gala wrote:
The binding spec wasn't clear that the order of the phandles in the
usb-phy array has meaning. Clarify this point in
On 08/12/2013 05:07 AM, Mark Rutland wrote:
[Adding Olof]
On Mon, Aug 12, 2013 at 10:51:36AM +0100, Mark Brown wrote:
On Sun, Aug 11, 2013 at 09:53:01PM -0400, Alan Stern wrote:
On Sun, 11 Aug 2013, Mark Brown wrote:
One example that's bugging me right now is that on the Insignal Arndale
On Fri, Aug 09, 2013 at 09:23:08PM +0300, Philippe De Swert wrote:
Some bad gadget drivers do not check the return status of usb_add_config.
fix the gadget driver
Thus they get a not correctly initialized config and when this gadget gets
deactivated the whole kernel crashes. Since on
On Mon, Aug 12, 2013 at 03:52:01PM +0200, Nicolas Ferre wrote:
On 01/08/2013 08:18, Boris BREZILLON :
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to
rh_call_control() contains a buffer, tbuf, which it uses to hold
USB descriptors. These discriptors are eventually copied into the
transfer_buffer in the URB. The buffer in the URB is dynamically
defined and is always large enough to hold the amount of data it
requests.
tbuf is currently
Reviewed-by: Dongjin Kim tobet...@gmail.com
I like this patch series, I dropped my changes to support non-i2c
based operation.
On Fri, Aug 9, 2013 at 7:41 PM, Mark Brown broo...@kernel.org wrote:
From: Mark Brown broo...@linaro.org
Refactor so that register writes for configuration are only
From: popcornmix [mailto:popcorn...@gmail.com]
Sent: Monday, August 12, 2013 6:39 AM
On Mon, Aug 12, 2013 at 8:40 AM, Matthijs Kooijman matth...@stdin.nl wrote:
Paul, did you try the patch without this hunk?
Dom, can you tell use why this hunk is needed?
The microframe patch
On Fri, Aug 09, 2013 at 07:09:18PM +0300, Ivan T. Ivanov wrote:
Hi,
On Fri, 2013-08-09 at 16:23 +0300, Felipe Balbi wrote:
Hi,
On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
diff --git a/drivers/usb/dwc3/dwc3-msm.c b/drivers/usb/dwc3/dwc3-msm.c
new file mode
On Mon, Aug 12, 2013 at 06:18:00PM +, Paul Zimmerman wrote:
From: popcornmix [mailto:popcorn...@gmail.com]
Sent: Monday, August 12, 2013 6:39 AM
On Mon, Aug 12, 2013 at 8:40 AM, Matthijs Kooijman matth...@stdin.nl
wrote:
Paul, did you try the patch without this hunk?
Dom,
On Mon, Aug 12, 2013 at 12:35:25AM +0400, Sergei Shtylyov wrote:
Hello.
On 08/11/2013 03:08 AM, Sergei Shtylyov wrote:
I have basically two questions on this change:
[...]
2) why you omitted am35x.c from this commit?
mistake
Are you going to fix it, or should I?
On Mon, 12 Aug 2013, Felipe Balbi wrote:
maybe a single callback for supporting 'testmodes' ? which receives the
test mode as argument ?
I don't have a clear picture of how you would apply such an approach to
this case. There would have to be a way to tell the HCD to insert a
musb_dsps.c utilizes a symbol which is only
available when CONFIG_OF_IRQ is set, so make
it depend on that.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index
On Sat, Aug 03, 2013 at 04:37:51PM +0200, Hans de Goede wrote:
Signed-off-by: Hans de Goede hdego...@redhat.com
---
Documentation/ABI/testing/sysfs-bus-usb | 38
+
1 file changed, 38 insertions(+)
This patch doesn't apply at all, can you redo it against the
On Sat, Aug 10, 2013 at 01:04:33PM +0530, Manjunath Goudar wrote:
Separate the W90X900(W90P910) on-chip host controller driver from
ehci-hcd host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other
On Sat, Aug 10, 2013 at 01:14:15PM +0530, Manjunath Goudar wrote:
Separate the OHCI NXP host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM.
Many place function name and struct name
On Mon, Aug 12, 2013 at 11:09:25AM -0700, Sean O. Stalley wrote:
rh_call_control() contains a buffer, tbuf, which it uses to hold
USB descriptors. These discriptors are eventually copied into the
transfer_buffer in the URB. The buffer in the URB is dynamically
defined and is always large
On Mon, Aug 12, 2013 at 12:08:17PM -0600, Stephen Warren wrote:
In a similar way, I wonder if the USB case can be considered the same
way? This seems less like a good fit since I don't expect the resources
are always so similar there, and also there's the case of the bus being
potentially
On Tue, Aug 06, 2013 at 01:16:50PM -0700, Sarah Sharp wrote:
On Tue, Aug 06, 2013 at 02:48:57PM -0400, Alan Stern wrote:
On Tue, 6 Aug 2013, Sarah Sharp wrote:
On Tue, Aug 06, 2013 at 10:16:15AM -0400, Alan Stern wrote:
Patch 1 has been rendered out of date by intervening changes
On Mon, Aug 12, 2013 at 12:23:44PM +0100, Mark Brown wrote:
On Sun, Aug 11, 2013 at 07:02:57PM -0700, Greg Kroah-Hartman wrote:
On Sun, Aug 11, 2013 at 08:08:26PM +0100, Mark Brown wrote:
I know there's been some discussion of this topic but do we have any
general consensus on how to
On Mon, 12 Aug 2013 gre...@linuxfoundation.org wrote:
This is a note to let you know that I've just added the patch titled
usb: ehci: Add support for SINGLE_STEP_SET_FEATURE test of EHSET
to my usb git tree which can be found at
On Mon, Aug 12, 2013 at 01:50:07PM -0700, Greg Kroah-Hartman wrote:
On Mon, Aug 12, 2013 at 12:23:44PM +0100, Mark Brown wrote:
I don't think they're bus specific - the main issue with a lot of this
is that they're outside the infrastructure that the bus standardises so
we should have a
This patch defines a new trace event, which is called xhci_dbg_ring_expansion
and belongs to the event class xhci_log_msg, and adds tracepoints that trace
the debug messages associated with the expansion of endpoint ring when there
is not enough space allocated to hold all pending TRBs.
On Mon, Aug 05, 2013 at 06:40:13PM +0100, Rupesh Gujare wrote:
This patch fixes crash issue when there is quick cycle of
de-enumeration enumeration due to loss of wireless link.
It is found that sometimes new device (or coming back device)
returns very fast, even before USB core read out
On Mon, Aug 12, 2013 at 11:16:24PM +, Stalley, Sean wrote:
-Original Message-
From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
Sent: Monday, August 12, 2013 1:32 PM
To: Stalley, Sean
Cc: linux-usb@vger.kernel.org; Sarah Sharp; Ismail, Abdul R; Alan Stern
On Tue, Aug 13, 2013 at 01:50:55AM +0200, srenau...@free.fr wrote:
Hello !
Is it possible to add the Hercules mini 300m v2 in the device list of
rtl8192cu.
The ID of this one is 0x06F8, 0xE035.
Does the driver work with these new device ids? If so, great, can you
send us a patch adding
On Mon, Aug 12, 2013 at 8:50 PM, srenau...@free.fr wrote:
Hello !
Is it possible to add the Hercules mini 300m v2 in the device list of
rtl8192cu.
The ID of this one is 0x06F8, 0xE035.
Does this work for you?
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
On Mon, 12 Aug 2013, Mark Brown wrote:
On Mon, Aug 12, 2013 at 01:50:07PM -0700, Greg Kroah-Hartman wrote:
On Mon, Aug 12, 2013 at 12:23:44PM +0100, Mark Brown wrote:
I don't think they're bus specific - the main issue with a lot of this
is that they're outside the infrastructure that
On Fri, Aug 09, 2013 at 03:16:20PM +, Wang, Yu Y wrote:
On Fri, Aug 09, 2013 at 01:34:09PM +, Wang, Yu Y wrote:
On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
Hi Balbi,
Because dwc3 driver request_threaded_irq with flags
IRQF_ONESHOT and
Hi,
As requested by Greg Kroah, please see bug 60738 - Summary: USB 3.0
connection delay seems to be too short for HP USB 3.0 hard drive.
I'll be pleased to help you as much as possible.
--
Alexandre Demers
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of
On Tue, Aug 06, 2013 at 08:40:56PM -0700, Sarah Sharp wrote:
On Tue, Aug 06, 2013 at 06:04:36AM +0800, Greg Kroah-Hartman wrote:
On Mon, Aug 05, 2013 at 09:46:46AM -0700, Sarah Sharp wrote:
I wanted to test it for a kernel release to make sure it didn't cause
any issues before sending it
On Mon, Aug 05, 2013 at 09:07:51PM -0400, Alan Stern wrote:
On Tue, 6 Aug 2013, Greg KH wrote:
Have you tried this patch?
http://marc.info/?l=linux-usbm=137523956310060w=2
What is the status of this patch, I'm starting to get lots of complaints
about this :(
James
79 matches
Mail list logo
