On 2016-05-16 09:43, YAMAMOTO Hiroyuki wrote:
Hi USB serial experts,
I am trying to support ZTE 403ZT modem by linux serial driver.
Currently, option driver can not be used for the modem, because USB Class Code
of the modem does not match.
Linux driver has 0xff as USB Class Code for the modem
On 2016-09-13 12:47, Felipe Balbi wrote:
"Steven J. Hill" writes:
On 09/12/2016 02:18 PM, Felipe Balbi wrote:
Please give this a shot. Patches are still RFT
because, well, they need testing. Note also that I
haven't, yet, added a binding documentation for your
compatible flag. I'll do that o
On 2016-11-16 02:13, 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
#define DLINK_PRODUCT_DWM_
On 2016-11-16 03:20, Giuseppe Lippolis wrote:
Signed-off-by: Giuseppe Lippolis
---
Adding support for 3G modem DWR-158 from Dlink (I found it embedded in the
DWR-512).
---
--- drivers/usb/serial/option.c.orig2016-11-15 21:05:16.987504020 +0100
+++ drivers/usb/serial/option.c 2016-11-15 21:0
On 2016-11-16 15:53, Oliver Neukum wrote:
On Wed, 2016-11-16 at 10:22 +0700, Lars Melin wrote:
On 2016-11-16 03:20, Giuseppe Lippolis wrote:
Signed-off-by: Giuseppe Lippolis
---
Adding support for 3G modem DWR-158 from Dlink (I found it embedded in the
DWR-512).
---
--- drivers/usb/serial
On 2016-11-17 01:35, Dan Williams wrote:
Also, is it really a D-Link DWM-158? That appears to be a USB dongle-
type device, while what's in the DWR-512 is a PCI-E minicard that looks
like a ZTE MF210, from the FCC pictures.
DWR-512A1 uses the ZTE MF210 module while DWR-512B1 uses the D-Link
On 2016-11-17 03:57, Oliver Neukum wrote:
On Wed, 2016-11-16 at 11:49 -0600, Dan Williams wrote:
This will make option grab all the ports, as shown by your dmesg
output. But USB interfaces 0 and 1 are actually cdc-ether and should
*not* be grabbed by option.
You want to limit option to grabbin
Seems it follows the layout given by the windows drivers, no special
Quectel layout.
MI_00 Qualcomm HS-USB Diagnostics 9003
MI_01 Qualcomm HS-USB NMEA 9003
MI_02 Qualcomm HS-USB AT Port 9003
MI_03 Qualcomm HS-USB Modem 9003
MI_04 Qualcomm Wireless HS-USB Ethernet Adapter 9003
wbr
/Lars
--
T
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 module "cdc_acm" recognizes it as CDC ACM device, creates a
device /dev/ttyACM*
On 2016-01-04 13:43, Oliver Neukum wrote:
On Mon, 2016-01-04 at 12:32 +0700, Lars Melin wrote:
K
04e8:6601 is also used for Samsung SCH-U209 CDMA modem so can not be
ignored.
04e8:685d is an update mode id so it can be ignored by cdc-acm.
04e8:68c3 does not look like update mode, it has cdc
On 2016-01-20 21:05, Jan Werner wrote:
Hi,
just wanted to let you know that we are using this command:
echo "2357 9000" > /sys/bus/usb-serial/drivers/generic/new_id
to add support for the TP-Link MA260 3G dongle on openwrt.
Why do you do that? It is supported in the option serial driver.
b
On 2016-02-10 04:52, Dimitrije Muzur wrote:
This happens every time i connect Lc Power LC-25U3-7W (it has asmedia
1053e chip inside) external enclosure with Seagate ST500LT0 12-9WS142
disk inside. Everything works perfectly when connected to USB 2.0
port but when its connected to usb 3.0 i get r
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 detected.
One of them is likely a QCDM port if this is really a Qualcomm based
device. The other m
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:
cfg #1
MI_00 HP Mobile Connect - PC UI Interface
MI_01 HP Mobile Connect - Application Interface
MI_02 HP Mobile Connect
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. Serial doesn't
necessarily imply AT commands...
I found the FCC ID for the de
On 2016-07-19 13:40, Kristian Evensen wrote:
I guess I can match on the VID/PID in usbnet, but won't it be cleaner
to add a new bind() function (in cdc_ether) which matches the two PIDs
and leave usbnet as is? Or am I misunderstanding how to add this
functionality to usbnet?
Matching on the u
On 2016-08-17 21:07, Binyamin Sharet wrote:
The issue was found on raspbian with kernel 4.4.6, and was not found on
ubuntu 16.04 with mainline kernel 4.8-rc2, I don't have much experience
with compiling kernels, so it will take me some time to build mainline
kernel for the raspberry pi.
Rasp
On 2016-03-14 11:31, bruce m beach wrote:
Hello Greg
I believe I can change the Device descriptors in firmware, upload the new
firmware and reboot the stick but wouldn't the usb subsystem have the old
device descriptor from the previous hotplug/system boot?
Nope, the kernel reads the descrip
On 2016-05-02 20:43, gre...@linuxfoundation.org wrote:
On Mon, May 02, 2016 at 09:22:57AM +0300, Felipe Balbi wrote:
Hi,
刘磊 writes:
dear linuxfoundation:
I am liulei come from ZTEMT. We need add some device ID to linux kernel,
We need some help from yours.
Looking forward to you reply
On 2016-05-03 14:48, Susmita/Rajib Bandopadhyay wrote:
Dear Sirs,
I had already tried
$ mkdir /media/sim
$ sudo mount /dev/sdc /media/sim
But this doesn't work, as I don't know the filesystem of the card.
Your reader is a TF/SD/MMC card reader from what I can see, it reads
various types of mem
On 2016-05-03 18:06, Susmita/Rajib Bandopadhyay wrote:
Since I don't have a winDoze system I can't use the software.
This list handles linux usb drivers, ie internal linux software.
Userland software for talking to your device should be provided by the mfgr.
You are jumping to big conclusion
On 2017-03-25 01:58, Bin Liu wrote:
On Wed, Mar 15, 2017 at 09:08:01AM -0500, Moreno Bartalucci wrote:
With usb-musb port in host mode, when the device
is disconnected, either logically (because of a mode switch) or
physically (by pulling the cable), the USB port should keep
suppling VBUS, with
On 2013-11-27 04:22, Thomas Schäfer wrote:
Hi,
I have it already mentioned somewhere. Sorry for duplicates.
The Huawei E5776
(normal use, classic IPv4, hilink mode (with webinterface and RFC1918 IP-
config including NAT)
worked well with 3.12 and before, but it doesn't work any more with 3.13.
On 2013-12-29 00:55, Greg KH wrote:
On Sat, Dec 28, 2013 at 02:13:08PM +, thomas.takacs.a...@gmail.com wrote:
Hi,
I've seen this message: tell linux-usb... to add your device to a proper device.
My USB modem is Alcatel One Touch X080C.
Please kindly add it or inform me how can I fix it.
Wha
On 2014-01-02 23:59, Dan Williams wrote:
On Sun, 2013-12-29 at 15:35 +0700, Lars Melin wrote:
On 2013-12-29 00:55, Greg KH wrote:
On Sat, Dec 28, 2013 at 02:13:08PM +, thomas.takacs.a...@gmail.com wrote:
Hi,
I've seen this message: tell linux-usb... to add your device to a proper d
On 2014-01-09 17:50, Linus Gasser wrote:
Hi list,
I'm trying to get an USB-modem running on a Smileplug, which is some
Arm7-device, using it with the kernel 3.12-6. As far as I can tell
it's an USB3-port. It works well with harddisks, but when I plug in
USB-modems, it always fails sooner or l
On 2014-01-09 00:17, Greg KH wrote:
On Wed, Jan 08, 2014 at 10:45:43PM +0700, Lars Melin wrote:
On 2014-01-02 23:59, Dan Williams wrote:
On Sun, 2013-12-29 at 15:35 +0700, Lars Melin wrote:
On 2013-12-29 00:55, Greg KH wrote:
On Sat, Dec 28, 2013 at 02:13:08PM +, thomas.takacs.a
On 2014-11-01 23:01, Matthias Klein wrote:
Add ID of the Peiker LTE NAD for legacy serial interface
Signed-off-by: Matthias Klein
---
drivers/usb/serial/option.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index d1a3f60..d7f10
On 2014-11-12 13:05, Lars Melin wrote:
On 2014-11-11 23:43, Sid Boyce wrote:
Results
---
root@sdrbox:~# lsusb
Bus 002 Device 004: ID 13fd:1840 Initio Corporation INIC-1608 SATA
bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 15ba:000c
On 2014-11-18 14:48, Jesse van der Berg wrote:
Hi,
uname -a
Linux Firen4ALL 3.17.3-031703-generic #201411141335 SMP Fri Nov 14
18:36:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Gives me the following in the syslog when I attach a Huawei E173 3G USB
modem to my computer. I don't know if it's rele
On 2014-12-30 04:18, anto1...@infinito.it wrote:
Hi
I send you this e-mail beacuse a read a warning message in kernel log
files.
I hope this can help...
[ 485.687201] usbserial_generic 1-1.1:1.2: The "generic" usb-serial
driver is only for testing and one-off prototypes.
[ 485.687206] usb
On 2014-03-21 11:33, Julio Araujo wrote:
Hello Bjørn,
I made the test like you suggested and I couldn't find any difference
between the printout for lsusb before and after the command.
What else I've been tried after read the page
http://www.draisberghof.de/usb_modeswitch/ was:
1 - For the fil
On 2014-04-14 23:26, Dan Williams wrote:
Some of these devices look like Android hotspots or phones, given the
"adb" blacklists in the patch, is that correct? But are any of them
Qualcomm Gobi-based WWAN cards? Do you have Windows .INF files for any
of these devices that we could look at to de
On 2014-05-18 21:50, Bjørn Mork wrote:
I could be wrong, but my impression is that the userspace API
preferences for network devices are
1. ethtool
2. sysfs
3. module param
..
99. ioctl
This is the primary reason why I was looking for someplace to put this
within the existing ethtool
On 2015-07-13 12:44, Dirk Behme wrote:
Add support for USB descriptor 0x1199, 0x68AB.
Signed-off-by: Dirk Behme
---
drivers/usb/serial/sierra.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/serial/sierra.c b/drivers/usb/serial/sierra.c
index 46179a0..4122e4f 100644
--- a
On 2015-07-24 16:30, Johan Hovold wrote:
On Fri, Jul 24, 2015 at 10:59:48AM +0200, Dirk Behme wrote:
On 24.07.2015 10:45, Johan Hovold wrote:
On Fri, Jul 24, 2015 at 10:17:24AM +0200, Dirk Behme wrote:
On 23.07.2015 19:26, Johan Hovold wrote:
This is probably the right driver, but I'm confu
On 2015-07-24 16:30, Johan Hovold wrote:
On Fri, Jul 24, 2015 at 10:59:48AM +0200, Dirk Behme wrote:
On 24.07.2015 10:45, Johan Hovold wrote:
On Fri, Jul 24, 2015 at 10:17:24AM +0200, Dirk Behme wrote:
On 23.07.2015 19:26, Johan Hovold wrote:
This is probably the right driver, but I'm confu
On 2015-08-02 19:00, Matthijs Kooijman wrote:
CustomWare uses the FTDI VID with custom PIDs for their ShipModul MiniPlex
products.
Signed-off-by: Matthijs Kooijman
---
drivers/usb/serial/ftdi_sio.c | 4
drivers/usb/serial/ftdi_sio_ids.h | 8
2 files changed, 12 insertions(
On 2015-08-03 00:07, Matthijs Kooijman wrote:
Hi Lars,
thanks for your feedback.
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2WI_PID) },
+ { USB_DEV
On 2015-08-15 11:41, Chase Metzger wrote:
Removed some checkpatch.pl warnings saying there was an unwanted space between
function names and their arguments.
Signed-off-by: Chase Metzger
---
drivers/usb/core/hub.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --
On 2014-09-24 13:48, Heiko Schocher wrote:
use the values for RNDIS over Ethernet as defined in
http://www.usb.org/developers/defined_class
(search for RDNIS):
- baseclass: 0xef (miscellaneous)
- subclass: 0x04
- protocol: 0x01
That is usb class, it is not the same thing as communication devic
On 2014-09-24 20:12, Heiko Schocher wrote:
Hello Lars,
Am 24.09.2014 14:25, schrieb Lars Melin:
On 2014-09-24 13:48, Heiko Schocher wrote:
use the values for RNDIS over Ethernet as defined in
http://www.usb.org/developers/defined_class
(search for RDNIS):
- baseclass: 0xef (miscellaneous
On 2014-09-29 19:11, Heiko Schocher wrote:
Hello Lars,
sorry for my late answer ...
Am 24.09.2014 16:22, schrieb Lars Melin:
On 2014-09-24 20:12, Heiko Schocher wrote:
Hello Lars,
Am 24.09.2014 14:25, schrieb Lars Melin:
On 2014-09-24 13:48, Heiko Schocher wrote:
use the values for RNDIS
On 2014-10-09 02:23, Adel Gadllah wrote:
Yet another device affected by this.
Tested-by: Kevin Fenzi
Signed-off-by: Adel Gadllah
---
drivers/usb/core/quirks.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 92125f9..cbbe701
On 2014-10-11 21:20, Greg KH wrote:
On Sat, Oct 11, 2014 at 03:49:43PM +0200, Philip Munksgaard wrote:
Fix a style issue
Signed-off-by: Philip Munksgaard
---
drivers/usb/serial/option.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/serial/option.c b/drivers
On 2014-10-11 23:02, Jonas Brunsgaard wrote:
Signed-off-by: Jonas Brunsgaard
---
drivers/usb/atm/ueagle-atm.c | 95
1 file changed, 42 insertions(+), 53 deletions(-)
diff --git a/drivers/usb/atm/ueagle-atm.c b/drivers/usb/atm/ueagle-atm.c
index 5a
On 2014-10-12 00:28, Jonas Brunsgaard wrote:
Could you be more specific, what is it you dislike? After this patch
the checkpatch script only come up with a couple of warnings, all due
to the line length limit, and these warnings are all acceppable as
they improve the ability to grep for user read
On 2014-07-02 02:01, Bernd Wachter wrote:
There's a new version of the Telewell 4G modem working with, but not
recognized by this driver.
Signed-off-by: Bernd Wachter
---
--- linux-3.15.3/drivers/net/usb/qmi_wwan.c.orig2014-07-01
21:31:07.0 +0300
+++ linux-3.15.3/drivers/net/us
On 2014-07-04 20:26, Bjørn Mork wrote:
Oliver Neukum writes:
On Thu, 2014-07-03 at 18:48 +0530, arun wrote:
Bus 001 Device 031: ID 2001:7d01 D-Link Corp.
The verbose output text file is attached.
2 things i would like to mention:
- As soon as it is inserted , it is 2001:a706. But after somet
On 2014-07-07 21:37, loody wrote:
hi Bryn:
2014-07-07 17:20 GMT+08:00 Bryn M. Reeves :
On Sun, Jul 06, 2014 at 01:18:03AM +0800, loody wrote:
hi all:
we met a USB Hard Disk that will go to suspend if host stop
sending scsi command over 5mins.
To save the IO, kernel will keep the file
On 2014-07-07 22:39, loody wrote:
hi David:
2014-07-07 23:06 GMT+08:00 David Laight :
From: Lars Melin
...
sgread is not included in BusyBox but you should have "touch".
Create a dummy file on the disk and let cron touch it every 4 minutes.
You don't need 'touch' a s
On 2014-07-20 03:21, Greg KH wrote:
On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
and dmesg are flooded with constant messages
option1 ttyUSB0: option_instat_callback: error -2
The device still work
On 2014-07-20 11:10, Greg KH wrote:
On Sun, Jul 20, 2014 at 10:43:44AM +0700, Lars Melin wrote:
On 2014-07-20 03:21, Greg KH wrote:
On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
and dmesg are
On 2014-07-23 04:17, Dan Williams wrote:
On Tue, 2014-07-22 at 14:02 +, Stanescu Victor wrote:
Hello,
This device works perfectly with usbserial generic, loaded with forced
vendor/product parameters. Can you please add it to the proper driver?
T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=
On 2014-07-24 16:07, Antonio wrote:
Hi!
When using a ZTE usb modem (that works correctly) I found a "please report the
device ID to the Linux USB developers!" message in the /var/log/syslog file of
a computer running Kubuntu 14.04.
The command "uname -a" answers
Linux laptop 3.13.0-32-gene
On 2014-07-25 00:50, Antonio wrote:
Hi!
[...] will probably fix your problem
Thank you for being kind. As far as I can tell, the modem is working
correctly, I wrote to this list because I saw a
"usb_modeswitch: please report the device ID to the Linux USB developers!"
message and I thought t
On 2014-08-06 07:20, Brennan Ashton wrote:
Both devices have the same VID and PID.
This patch has been tested on both of these modem versions.
Signed-off-by: Brennan Ashton
---
drivers/usb/serial/option.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/usb/serial/option.c b
On 2015-03-24 17:20, Oliver Neukum wrote:
On Mon, 2015-03-23 at 21:11 +0200, Sami Farin wrote:
I tried reverting f46ad73ac696 in 4.0.0-rc5, did not help. Have to
reboot first into 3.18.9.
This happens:
[ 2765.268081] usb 2-1.4.4: USB disconnect, device number 16
[ 2777.209388] usb 2-1.4.4: new
On 2015-03-24 18:26, Sami Farin wrote:
On Tue, Mar 24, 2015 at 18:02:51 +0700, Lars Melin wrote:
On 2015-03-24 17:20, Oliver Neukum wrote:
...
[ 2777.325282] scsi host37: usb-storage 2-1.4.4:1.0
[ 2777.903039] usb 2-1.4.4: usbfs: interface 0 claimed by usb-storage
while 'usb_modeswitch&
On 2015-03-24 18:57, Sami Farin wrote:
On Tue, Mar 24, 2015 at 12:29:19 +0100, Oliver Neukum wrote:
On Tue, 2015-03-24 at 13:26 +0200, Sami Farin wrote:
...
4.0.0-rc5+ does not switch to "old Win" mode even if I blacklist usb_storage,
have to reboot to 3.18.9.
Why?
Good question. Please post
On 2015-06-10 06:20, Peter Stuge wrote:
Joe wrote:
I'm considering the idea of posting without that tag for now,
so that you can evaluate/add my patch as soon as possible.
However... will it be possible, in case, to correct my previous
subbmitted patch to add the Suggested-by tag?
No, that's no
On 2015-06-10 15:59, Joe wrote:
Lars Melin wrote:
If these hints to "Joe" justifies a Suggested-by then he can add me,
info is in this mails header.
I do however not agree to the place where "Joe" has stuck it into the
usb_device_id list, it should not be among
the other
On 2015-07-01 19:24, Oliver Neukum wrote:
This device automatically switches itself to another mode (0x1405)
unless the specific access pattern of Windows is followed in its
initial mode. That makes a dirty unmount of the internal storage
devices inevitable if they are mounted. So the devices sho
On 2015-07-01 22:41, Matthew Dharm wrote:
On Wed, Jul 1, 2015 at 8:36 AM, Lars Melin wrote:
On 2015-07-01 19:24, Oliver Neukum wrote:
This device automatically switches itself to another mode (0x1405)
unless the specific access pattern of Windows is followed in its
initial mode. That makes a
On 2015-07-02 20:01, Oliver Neukum wrote:
On Thu, 2015-07-02 at 14:43 +0200, Oliver Neukum wrote:
On Wed, 2015-07-01 at 22:50 +0700, Lars Melin wrote:
Then I would like to see an lsusb listing for 19d2:1225 with an SD-card
interface, I have only seen 19d2:1225 with a single storage interface
VICE, USB_PR_DEVICE, NULL,
+ US_FL_SINGLE_LUN ),
+
/* Reported by Sven Geggus
* This encrypted pen drive returns bogus data for the initial READ(10).
*/
Looks good now
Reviewed-by: Lars Melin
rgds
Lars
--
To unsubscribe from this list: send the line "unsubscribe linux
On 2015-10-24 22:44, Michele Baldessari wrote:
The Xin-Mo Dual Arcade controller (16c0:05e1) needs this quirk in order
to have the two distinct joysticks working.
Before the change:
$ jstest /dev/input/js0
Joystick (Xin-Mo Xin-Mo Dual Arcade) has 2 axes (X, Y)
...
$ jstest /dev/input/js1
jstest:
On 2015-03-05 10:00, Rick Farina wrote:
On 03/04/15 13:01, Greg KH wrote:
And again, a kernel patch is the real way to fix it for everyone.
Okay, got a lot of things figured out and have everything working now.
Glad I spent the extra time because I found some neat things on the device.
I've m
On 2015-03-05 11:53, Lars Melin wrote:
There is already support in option for a few other Huawei dongles with
the same type of interface attributes and that is the right place
for adding 12d1:1556
Here is the relevant part of option.c :
645{ USB_DEVICE_AND_INTERFACE_INFO
On 7/16/2019 18:17, Johan Hovold wrote:
snip
Ok, thanks. Do you have any idea what all those vendor interface are
for? Some of the other D-Link entries blacklist a speech and debug port
for example.
We can always do that later if we need to, but perhaps you or someone
already know (also adding
On 7/17/2019 12:40, Yoshiaki Okamoto wrote:
This patch adds support for MF871A USB modem (aka Speed USB STICK U03)
to option driver. This modem is manufactured by ZTE corporation, and
sold by KDDI.
Interface layout:
0: AT
1: MODEM
usb-devices output:
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev
On 7/18/2019 21:46, OKAMOTO Yoshiaki wrote:
Hi Lars,
Please do a full test of the interface attributes (Class/SubClass/Proto)
whenever possible, this could be helpful in case the mfgr makes a device
with different interface layout but re-uses an already used vid:pid.
What should we do specif
On 7/23/2019 21:49, Tony Lindgren wrote:
+#define MOTOROLA_VENDOR_ID 0x22b8
+#define MOTOROLA_PRODUCT_MDM6600 0x2a70
+#define MOTOROLA_PRODUCT_MDM9600 0x2e0a
+#define MOTOROLA_PRODUCT_MDM_RAM_DL0x4281
+#define MOTOROLA_PRODUCT_MDM_QC_DL
On 4/23/2018 14:03, Giuseppe Lippolis wrote:
The dwm-158 interface 4 and 5 doesn't answer to the AT commands
and doesn't appears a option interface.
Tested on openwrt distribution (kernel 4.14 using the old blacklist
definitions).
Signed-off-by: Giuseppe Lippolis
---
drivers/usb/serial/option
On 4/23/2018 23:54, Dan Williams wrote:
MI_00 D-Link Mobile Broadband Device (cdc_ether)
MI_02 D-Link HSPA+DataCard Diagnostics Interface (also ppp m
MI_03 D-Link HSPA+DataCard NMEA Device
MI_04 D-Link HSPA+DataCard Speech Port
Any idea what format this port speaks? Some Huawei Qualcomm-base
On 4/26/2018 14:09, Johan Hovold wrote:
On Thu, Apr 26, 2018 at 02:28:31PM +0800, SZ Lin (林上智) wrote:
This patch adds support for ublox R410M PID 0x90b2 USB modem to option
driver, this module supports LTE Cat M1 / NB1.
Interface layout:
0: QCDM/DIAG
1: ADB
2: AT
3: RMNET
Signed-off-by: SZ Lin
On 4/26/2018 18:39, Lars Melin wrote:
On 4/26/2018 18:19, Bjørn Mork wrote:
Anyway, Qualcomm based designs are definitely handled by both drivers.
Using qcserial only makes sense if the interface layout matches one of
the defined shared schemes, which currently are:
QCSERIAL_G2K = 0
On 4/26/2018 18:19, Bjørn Mork wrote:
Anyway, Qualcomm based designs are definitely handled by both drivers.
Using qcserial only makes sense if the interface layout matches one of
the defined shared schemes, which currently are:
QCSERIAL_G2K = 0, /* Gobi 2000 */
QCSERIAL_G1
On 4/26/2018 23:12, Johan Hovold wrote:
On Thu, Apr 26, 2018 at 06:40:46PM +0700, Lars Melin wrote:
On 4/26/2018 18:39, Lars Melin wrote:
On 4/26/2018 18:19, Bjørn Mork wrote:
Anyway, Qualcomm based designs are definitely handled by both drivers.
Using qcserial only makes sense if the
On 11/20/2017 16:27, Shrirang Bagul wrote:
Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74
series modems which will by default boot with vid 0x413c and pid's
0x81cf, 0x81d0, 0x81d1,0x81d2. Along with qcserial, these modems support
qmi_wwan on the usb interface #12.
Signed-off
On 12/13/2017 14:18, martin.er...@centrum.cz wrote:
Dear linux development,
please to add device to a proper driver. I wrote this requirement according log
list message.
My USB modem is D-link DWM-222
Vendor 3G Standard Default Id Modem Id User Modem
Storage Diag
On 2017-04-18 02:06, Anders Eriksson wrote:
[1.056684] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
The pesky dwc_otg driver is the reason for your problem, it is not
part of the official 4.9 kernel.
It was replaced by dwc2 some two years ago.
/Lars
--
To unsubscribe from this list:
On 2017-06-12 15:46, Teemu Likonen wrote:
Johan Hovold [2017-06-12 10:24:11+02] wrote:
What is the output of "lsusb -v" for this device?
Interface usage:
MI_00 Wireless Diagnostics
MI_01 Wireless Modem
MI_02 Wireless Application
MI_03 Wireless Data Device Ethernet Adapter (qmi_wwan)
MI_04
On 2017-06-12 16:50, Bjørn Mork wrote:
Johan Hovold writes:
Add device-id entry for the Telewell TW-3G HSPA+ modem, which uses the
Longcheer vendor id.
Reported-by: Teemu Likonen
Cc: stable
Signed-off-by: Johan Hovold
---
drivers/usb/serial/option.c | 4
1 file changed, 4 insertion
On 2017-06-12 17:37, Bjørn Mork wrote:
Lars Melin writes:
1c9e:9803 can be added, the other ones may be reserved id's for
products that never reached the market.
Out of curiosity: How do you know these things?
Thanks for very valuable information. Our lists of supported devices
are
On 2017-07-03 15:10, Johan Hovold wrote:
On Thu, Jun 29, 2017 at 07:41:24PM +0200, Sebastian wrote:
Sorry for the long delay, Johan.
2017-06-01 9:20 GMT+02:00 Johan Hovold :
[ +CC: media list ]
On Wed, May 31, 2017 at 08:25:42PM +0200, Sebastian wrote:
What is the lsusb -v output for your de
On 2017-07-14 13:58, Linus Lüssing wrote:
---
$ dmesg
[...]
[166914.044029] usb 1-1.6.1: new full-speed USB device number 23 using dwc_otg
dwc_otg is not an official kernel driver, no support for it here.
/Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the b
On 8/9/2017 02:33, Bjørn Mork wrote:
The qmi_wwan part looks fine to me. But you
will need to split it in two patches since the two
drivers are parts of different subsystems.
The option driver use interface blacklists
instead of multiple match entries. You should
probably follow the same sty
On 9/10/2018 18:39, Kristian Evensen wrote:
Hi,
On Mon, Sep 10, 2018 at 12:30 PM Johan Hovold wrote:
Please provide the output of usb-devices (or lsusb -v) for both
"configurations". How do you update the configuration by the way?
The configuration is updated using a proprietary AT-command
(
On 9/11/2018 21:34, Kristian Evensen wrote:
On Tue, Sep 11, 2018 at 4:00 PM Lars Melin wrote:
My opinion is that the option and qmi-wwan drivers should support EP06
in the factory delivery configuration and not in a configuration the
user has selected with a Quectel proprietary AT cmd.
Can
On 9/12/2018 23:57, Kristian Evensen wrote:
On Wed, Sep 12, 2018 at 6:32 PM Lars Melin wrote:
You have chosen a platform which has limited usb resources and want to
solve that problem by adjusting the device driver?
No, you asked for a good reason for why disabling and not just
ignoring an
On 12/10/2018 06:21, Jörgen Storvist wrote:
Added USB serial option driver support for Fibocom NL668 series cellular module.
Reserved USB endpoints 4 and 5 for network interfaces.
Signed-off-by: Jörgen Storvist
drivers/usb/serial/option.c | 5 +
1 file changed, 5 insertions(+)
diff --gi
On 12/18/2018 22:19, Macpaul Lin wrote:
Hi all,
After double check the PID/VID officially used (registered) by Mediatek
Inc. The following VID/PID maps to the corresponding USB interface of
the firmware of cell phone.
VID:0x0e8d, PID:0x0003: Mediatek BROM.
VID:0x0e8d, PID:0x2000: Mediatek Prel
On 12/19/2018 00:48, Macpaul Lin wrote:
Hi Lars, Oliver, and Johan,
Well, it's about 1:30 a.m. here in Taiwan. I can do lsusb dump tomorrow
in Mediatek's office.
But there are a lot of tutorials about hacking and flash method of
customized firmware over the WWW. I can find one of the tutorial s
On 12/19/2018 10:16, Macpaul Lin wrote:
.
Here comes the verbose lsusb -v dump.
Bus 001 Device 003: ID 0e8d:0003 MediaTek Inc. MT6227 phone
[432/3160]
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass2 Communica
On 8/14/2019 22:59, Jonathan Bell wrote:
There is a bug when the dwc2 core receives USB data packets that are
between 1 and 4 bytes in length - 4 bytes are always written to memory
where the non-packet bytes are garbage.
Which host controller driver, dwc2 or the out-of-tree dwc_otg driver?
Tha
On 9/18/2019 04:38, JH wrote:
..
That was always my thought until I tried kernel 5.1 under the same
platform (nothing changed except the kernel version), the kernel 5.1
can connect to the 4G modem, I could not tell the hardware engineer if
it was hardware problem where kernel 5.1 can connect
97 matches
Mail list logo
