On Thu, 2012-12-06 at 18:35 +, Cunningham, Robert wrote:
> I'm trying to bring up an OMAP4 system based on Variscite's OM44 module
> running Linaro's Ubuntu Precise in a headless configuration. The system
> contains two SMSC LAN7500 USB-GigE chips (not dongles), both of which are
> fully fu
On Thu, 2012-12-06 at 12:44 -0600, Dan Williams wrote:
> On Thu, 2012-12-06 at 18:35 +, Cunningham, Robert wrote:
> > I'm trying to bring up an OMAP4 system based on Variscite's OM44 module
> > running Linaro's Ubuntu Precise in a headless configuration. The
>
> > On Fri, Dec 7, 2012 at 12:21 AM, Dan Williams wrote:
> > > On Thu, 2012-12-06 at 12:44 -0600, Dan Williams wrote:
> > >> On Thu, 2012-12-06 at 18:35 +, Cunningham, Robert wrote:
> > >> > I'm trying to bring up an OMAP4 system based
On Fri, 2012-12-07 at 15:27 +, Cunningham, Robert wrote:
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Friday, December 07, 2012 7:17 AM
> > Subject: Re: Random MAC address from smsc75xx: How to permanently set?
> >
> > On Fri, 2012-12-07 at 14:13 +
On Mon, 2012-12-10 at 15:15 -0800, United Seabears Corp. wrote:
> Two months ago I asked for
> assistance with the installation of a Franklin U600 3G/4G modem on the
> above OS. Meanwhile I managed to get the 3G part of the dual modem to
> work reliably.
> I had to discover on my own that this m
On Mon, 2012-12-10 at 15:15 -0800, United Seabears Corp. wrote:
> Two months ago I asked for
> assistance with the installation of a Franklin U600 3G/4G modem on the
> above OS. Meanwhile I managed to get the 3G part of the dual modem to
> work reliably.
> I had to discover on my own that this m
killed/re-submitted for suspend/resume, as before.
Signed-off-by: Dan Williams
---
Oliver: alternatively, is there a problem with *always*
submitting the interrupt URB, and then simply not calling
the subdriver's .status function when the netdev is
closed? That would be a much simpler
dication can be received even if the netdev is closed, which is
the case right after device insertion.
Signed-off-by: Dan Williams
---
diff --git a/drivers/net/usb/sierra_net.c b/drivers/net/usb/sierra_net.c
index 18dd425..e6e2857 100644
--- a/drivers/net/usb/sierra_net.c
+++ b/drivers/net/u
On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote:
> On Friday 04 January 2013 10:48:16 Dan Williams wrote:
> > Some drivers (ex sierra_net) need the status interrupt URB
> > active even when the device is closed, because they receive
> > custom indications from firmwar
On Sat, 2013-01-05 at 11:59 +0100, Bjørn Mork wrote:
> Dan Williams writes:
> > On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote:
> >> On Friday 04 January 2013 10:48:16 Dan Williams wrote:
> >> > Some drivers (ex sierra_net) need the status interrupt URB
>
On Sat, 2013-01-05 at 12:01 +0100, Oliver Neukum wrote:
> On Friday 04 January 2013 19:26:33 Dan Williams wrote:
> > On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote:
> > > On Friday 04 January 2013 10:48:16 Dan Williams wrote:
> > > > Some drivers (ex sierra_
On Wed, 2013-01-09 at 16:54 +0800, hockseng leow wrote:
> I got the dmesg after having the parameters, usbserial.vendor=0x2357
> usbserial.product=0x0200" in the linux start-up.
>
> I already got the modem working under usb_modeswitch.
>
> No further work need to be done in the kernel.
Are you a
On Sat, 2013-01-12 at 15:35 -0800, David Miller wrote:
> From: Wei Shuai
> Date: Sat, 12 Jan 2013 19:34:39 +0800
>
> > Infineon(now Intel) HSPA Modem platform NCM cannot support ARP. so I
> > introduce a flag CDC_NCM_DRIVER_DATA_NOARP which is defined in
> > driver_info:data. so later on, if more
On Sun, 2013-01-13 at 20:09 +0100, mas...@georadis.com wrote:
> Hello guys,
> I've found a following problems on BeagleBoard and Kernel 3.0.8 with
> gadget serial driver.
>
> Attached is a small program, which opens gadget serial tty at
> /dev/ttyGS0. USB is NOT connected to host. Then it fills
On Sat, 2013-01-05 at 12:01 +0100, Oliver Neukum wrote:
> On Friday 04 January 2013 19:26:33 Dan Williams wrote:
> > On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote:
> > > On Friday 04 January 2013 10:48:16 Dan Williams wrote:
> > > > Some drivers (ex sierra_
On Fri, 2013-01-11 at 11:06 +0800, Ming Lei wrote:
> On Sat, Jan 5, 2013 at 9:26 AM, Dan Williams wrote:
> > On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote:
> >> On Friday 04 January 2013 10:48:16 Dan Williams wrote:
> >> > Some drivers (ex sierra_net)
On Sat, 2013-01-12 at 19:34 +0800, Wei Shuai wrote:
> Infineon(now Intel) HSPA Modem platform NCM cannot support ARP. so I
> introduce a flag CDC_NCM_DRIVER_DATA_NOARP which is defined in
> driver_info:data. so later on, if more such buggy devices are found, they
> could use same flag to handle.
On Thu, 2013-01-17 at 14:44 +0800, Wei Shuai wrote:
> OK, I will follow up. after add FLAG_NOARP, how should I handle
> IFF_NOARP? will I do it in cdc_ncm.c or usb_net.c?
usbnet.c
Dan
> 2013/1/17 Dan Williams :
> > On Sat, 2013-01-12 at 19:34 +0800, Wei Shuai wrote:
> >
On Tue, 2016-11-15 at 20:13 +0100, Giuseppe Lippolis wrote:
> Dear all,
> I'm porting the Dlink DWR-512 device to LEDE (embedded linux).
> This device embed a 3G modem connected through the usb bus .
> The modem work properly with the option kernel module.
>
> I added these line in the
>
>
On Wed, 2016-11-16 at 11:49 -0600, Dan Williams wrote:
> On Tue, 2016-11-15 at 20:13 +0100, Giuseppe Lippolis wrote:
> >
> > Dear all,
> > I'm porting the Dlink DWR-512 device to LEDE (embedded linux).
> > This device embed a 3G modem connected through the usb b
On Thu, 2016-11-17 at 11:15 +0100, Johan Hovold wrote:
> On Wed, Nov 16, 2016 at 10:03:52PM +0100, Giuseppe Lippolis wrote:
> >
> > Dear All,
> > thanks for the very interesting discussion.
> >
> > >
> > > >
> > > > This will make option grab all the ports, as shown by your
> > > > dmesg
> > >
only* claim interfaces and devices they
actually should drive. They should not claim interfaces they should
not or cannot drive.
Dan
> Thanks,
> Bye.
>
> >
> > -Ursprüngliche Nachricht-
> > Von: Oliver Neukum [mailto:oneu...@suse.com]
> > Gesendet: Mittwo
On Wed, 2015-12-16 at 10:39 +0100, Daniele Palmas wrote:
> This patch series add support in the cdc_ncm driver for two devices
> based on the same platform, that are different only for carrier
> customization.
>
> The devices do not have ARP capabilities.
>
> Daniele Palmas (2):
> net: usb: cdc
On Mon, 2016-01-04 at 12:32 +0700, Lars Melin wrote:
> On 2016-01-04 05:00, Jose Alonso wrote:
> >
> > The program Heimdall (http://glassechidna.com.au/heimdall) is used
> > to flash a new firmware in Samsung Mobile Phones. It uses only the
> > library libusb to access the device.
> >
> > The mod
On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> On 2016-02-19 17:31, Bjørn Mork wrote:
> > Daniel Johnson writes:
> >
> > > > > Currently 4 ttyUSB devices are detected, but only the second
> > > > > two respond to
> > > > > AT commands. The first two serial ports may be falsely
> > > > > d
On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
> Dan Williams writes:
> > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> >
> > > cfg #1
> > > MI_00 HP Mobile Connect - PC UI Interface
> > > MI_01 HP Mobile Connect - Application Inter
On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote:
> On 2016-02-21 10:09, Daniel Johnson wrote:
> > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork wrote:
> > > One of them is likely a QCDM port if this is really a Qualcomm
> > > based
> > > device. The other might be an inactive NMEA port. Seria
On Sun, 2016-02-21 at 12:44 +0700, Lars Melin wrote:
> On 2016-02-20 03:34, Dan Williams wrote:
> > On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
> > > Dan Williams writes:
> > > > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> > > >
On Thu, 2016-02-25 at 18:15 +0100, Bjørn Mork wrote:
> Dan Williams writes:
> > On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote:
> > > On 2016-02-21 10:09, Daniel Johnson wrote:
> > > > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork
> > > > wrote:
>
On Sat, 2016-08-20 at 14:50 +0300, Aleksandr Makarov wrote:
> USB: serial: option: add WeTelecom WM-D200
>
> Add support for WeTelecom WM-D200.
>
> T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=22de Pr
On Mon, 2016-08-22 at 20:07 +0300, Aleksandr Makarov wrote:
> 22.08.2016 18:03, Dan Williams пишет:
> >
> > On Sat, 2016-08-20 at 14:50 +0300, Aleksandr Makarov wrote:
> > >
> > > USB: serial: option: add WeTelecom WM-D200
> > >
> > > Add sup
On Tue, 2016-08-23 at 14:25 +0300, Aleksandr Makarov wrote:
> 22.08.2016 22:20, Dan Williams пишет:
> >
> > On Mon, 2016-08-22 at 20:07 +0300, Aleksandr Makarov wrote:
> > >
> > > 22.08.2016 18:03, Dan Williams пишет:
> > > >
> > > >
>
On Tue, 2017-01-24 at 10:36 +0100, Bjørn Mork wrote:
> Bjørn Mork writes:
>
> > From: Dan Williams
>
> Woops! I didn't intend to blame this on you Dan. Sorry. I reused
> your
> commit message, and obviously unintentionally also the "author"
> line...
On Thu, 2017-03-09 at 10:28 +0100, Oliver Neukum wrote:
> Am Mittwoch, den 08.03.2017, 17:30 -0500 schrieb Balazs Harmath:
> > Hi guys,
> >
> > I’w working with a Quectel EC21 modem and i ran into an issue that
> > the qcserial driver is not getting installed for it.
> > Previously i was working
Add Quectel UC15, UC20, EC21, and EC25. The EC20 is handled by
qcserial due to a USB VID/PID conflict with an existing Acer
device.
Signed-off-by: Dan Williams
---
NOTE: The UC20, EC21, and EC25 should also get a corresponding qmi_wwan
patch but I don't have that lying around at this
On Thu, 2017-03-09 at 13:14 -0500, Balazs Harmath wrote:
> So i can expect these to be added soon?
Are you able to apply and test this patch, and see if it works for your
device? That would help.
Thanks!
Dan
> Thanks,
> Bali
>
>
> > On Mar 9, 2017, at 12:32 PM
On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> From: danielepa
>
> Add PID and special handling for Telit LE920
Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
interface that could be used instead of PPP? What's the lsusb -v output
for the device?
Dan
> Sig
On Tue, 2013-01-29 at 11:19 -0600, Dan Williams wrote:
> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> > From: danielepa
> >
> > Add PID and special handling for Telit LE920
>
> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
>
On Thu, 2013-01-31 at 19:50 +0100, Bjørn Mork wrote:
> Bastian Löffler writes:
>
> > Hello,
> >
> > my device seems to be out of order since a few weeks:
> >
> > [ 5965.767060] usbserial_generic 1-2:1.1: generic converter detected
> > [ 5965.767198] usb 1-2: generic converter now attached to ttyU
It advertises a standard CDC-ETHER interface, which actually should be
driven by qmi_wwan.
Signed-off-by: Dan Williams
---
diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
index 3f3d12d..cc6d0c1 100644
--- a/drivers/net/usb/cdc_ether.c
+++ b/drivers/net/usb/cdc_ether.c
killed/re-submitted for suspend/resume, as before.
Signed-off-by: Dan Williams
---
Note: unchanged from previous version, but rebased.
drivers/net/usb/usbnet.c | 43 +++
include/linux/usb/usbnet.h | 3 +++
2 files changed, 34 insertions(+), 12
NTR_ALWAYS.
Second, move the code that sends the SYNC message out of the
bind() hook and after usbnet_probe() to ensure the interrupt URB
is set up before trying to use it.
Signed-off-by: Dan Williams
---
drivers/net/usb/sierra_net.c | 33 ++---
1 file changed, 26 insert
On Wed, 2013-02-06 at 20:51 +0100, Bjørn Mork wrote:
> Dan Williams writes:
>
> > It advertises a standard CDC-ETHER interface, which actually should be
> > driven by qmi_wwan.
> >
> > Signed-off-by: Dan Williams
> > ---
> > diff --git a/drivers/net/usb
On Wed, 2013-02-06 at 22:11 +0100, Bjørn Mork wrote:
> Dan Williams writes:
>
> > As part of the initialization sequence, the driver sends a SYNC message
> > via the control pipe to the firmware, which appears to request a
> > firmware restart. The firmware responds wi
On Wed, 2013-02-06 at 21:17 +0100, Oliver Neukum wrote:
> On Wednesday 06 February 2013 12:42:56 Dan Williams wrote:
> > As part of the initialization sequence, the driver sends a SYNC message
> > via the control pipe to the firmware, which appears to request a
> > firmware r
On Tue, 2013-02-12 at 13:42 +0100, Bjørn Mork wrote:
> Interface layout:
>
> 00 CD-ROM
> 01 debug COM port
> 02 AP control port
> 03 modem
> 04 usb-ethernet
Any idea what AT command set the thing uses? If it's got an ethernet
port, then it's going to have some proprietary commands to start/
On Wed, 2013-02-13 at 08:53 +0100, Bjørn Mork wrote:
> Dan Williams writes:
>
> > On Tue, 2013-02-12 at 13:42 +0100, Bjørn Mork wrote:
> >> Interface layout:
> >>
> >> 00 CD-ROM
> >> 01 debug COM port
> >> 02 AP control port
>
On Wed, 2013-02-13 at 15:27 +0100, Oliver Neukum wrote:
> On Saturday 09 February 2013 20:16:20 Bjørn Mork wrote:
> > Oliver Neukum writes:
> > > On Saturday 09 February 2013 18:41:52 Bjørn Mork wrote:
>
> > Well, OK..., "generic" then. In the sense that the attribute stays the
> > same regardle
On Wed, 2013-02-13 at 12:44 +0100, Bjørn Mork wrote:
> Dan Williams writes:
>
> > It doesn't need to run exactly at probe, but it appears to need to be
> > the first thing the driver does when communicating with the firmware to
> > ensure clear state and whatnot
4 ports; AT/PPP is standard CDC-ACM. The other three (added by this
patch) are QCDM/DIAG, possibly GPS, and unknown.
Signed-off-by: Dan Williams
---
diff --git a/drivers/usb/serial/qcaux.c b/drivers/usb/serial/qcaux.c
index 9b1b96f..31f81c3 100644
--- a/drivers/usb/serial/qcaux.c
+++ b/drivers
It advertises a standard CDC-ETHER interface, which actually should be
driven by qmi_wwan.
Signed-off-by: Dan Williams
---
index 3f3d12d..57136dc 100644
--- a/drivers/net/usb/cdc_ether.c
+++ b/drivers/net/usb/cdc_ether.c
@@ -615,6 +615,13 @@ static const struct usb_device_id products
4 ports; AT/PPP is standard CDC-ACM. The other three (added by this
patch) are QCDM/DIAG, possibly GPS, and unknown.
Signed-off-by: Dan Williams
---
This time with a [PATCH] prefix.
diff --git a/drivers/usb/serial/qcaux.c b/drivers/usb/serial/qcaux.c
index 9b1b96f..31f81c3 100644
--- a/drivers
On Wed, 2013-03-06 at 09:44 +0800, Greg KH wrote:
> On Wed, Mar 06, 2013 at 01:34:44AM +, Linlei (Lei Lin) wrote:
> > Hello Mork,
> >
> > >> -- Because in the embedded linux system, Android, or Chrome OS,
> > >> etc. They don't integrate userspace usb_modeswitch utility for
> > >> switch
On Fri, 2013-03-08 at 22:03 +0100, Loic Domaigne wrote:
> This patch limits the Rx URB size to 16kB if the driver is compiled for a
> VMware environment. As of workstation 9, there are some major performance
> problems if the Rx URB size exceeds that limit.
>
> This patch applies to longterm kerne
With Gobi 1K devices, USB interface #3's altsetting is 0 by default, but
altsetting 0 only provides one interrupt endpoint and is not sufficent
for QMI. Altsetting 1 provides all 3 endpoints required for qmi_wwan
and works with QMI.
IIRC the altsetting used to be set by qcserial back before we ma
out losing the added benefit of using a single bind
> function.
>
> The driver has always required a CDC Union functional descriptor
> for two-interface functions. Using the existence of this
> descriptor to detect two-interface functions is the logically
> correct method.
>
&
Turns out we just need altsetting 1 and then we can talk to it.
Signed-off-by: Dan Williams
---
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 2466254..59b32b7 100644
--- a/drivers/usb/serial/qcserial.c
+++ b/drivers/usb/serial/qcserial.c
@@ -197,12 +197,15
On Wed, 2013-03-13 at 08:11 -0700, Greg KH wrote:
> On Wed, Mar 13, 2013 at 09:58:18AM -0500, Dan Williams wrote:
> > Turns out we just need altsetting 1 and then we can talk to it.
> >
> > Signed-off-by: Dan Williams
>
> Should this go to the -stable releases as w
h
the 1K and 2K+ cases separately. This patch should not affect the new
Sierra device support, because those devices are matched via
interface-specific matching and thus should never hit the composite
code.
Signed-off-by: Dan Williams
---
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/se
On Mon, 2012-07-23 at 22:23 +0200, Bjørn Mork wrote:
> Dan Williams writes:
>
> > Bjorn's latest patchset does break Gobi 1K and 2K because on both
> > devices as it claims usb interface 0. That's because usbif 0 is not
> > handled in the switch statement, and
Tag Ericsson NCM devices as WWAN modems, since they almost certainly all
are. This way userspace clients know that the device requires further
setup on the AT-capable serial ports before connectivity is available.
Signed-off-by: Dan Williams
---
NOTE: it seems unlikely that all NCM devices are
On Wed, 2012-08-15 at 15:43 +0200, Bjørn Mork wrote:
> The ZTE (Vodafone) K5006-Z use the following
> interface layout:
>
> 00 DIAG
> 01 secondary
> 02 modem
> 03 networkcard
> 04 storage
>
> Ignoring interface #3 which is handled by the qmi_wwan
> driver.
At some point you should just start add
On Fri, 2012-09-07 at 10:53 +0200, Bjørn Mork wrote:
> Oliver Neukum writes:
> > On Thursday 06 September 2012 10:17:46 Bjørn Mork wrote:
> >> Not really related, but I am still worrying how MBIM is going to fit
> >> into the usbnet model where you have a strict relation between one
> >> netdev an
Greg,
Just (finally?) noticed the zte_ev driver was added for v3.7 kernel; and
it contains ID conflicts with 'option' for 0x05c6/0x6000, 0x19d2/0xfffe,
and 0x19d2/0x. These devices are listed in both drivers as being
ZTE devices (despite the Qualcomm vendor ID of one), so perhaps the IDs
shou
On Tue, 2013-06-04 at 12:18 -0700, Greg KH wrote:
> On Tue, Jun 04, 2013 at 12:50:06PM -0500, Dan Williams wrote:
> > Greg,
> >
> > Just (finally?) noticed the zte_ev driver was added for v3.7 kernel; and
> > it contains ID conflicts with 'option' for 0x05c6/
e the 2718 over because I could not find any ZTE Linux
drivers for that device, nor even any Windows drivers.
Signed-off-by: Dan Williams
---
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 7343728..94dbddd 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/s
-off-by: Dan Williams
---
drivers/usb/serial/option.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 7343728..7df7c67 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
@@ -159,7 +159,6 @@ static void
On Thu, 2013-06-20 at 13:27 -0500, Dan Williams wrote:
> The USB-1000 is a Gobi1K device in USB dongle form, requires firmware
> download via gobi_loader, and has the Gobi1K descriptor layout. It
> also supports QMI like any other Gobi1K device, but option grabs
> all the USB in
These devices are all Gobi1K devices (according to the Windows INF
files) and should be handled by qcserial instead of option. Their
network port is handled by qmi_wwan.
Signed-off-by: Dan Williams
---
drivers/usb/serial/option.c | 4
drivers/usb/serial/qcserial.c | 8 +++-
2 files
On Thu, 2013-06-27 at 16:12 +0200, Enrico Mioso wrote:
> Hi Bjorn and thank you very much for your kindness, attention and reply!
>
> Yes - I tested the all three ports of the device, even because my
> understanding
> of the Windows INF files is very primitive!
> And yes - I have verified that t
option or qcaux or
sierra or whatever, qcserial should probably be kept to actual Gobi
devices only.
Dan
>
>
> Bjørn
>
> > On Thu, 27 Jun 2013, Bj?rn Mork wrote:
> >
> > ==Date: Thu, 27 Jun 2013 17:44:46 +0200
> > ==From: Bj?rn Mork
> > ==To: En
Speaks AT on interfaces 5 (command & PPP) and 3 (secondary), other
interface protocols are unknown.
Cc: sta...@vger.kernel.org
Signed-off-by: Dan Williams
---
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 5dd857d..feda580 100644
--- a/drivers/usb/serial/opti
On Sun, 2013-08-04 at 01:59 +0200, Enrico Mioso wrote:
> Hello everybody!
> I'm going to investigate a little bit on an obscure Alcatel device - the
> Alcatel X220s, manifactured by TCT Mobile Phones.
>
> It supports a NDIS network interface, as you will be able to discover looking
> at the driv
On Mon, 2013-08-05 at 19:41 +0800, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman
>
> Instead of having to create a new driver for a "simple" usb to serial
> device, mush them all into one file, with a macro, so as to make it easy
> to add new ones.
>
> Cc: "René Bürgel"
> Cc: Wei Shuai
t; Patch is only compile tested.
Tested-by: Dan Williams
> Cc:
> Signed-off-by: Jussi Kivilinna
> ---
> drivers/net/usb/hso.c | 18 ++
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
>
uffer.
>
> Patch is only compile tested.
Tested-by: Dan Williams
> Cc:
> Signed-off-by: Jussi Kivilinna
> ---
> drivers/net/usb/hso.c | 18 ++
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/usb/hso.c b/drivers/n
On Wed, 2013-08-14 at 11:43 -0500, Peter Hyman wrote:
> Linux Kernel: 3.9.10
> Device Driver: usb/serial/sierra.c
> Device Driver version: not known
>
> Apparently Sierra has sold the AirCard 250U product to Netgear, so I am
> sure driver development on drivers/usb/serial/sierra.c will be in limbo
On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote:
> Peter Hyman writes:
>
> > On 08/14/2013 01:42 PM, Bjørn Mork wrote:
> > snip...
> >
> >> Great! And if you can snoop on Windows trying to figure out how to
> >> switch the modes, then that would also help. I believe Wireshark with
> >> usbp
On Thu, 2013-08-15 at 03:47 -0500, Peter Hyman wrote:
> On 08/14/2013 06:03 PM, Dan Williams wrote:
> snip...
> > It's almost certainly not the domain of the driver to switch this mode,
> > it's the responsibility of userland. Kernel drivers must only talk to
> >
On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote:
> On 08/15/2013 09:47 AM, Dan Williams wrote:
> > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote:
> >> Peter Hyman writes:
> >>
> >>> On 08/14/2013 01:42 PM, Bjørn Mork wrote:
> >>> s
On Sat, 2013-08-17 at 18:05 -0400, Peter Hyman wrote:
> On 08/17/2013 04:58 PM, Forest Bond wrote:
>
> snip...
>
>
> > Okay, I published it here:
> >
> >
> http://www.alittletooquiet.net/media/2131024%20CDMA%20EVDO%20CnS%20Reference.pdf
> >
> > For the record, the document states its license a
On Thu, Sep 19, 2013 at 2:37 PM, Sarah Sharp
wrote:
> On Fri, Sep 13, 2013 at 03:50:48PM +0530, Pratyush Anand wrote:
>> On Fri, Sep 13, 2013 at 3:40 PM, Xenia Ragiadakou
>> wrote:
>> > Nope :). There is still Kumar 's patch that keeps the wrappers, so it can
>> > be applied instead of mine. But
On Thu, Sep 19, 2013 at 10:24 PM, Pratyush Anand wrote:
> On Fri, Sep 20, 2013 at 05:37:50AM +0800, Sarah Sharp wrote:
>> On Fri, Sep 13, 2013 at 03:50:48PM +0530, Pratyush Anand wrote:
>> > On Fri, Sep 13, 2013 at 3:40 PM, Xenia Ragiadakou
>> > wrote:
>> > > Nope :). There is still Kumar 's patc
On Sat, Sep 21, 2013 at 3:43 AM, Xenia Ragiadakou wrote:
> On 09/21/2013 04:30 AM, Dan Williams wrote:
> Hi Dan,
>
> What do you mean by saying "1% object size hit"? Do you mean 1% increase in
> xhci footprint?
I was comparing the results of size(1) on xhci-hcd.o
This is all 3.13 material. We may want the enumeration change in
-stable at some point, but for now it needs more exposure.
Comments welcome.
--
Dan
---
Dan Williams (4):
usb: hub_activate kill an 'else'
usb: xhci: kill a conditional when toggling cycle
usb: xhci:
Remove a few extra lines and make it clear that all implementations
disable the port by sharing the same line of code.
Cc: Alan Stern
Signed-off-by: Dan Williams
---
drivers/usb/core/hub.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/core/hub.c
Perform an unconditional toggle of the cycle bit with 'xor'.
Signed-off-by: Dan Williams
---
drivers/usb/host/xhci-ring.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 411da1f..7c043ec 10
Only used for debug output, so we don't need to save it.
Signed-off-by: Dan Williams
---
drivers/usb/host/xhci.c | 10 ++
drivers/usb/host/xhci.h |2 --
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 49
ice, but omits sending
the device a SetAddress command (BSR == block set address request).
Then, after GetDescriptor completes, follow up with the full
AddressDevice+SetAddress operation.
Reported-by: David Moore
Suggested-by: Sarah Sharp
Signed-off-by: Dan Williams
---
On Mon, 2013-09-30 at 08:37 +, Thomas TJ wrote:
> I'm trying to connect Huawei wireless data modem in Freescale i.MX6 Board.
> It's detected as a usb device and the result of lsusb is
> "Bus 002 Device 007: ID 12d1:140b Huawei Technologies Co., Ltd. EC1260
> Wireless Data Modem HSD USB Card"
>
On Mon, Sep 23, 2013 at 4:29 PM, Dan Williams wrote:
> Change the enumeration scheme for xhci attached devices from:
>
>SetAddress
>GetDescriptor(8)
>GetDescriptor(18)
>
> ...to:
>
>GetDescriptor(64)
>SetAddress
>GetDescriptor(18)
>
> Is there a commit id for this, please? and, where can I find this patch? I
> would like to try this on my machine as I have a device that does not
> enumerate on xhci only.
>
Not upstream yet, but you can give the attached one a try.
--
Dan
xhci-new-scheme.patch
Description: Binary data
1" or an address setup
"address device BSR=0"
4/ Patch 1, 2, 3: unchanged
[1]: http://marc.info/?l=linux-usb&m=137997896602457&w=2
[2]: http://marc.info/?l=linux-usb&m=138074667626129&w=2
This Set is against usb-next as of cccd3a25 "usb: wusbcore: fix
Perform an unconditional toggle of the cycle bit with 'xor'.
Signed-off-by: Dan Williams
---
No change since v1
drivers/usb/host/xhci-ring.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 6b
Remove a few extra lines and make it clear that all implementations
disable the port by sharing the same line of code.
Acked-by: Alan Stern
Signed-off-by: Dan Williams
---
No change since v1
drivers/usb/core/hub.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff
Only used for debug output, so we don't need to save it.
Signed-off-by: Dan Williams
---
No change since v1
drivers/usb/host/xhci.c | 10 ++
drivers/usb/host/xhci.h |2 --
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb
Specify whether we are only performing the context setup portion of the
'address device' command, or the full operation issuing 'SetAddress'
on the wire.
Signed-off-by: Dan Williams
---
New in v2
drivers/usb/host/xhci.c | 22 --
1 files changed,
otocol= 0
bMaxPacketSize0= 9
which results in the discovery process looping until falling back to
'old scheme' enumeration.
Cc: Alan Stern
Reported-by: David Moore
Suggested-by: Sarah Sharp
Signed-off-by: Dan Williams
---
Changes since v1
1/ Updated after testing to disab
On Mon, Oct 7, 2013 at 12:41 PM, Alan Stern wrote:
> On Mon, 7 Oct 2013, Dan Williams wrote:
>
>> Change the default enumeration scheme for xhci attached USB < 3 devices
>> from:
>
> Careful about the distinction between USB-3 and SuperSpeed. They
> aren'
On Tue, 2013-10-08 at 11:29 -0400, Don Zickus wrote:
> Hi Oliver,
>
> I am trying to verify a fix for the cdc-wdm driver and am having trouble
> figuring out what devices requires that driver. It seems related to cell
> phones but I wasn't sure if there was a particular one or all of them in
> ge
1 - 100 of 650 matches
Mail list logo
