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.c | 3 ++-
1 file changed, 2 insert
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.c | 3 ++-
1 file changed, 2 insert
uftrag von Johan Hovold
> Gesendet: Freitag, 23. März 2018 10:14
> An: Giuseppe Lippolis
> Cc: linux-usb@vger.kernel.org; jhov...@gmail.com
> Betreff: Re: [PATCH v2] net-usb: add qmi_wwan if on lte modem wistron
> neweb d18q1
>
> On Fri, Mar 23, 2018 at 09:55:38AM +0100, Giusepp
Johan thanks for your advices.
Currently I don't have the opportunity to test the patch on a linux-next system.
Therefore I will apply now the patch only for the qmi_wwan IF only and I will
wait the option backport/update on my system to send the option patch.
For this device the option IF is an
on openwrt distribution
Signed-off-by: Giuseppe Lippolis
---
drivers/net/usb/qmi_wwan.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index 5894e3c..b1f9b0a 100644
--- a/drivers/net/usb/qmi_wwan.c
+++ b/drivers/net/usb/qmi_wwa
wer Management (LPM) Supported
Device Status: 0x
(Bus Powered)
The patch has been tested using the openwrt distribution
Signed-off-by: Giuseppe Lippolis
---
drivers/net/usb/qmi_wwan.c | 3 +++
drivers/usb/serial/option.c | 11 +++
2 files changed, 14 insertions(+)
diff --gi
> sendsetup is to prevent the driver from sending a specific USB control
> message for setting up serial parameters, which some devices ignore and
> cause the driver to stall.
>
> reserved is what you're looking for. This one tells option not to bind to the
> given USB interfaces.
>
> So for exa
> The option driver use interface blacklists instead of multiple match entries.
> You should probably follow the same style there. But this is up to Johan...
Can I ask what ist he difference between .sendsetup and .reserved and how to
use the bitmask in drivers/usb/serial/option.c ?
Thanks,
Bye.
> But we already have many Sierra devices with 2 QMI interfaces (the 3rd one
> is documented and verified non-functional for unknown reasons). And these
> tend to come with multiple OEM device IDs. So a whitelist method could
> reduce the number of matching entries considerably. Feel free to subm
Hi all,
I'm working to port OpenWRT/LEDE on a new router with embedded usb LTE
modem.
The modem have 3 qmi_wwan interfaces and 2 option.
I would like to prepare the patch, but before I would like to know if using
the QMI_FIXED_INTF macro is the best way to identify the interface or if
there is a b
Dear Johan,
Thanks for the tips.
Here is the patch.
Bye.
---
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 9894e34..386b687 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
> Any chance you can resend this in a format we can apply it in (tabs
properly
> used, no line-wrap, correct signed-off-by, good subject and changelog
text,
> etc.)?
Adding registration for 3G modem DWM-158 in usb-serial-option
Signed-off-by: Giuseppe Lippolis
diff --git a/drivers/u
I all,
This patch will add the 3G modem dwm-158 found inside the DWR-512 from
Dlink.
The modem have 2 cdc_ether interface and 4 usb-serial.
I tested the patch in the current lede system and compiled on the latest
linux tree.
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
i
Dear All,
> If possible you want to tell the option driver which interfaces to
> bind to (white-listing) rather than specifying which not to bind to
> (black-listing). The latter typically means probing all interfaces,
> checking the black list, and then bailing out for unsupported
> interface
ther
Interface and only gets the serial ports?
Thanks,
Bye.
> -Ursprüngliche Nachricht-
> Von: Oliver Neukum [mailto:oneu...@suse.com]
> Gesendet: Mittwoch, 16. November 2016 21:57
> An: Dan Williams
> Cc: Giuseppe Lippolis ; linux-usb@vger.kernel.org
> Betreff: Re: add
Dear All,
thanks for the very interesting discussion.
> > 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 grabbing bInterfaceClass=255 to m
> Your email client ate the tabs and spit out spaces and line-wrapped the
> patch, making it impossible to apply.
>
> Also, you need to make it against the latest kernel tree, 4.4 is really
old.
>
> And finally, there is no good subject: line, or description of the patch,
or a
> signed-off-by: li
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:08:27.722378924 +0100
@@ -306,6 +306,9 @@ static
) },
bye
> -Ursprüngliche Nachricht-
> Von: Greg KH [mailto:gre...@linuxfoundation.org]
> Gesendet: Dienstag, 15. November 2016 20:19
> An: Giuseppe Lippolis
> Cc: linux-usb@vger.kernel.org
> Betreff: Re: add usb option device
>
> On Tue, Nov 15, 2016 at 08
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_652 0x3e04
#define DLI
20 matches
Mail list logo
