Re: umodeswitch

[manu%netbsd.org@localhost (Emmanuel Dreyfus)]

Martin Husemann <martin%duskware.de@localhost> wrote:

> How did you add the ID?

Like in patch below. I also tried the same apporach as NOVATEL2 case in
umodeswitch_attach, with no better outcome.

I am a bit surprised for D-Link DWM222 since Linux's usb_modeswitch
supports it with no special handling.

--- umodeswitch.c.orig  2021-04-09 20:51:58.812087597 +0200
+++ umodeswitch.c       2021-04-09 17:57:17.853298685 +0200
@@ -420,8 +421,9 @@
                break;
 
        case USB_VENDOR_ZTE:
                switch (uaa->uaa_product){
+               case USB_PRODUCT_ZTE_MF112: 
                case USB_PRODUCT_ZTE_INSTALLER:
                case USB_PRODUCT_ZTE_MF820D_INSTALLER:
                        (void)u3g_bulk_ata_eject(uaa->uaa_device);
                        (void)u3g_bulk_scsi_eject(uaa->uaa_device);
@@ -439,8 +441,9 @@
        case USB_VENDOR_DLINK:
                switch (uaa->uaa_product) {
                case USB_PRODUCT_DLINK_DWM157E_CD:
                case USB_PRODUCT_DLINK_DWM157_CD:
+               case USB_PRODUCT_DLINK_DWM222_CD:
                        (void)u3g_bulk_ata_eject(uaa->uaa_device);
                        (void)u3g_bulk_scsi_eject(uaa->uaa_device);
                        return UMATCH_HIGHEST;
                default: 

> If it does not do that, either the command was wrong, or it does not
> like moving to configured state (see the NOVATEL2 case in umodeswitch_attach).
> 
> Martin


-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost