[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

Hans Petter Selasky  changed:

   What|Removed |Added

   Assignee|u...@freebsd.org |hsela...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

Hans Petter Selasky  changed:

   What|Removed |Added

 Status|New |In Progress

--- Comment #8 from Hans Petter Selasky  ---
OK, I'll try to get the patch upstreamed.

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #7 from Martin Birgmeier  ---
After deleting this line cdce.ko does not attach to the device anymore. RNDIS
still attaches and works o.k.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #6 from Hans Petter Selasky  ---
Did you try to revert the mentioned patch?

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #5 from Martin Birgmeier  ---
By whom - given the "we" in comment #3 and the assignee being "freebsd-usb
(Nobody)"? ;-)

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #4 from Hans Petter Selasky  ---
Ping - any updates?

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #3 from Hans Petter Selasky  ---
Hi,

It is because of these values that CDCE attaches:

  idVendor = 0x0525 
  idProduct = 0xa4a2 

I think the vendor forgot to patch/update those values.

Probably we can revert this patch from 2005:

https://svnweb.freebsd.org/base/head/sys/dev/usb/if_cdce.c?r1=150700=150701=171005;

-_HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

Martin Birgmeier  changed:

   What|Removed |Added

 Attachment #223338|text/x-log  |text/plain
  mime type||

--- Comment #2 from Martin Birgmeier  ---
Created attachment 223338
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223338=edit
part of devd.log showing RNDIS gadget attach and detach

For additional info attached is a part of /var/log/devd.log showing the actions
taken when attaching and (5 minutes later) detaching the device.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

--- Comment #1 from Martin Birgmeier  ---
Some additional info:

- On attach, devd loads both the if_urndis and the if_cdce drivers. This is
also strange given that only configuration 0 (RNDIS) should be active.
- When attached, it is possible to use the ue interface attached to if_urndis,
but not the one attached to if_cdce.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 254345] cdce erroneously attaches to a combined RNDIS/CDCE Ethernet gadget

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254345

Bug ID: 254345
   Summary: cdce erroneously attaches to a combined RNDIS/CDCE
Ethernet gadget
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: usb
  Assignee: u...@freebsd.org
  Reporter: d8zne...@aon.at

Created attachment 223335
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223335=edit
files mentioned in the bug report

Scenario:
- Raspberry Pi B+
- FreeBSD main at 51dfae383bf6298af9e6d816a78b92b6f34d68be
- (Physically) attaching a combined RNDIS/CDCE Ethernet gadget: configuration 0
supports RNDIS, configuration 1 supports CDCE (see the attached output of
"usbconfig dump_all_desc"
- The current configuration is 0, see the attached output of "usbconfig
dump_curr_config_desc"
- devd with a default configuration plus a special configuration for a Huawei
4G modem is running; the special configuration matches this device (although it
really should not, but this is not the point of this PR); the special devd
configuration file is attached ("e3372.conf")

Result:
- Two ue interfaces are created, one attached to interface 0 of the RNDIS
device, the other to interface 1; see the attached output of "devinfo -rv"

Expected result:
- Since configuration 0 is active, only one network interface for the RNDIS
device should be created; this network interface must make use of the two USB
interfaces (0, 1, see above) of USB configuration 0 of the device, see
https://docs.microsoft.com/de-at/windows-hardware/drivers/network/overview
- The CDCE driver should not attach at all to this device as long as it is in
USB configuration 0.

Notes:
- I am not an expert here so my analysis may be wrong. :-)
- It is important not to mix the notions of "USB interface" and "network
interface" when checking this PR.
- There is a major issue with devd and the ue USB Ethernet interfaces because
the available information does not allow devd to determine which device it is
really dealing with. In this case, with e3372.conf a DHCP client is started on
all ue devices; but this is useless for the Ethernet gadget of this PR because
that needs to have a fixed IP address assigned which is impossible to achieve
with devd rules as long as the real E3372 offers a DHCP service.
- FreeBSD needs a way to distinguish interfaces by some hardware ID; most
likely the best way would be to create the device as ue-.
But this is not the main issue of this bug report; this bug report is about
CDCE erroneously attaching to the data interface of a USB RNDIS device.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 247439] ue(4): Rename to match it's driver (cdce or uether)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247439

Hans Petter Selasky  changed:

   What|Removed |Added

 CC||hsela...@freebsd.org

--- Comment #1 from Hans Petter Selasky  ---
Hi,

The line you are looking for is:

if_initname(ifp, "ue", ue->ue_unit);

I'm not sure if it will solve anything to have different names for the USB
ethernet adapters. They are currently named the same because these are USB
devices, and so it is easy to recognize them.

If you want to map ueX to a given USB port, you need to look at the "sysctl -a"
output. There is something called %parent and %location which will help you. 

Check this out:

net.ue.0.%parent: axge0

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 247439] ue(4): Rename to match it's driver (cdce or uether)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247439

Kubilay Kocak  changed:

   What|Removed |Added

 CC||n...@freebsd.org
   Keywords||needs-patch, needs-qa
Summary|network interface "ue"'s|ue(4): Rename to match it's
   |name should be same as it's |driver (cdce or uether)
   |driver (cdce or uether) |
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 247439] network interface "ue"'s name should be same as it's driver (cdce or uether)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247439

Bug ID: 247439
   Summary: network interface "ue"'s name should be same as it's
    driver (cdce or uether)
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: usb
  Assignee: u...@freebsd.org
  Reporter: t.eichsta...@gmx.net

Dear programmer,

Usually network interface names are _the same_ (no abbr.) as their resp.
driver.  The 'ue' interface should follow this convention, too.

This interface appears when a wireless modem is attached to the system.  I
/guess/ it's the bridge supplied by cdce(4), but since 'ue' could also be meant
as abbreviation for uether(4), I'm not quite shure... (and uether(4) has no man
page)

It's easy to avoid such confusion by simply following the convention. To save
two or three keystrokes is a void (pardon - silly) plea.  I do not mean this in
an offensive way.

IMHO the fix should be that 1. the IF is named "uetherN" 2. when cdce(4) takes
it, renames it to "cdceN".  I tried to fix it myself, but gave up after an hour
reading through the src (found a module_map[] in sbin/ifconfig.c, does it
belong in there?).  When you fix it, it takes you 10 minutes.

THX

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 243999] cdce does not find Lenovo onelink+ dock

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243999

Hans Petter Selasky  changed:

   What|Removed |Added

 CC||hsela...@freebsd.org

--- Comment #1 from Hans Petter Selasky  ---
Try:

usbdump -d 0.5 dump_curr_config_desc dump_device_desc

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 243999] cdce does not find Lenovo onelink+ dock

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243999

Mark Linimon  changed:

   What|Removed |Added

  Component|kern|usb
   Assignee|b...@freebsd.org|u...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

Jesper Schmitz Mouridsen  changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #11 from Jesper Schmitz Mouridsen  ---
(In reply to Bipin Chandra from comment #10)

It works on 12.1-RELEASE by kldunload if_cdce.ko, after the Zero has booted.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #49 from jeff  ---
I tried first on vm fresh install pf 2.3.5..load this driver on boot.no ue0
inteface..here's the dmesg

BIOS 640kB/261120kB available memory

FreeBSD/x86 bootstrap loader, Revision 1.1
(root@ce23-i386-builder, Tue Oct 24 04:52:46 CDT 2017)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x122025a data=0x84738c+0xd9688
syms=[0x4+0xf3aa0+0x4+0
   x16b822]
/boot/kernel/if_cdce.ko text=0x35e0 data=0x164+0x4 syms=[0x4+0x920+0x4+0x9ff]


.then I tried it again on vm fress install 10.3 , load this driver on boot..ue0
interface came up..

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #48 from Hans Petter Selasky  ---
Did you unload the if_cdce driver before installing new one?

Anything printed in dmesg?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #47 from jeff  ---
I patched and compiled cdce driver on 10.3 box..Then I attached the e3372 and
it was detected and ue0 interface came up..I copy if_cdce.ko to /boot/kernel
folder on pfsense 10.3 and add this this line if_cdce_load="YES" to
boot/loader.conf..but still same issue..no ue0 interface .. any ideas ??

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #46 from jeff  ---
I use vmware freebsd 10.3 and download sources.Can someone please guide me in
applying this patch and compiling it on 10.3

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #45 from jeff  ---
Do i need to apply this patch to u3g as well? after compilation , Can I load
patched u3g and cdc module on our pfsense 2.3.5??

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #44 from Hans Petter Selasky  ---
If the code compiles it should work for this case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

jeff  changed:

   What|Removed |Added

 CC||jefb...@gmail.com

--- Comment #43 from jeff  ---
Hi ,
  We have a Alix 2d13 i386 with pfsense 2.3.5 which is based on freebsd
10.3..netgate stop its support on nanobsd based on i386 so I cant upgrade it
anything newer than pfsense 2.3.5 freebsd 10.3..My problem is we want to use it
with 4g e3372 converted with stick firmware 21.300 (non hilink). When plug it
on my alix  here's dmesg:

ugen1.2:  at usbus1
u3g0:  on usbus1
u3g0: Found 2 ports

No ue0/cdc inteface came up..I tried it with vm pfsense 2.4.4 freebsd 11 and
modem was detected , I see ue0/cdc interface came up..
my 3372 modem has 0x12d1 Sub=03 Prot=16t . and I think there's no cdc module
for 0x12d1 Sub=03 Prot=16 on 10.3,

I just want to ask if I can compile this cdce driver for 10.3 and apply this
patch??Hope someone could help.I can donate for some beers,,

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

Mark Linimon  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

--- Comment #42 from Mark Linimon  ---
Committed 2018-03-19.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #41 from commit-h...@freebsd.org ---
A commit references this bug:

Author: eadler
Date: Mon Mar 19 04:03:55 UTC 2018
New revision: 331176
URL: https://svnweb.freebsd.org/changeset/base/331176

Log:
  MFC r328162:

  Improve support for USB based 3G/4G/5G dongles from Huawei.

  PR:   192345

Changes:
_U  stable/11/
  stable/11/sys/dev/usb/net/if_cdce.c
  stable/11/sys/dev/usb/serial/u3g.c
  stable/11/sys/dev/usb/serial/umodem.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #40 from Hans Petter Selasky  ---
Yes, I know. Because I think drivers should only have one probe success. The
approach with multiple probes returning a match, and then falling back to the
best, is not good. It will also confuse devd.

My question to you: Does my patch work or not?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|Closed  |In Progress

--- Comment #39 from rozhuk...@gmail.com ---
You re implement my first solution, U3G_HUAWEI_IS_CDC() = u3g_huawei_is_cdc()
is same.

My last patch does not need this function to work.
See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345#c28

We do not need compare device id~s, we need only one simple thing: call
usbd_set_parent_iface(uaa->device, i, uaa->info.bIfaceIndex);
only after some serial sub device is attached.

Current code call: usbd_set_parent_iface(uaa->device, i,
uaa->info.bIfaceIndex);
then try attach and if it fail then device still marked as "no need to driver
probe".

Also my patch on probe() fail return more proper code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

Hans Petter Selasky  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|In Progress |Closed

--- Comment #38 from Hans Petter Selasky  ---
Check if the submitted patch works for you.

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #37 from commit-h...@freebsd.org ---
A commit references this bug:

Author: hselasky
Date: Fri Jan 19 12:59:14 UTC 2018
New revision: 328162
URL: https://svnweb.freebsd.org/changeset/base/328162

Log:
  Improve support for USB based 3G/4G/5G dongles from Huawei.

  PR:   192345
  Sponsored by: Mellanox Technologies

Changes:
  head/sys/dev/usb/net/if_cdce.c
  head/sys/dev/usb/serial/u3g.c
  head/sys/dev/usb/serial/umodem.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #36 from Hans Petter Selasky  ---
Still on my todo. Has been very hectic.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #35 from Hans Petter Selasky  ---
OK. I see. I'll try to give your patch the needed attention this week.
Thanks for the reminder.

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #34 from rozhuk...@gmail.com ---
(In reply to Hans Petter Selasky from comment #33)

IMHO it is different problem, that user can fix by manual loading cdce or add
it to loader.conf[.local] or to kld_list in rc.conf[.local].
We can add cdce to u3g as required module or patch devd to load 2
modules/drivers. I prefer to change devd config :)

Half of patch is not huawei specific, it affect all other devices that handled
by u3g+cdce and that have serial interface before cdce interface.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #33 from Hans Petter Selasky  ---
Hi,

The patch looks OK, but I see a problem with /etc/devd/usb.conf, that the
widening of the matching and USB bus probe default might cause the wrong driver
to be loaded by devd ...

devd usually only expects one match when loading a driver.

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #32 from rozhuk...@gmail.com ---
ping

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Attachment #188484|0   |1
is obsolete||

--- Comment #31 from rozhuk...@gmail.com ---
Created attachment 188485
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188485=edit
use BUS_PROBE_DEFAULT for cdce

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Attachment #188479|0   |1
is obsolete||

--- Comment #30 from rozhuk...@gmail.com ---
Created attachment 188484
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188484=edit
move usbd_set_parent_iface() fixed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #27 from Hans Petter Selasky  ---
There is another way. You can set different probe priority too. I'm not sure
how well it is to mix these USB drivers together.

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #26 from rozhuk...@gmail.com ---
I think add to u3g module depend if_cdce, [export and] call cdce_probe to check
is device cdce is more proper way than playing with quirk.
u3g already cam handle ucom and add if_cdce handle is good way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #24 from rozhuk...@gmail.com ---
I see usb_quirk.c but not found how to add device Interfaces ID.
U3G_HUAWEI_IS_CDC() macro catch only specific device interfaces, that specified
in if_cdce, but I dont know how to add if_cdce probe/attach in u3g like this
done for ucom.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #23 from Hans Petter Selasky  ---
Hi,

The "U3G_HUAWEI_IS_CDC" macro should be converted into a new quirk in the
usb_quirk.c . Can you do that instead of adding specific code for this? Then
new ID's can easily be added later on.

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [cdce] patch for huawei 4G/LTE modems: E3272, E3372

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

Summary|[u3g] patch for huawei  |[u3g] [cdce] patch for
   |4G/LTE modems: E3272, E3372 |huawei 4G/LTE modems:
   ||E3272, E3372

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #10 from Bipin Chandra  ---
as per one of the members at pfsense i was told the below:

"It still concerns me that the device created is cdce0 and not urndis0. It
looks to me as though it's not even using the urndis driver"

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #9 from Bipin Chandra  ---
tried the patch but the behavior is still same

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #8 from Bipin Chandra  ---
(In reply to Hans Petter Selasky from comment #6)

i wont be able to test this patch because im using pfsense and im trying to
make this work with that and secondly im not a developer so its out of my
scope. Ill ask some1 on pfsense forum if they can give it a try

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #7 from Bipin Chandra  ---
(In reply to Hans Petter Selasky from comment #5)

usbconfig -d 0.2 dump_curr_config_desc

ugen0.2:  at usbus0,
cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)


 Configuration index 0

bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x004b
bNumInterfaces = 0x0002
bConfigurationValue = 0x0002
iConfiguration = 0x  
bmAttributes = 0x00c0
bMaxPower = 0x0001

Additional Descriptor

bLength = 0x08
bDescriptorType = 0x0b
bDescriptorSubType = 0x00
 RAW dump:
 0x00 | 0x08, 0x0b, 0x00, 0x02, 0x02, 0x06, 0x00, 0x06


Interface 0
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x
  bAlternateSetting = 0x
  bNumEndpoints = 0x0001
  bInterfaceClass = 0x0002  
  bInterfaceSubClass = 0x0002
  bInterfaceProtocol = 0x00ff
  iInterface = 0x0004  

  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x00
   RAW dump:
   0x00 | 0x05, 0x24, 0x00, 0x10, 0x01


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x01
   RAW dump:
   0x00 | 0x05, 0x24, 0x01, 0x00, 0x01


  Additional Descriptor

  bLength = 0x04
  bDescriptorType = 0x24
  bDescriptorSubType = 0x02
   RAW dump:
   0x00 | 0x04, 0x24, 0x02, 0x00


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x06
   RAW dump:
   0x00 | 0x05, 0x24, 0x06, 0x00, 0x01


 Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0082  
bmAttributes = 0x0003  
wMaxPacketSize = 0x0008
bInterval = 0x0009
bRefresh = 0x
bSynchAddress = 0x


Interface 1
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x0001
  bAlternateSetting = 0x
  bNumEndpoints = 0x0002
  bInterfaceClass = 0x000a  
  bInterfaceSubClass = 0x
  bInterfaceProtocol = 0x
  iInterface = 0x0005  

 Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081  
bmAttributes = 0x0002  
wMaxPacketSize = 0x0200
bInterval = 0x
bRefresh = 0x
bSynchAddress = 0x

 Endpoint 1
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0001  
bmAttributes = 0x0002  
wMaxPacketSize = 0x0200
bInterval = 0x
bRefresh = 0x
bSynchAddress = 0x

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #6 from Hans Petter Selasky  ---
Created attachment 184536
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184536=edit
USB RNDIS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

--- Comment #4 from Bipin Chandra  ---
i use the below command in the rpi cmdline.txt file to load the module which
also sets both the device and host mac id and yes i get the same host mac id on
macos/windows/linux

modules-load=dwc2,g_ether g_ether.use_eem=0 g_ether.dev_addr=8e:7a:7e:37:6f:bb
g_ether.host_addr=8e:7a:7e:37:6f:aa


usbdump -i usbus0 -f 2 -s 65536 -vvv > log.txt

10:02:39.038743 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 01 00 00 12 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 18 bytes
 flags 0x10 
 status 0xca1a3

10:02:39.040632 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=20,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 18 bytes
   12 01 00 02 02 00 00 40  25 05 A2 A4 09 04 01 02  |...@%...|
 0010  00 02 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |..  |
 flags 0x10 
 status 0xca1a1

10:02:39.043696 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 02 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 2 bytes
 flags 0x10 
 status 0xca1a3

10:02:39.045496 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 2 bytes
   04 03 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |..  |
 flags 0x10 
 status 0xca1a1

10:02:39.045546 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
 flags 0x10 
 status 0xea1a3

10:02:39.046485 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
 flags 0x10 
 status 0xea1a1

10:02:39.046535 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 01 03 09 04 02 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 2 bytes
 flags 0x10 
 status 0xca1a3

10:02:39.047472 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 2 bytes
   40 03 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |@.  |
 flags 0x10 
 status 0xca1a1

10:02:39.047521 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 01 03 09 04 40 00  -- -- -- -- -- -- -- --  |..@.|
 frame[1] READ 64 bytes
 flags 0x10 
 status 0xea1a3

10:02:39.048467 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=64,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 64 bytes
   40 03 4C 00 69 00 6E 00  75 00 78 00 20 00 34 00  |@.L.i.n.u.x. .4.|
 0010  2E 00 39 00 2E 00 33 00  37 00 2B 00 20 00 77 00  |..9...3.7.+. .w.|
 0020  69 00 74 00 68 00 20 00  32 00 30 00 39 00 38 00  |i.t.h. .2.0.9.8.|
 0030  30 00 30 00 30 00 30 00  2E 00 75 00 73 00 62 00  |0.0.0.0...u.s.b.|
 flags 0x10 
 status 0xea1a1

10:02:39.048523 usbus0.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 02 03 09 04 02 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 2 bytes
 flags 0x10 
 status 0xca1a3

10:02:39.049466 usbus0.2
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 2 bytes
   2C 03 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |,.  |
 flags 0x10 
 status 0xca1a1

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

Hans Petter Selasky  changed:

   What|Removed |Added

 CC||hsela...@freebsd.org

--- Comment #3 from Hans Petter Selasky  ---
Could you dump the USB messages when this device is connected under FreeBSD:

Note the numbers after ugenX.Y:

Before plugging the device, run:

usbdump -i usbusX -F Y -s 65536 -vvv > log.txt

After plugging CTRL+C the usbdump.

Likely the Linux OTG module is storing the MAC address in a way that is
currently not compatible. This should be easy to figure out by code inspection.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #2 from Ed Maste  ---
Do you get the same MAC on macOS / Windows / Linux?

Independent of obtaining the "proper" MAC address the current approach for
generating a randomized MAC (from r184610) is somewhat bogus and should also be
revisited.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

Bipin Chandra  changed:

   What|Removed |Added

   Hardware|amd64   |Any

--- Comment #1 from Bipin Chandra  ---
ugen0.2:  at usbus0,
cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0002  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0525
  idProduct = 0xa4a2
  bcdDevice = 0x0409
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x  
  bNumConfigurations = 0x0002

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852

Bug ID: 220852
   Summary: [cdce] [usb] raspberry pi or anything that can emulate
Ethernet gadget over usb mac id not read
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: usb
  Assignee: freebsd-usb@FreeBSD.org
  Reporter: bi...@xbipin.com

raspberry pi zero have a kernel module which allows it to use the OTG port to
generate a virtual USB Ethernet adapter (RNDIS Gadget) and we can define its
host and device mac id and it works fine connecting the pi to mac OS, windows
or Linux but when you connect it to pfsense or any FreeBSD based system then
those ignore the supplied mac id and they always generate a random mac id
making it almost useless to be able to use on pfsense etc. I had reported this
on the pfsense bug request portal and i was told to report it here.

when the pi is connected to pfsense using USB the below is generated

ugen0.2:  at usbus0
cdce0: on usbus0
cdce0: No valid alternate setting found
device_attach: cdce0 attach returned 6
cdce0: on usbus0
cdce0: faking MAC address
ue0: on cdce0
ue0: Ethernet address: 2a:3f:38:a3:80:00

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

[Bug 192345] [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

Nick Hibma n_hi...@freebsd.org changed:

   What|Removed |Added

 Attachment #145319|0   |1
is obsolete||
 CC||n_hi...@freebsd.org
   Assignee|freebsd-usb@FreeBSD.org |n_hi...@freebsd.org

--- Comment #5 from Nick Hibma n_hi...@freebsd.org ---
Created attachment 145389
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145389action=edit
Same patch but reduced to including only E3272 related changes; the rest was
committed.

The attached patch has been reduced to the stuff which has not yet been
committed. Please note that this patch can not be applied as is to the sources
due to me picking out the rest of the patch and committing that.


This patch I am not quite sure how it works: It looks like the u3g driver is
used to do the eject and ignore the device afterwards. The change around line
857 in u3g.c I don't like. Could you attach the output of

   dmesg

after attaching the device? And the output of

   usbconfig -d ugenX.Y dump_device_desc


Thanks for the other changes! They have been committed (in some form).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[Bug 192345] [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Attachment #145289|0   |1
is obsolete||

--- Comment #4 from rozhuk...@gmail.com ---
Created attachment 145319
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145319action=edit
typo fix in comment

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[Bug 192345] New: [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

Bug ID: 192345
   Summary: [u3g] [umodem] [cdce] patch for new huawei 4G/LTE
modems (E3272 tested), Novatel MC990D Device ID
   Product: Base System
   Version: 10.0-RELEASE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: usb
  Assignee: freebsd-usb@FreeBSD.org
  Reporter: rozhuk...@gmail.com

Updates huawei usb mode switch (code from usb-modeswitch-2.2.0).
New switch code and modems without initial CD-ROM only mode - use vendor
specific InterfaceClass.
Tested on E3272 with different FW.

Details:
http://4pda.ru/forum/index.php?showtopic=508842view=findpostp=33295644

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[Bug 192345] [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

--- Comment #1 from rozhuk...@gmail.com ---
Created attachment 145259
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145259action=edit
patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[Bug 192345] [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Attachment #145259|0   |1
is obsolete||

--- Comment #2 from rozhuk...@gmail.com ---
Created attachment 145278
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145278action=edit
add cdc 46 code

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[Bug 192345] [u3g] [umodem] [cdce] patch for new huawei 4G/LTE modems (E3272 tested), Novatel MC990D Device ID

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

rozhuk...@gmail.com changed:

   What|Removed |Added

 Attachment #145278|0   |1
is obsolete||

--- Comment #3 from rozhuk...@gmail.com ---
Created attachment 145289
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145289action=edit
UISUBCLASS_ABSTRACT_CONTROL_MODEL - 0x02, some cosmetic

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

usb/174464: clone MAC address(es) on usb networks cdce(4) ue[0-9] -- no documentation (solution provided)

[Chris H]

Number: 174464
Category:   usb
Synopsis:   clone MAC address(es) on usb networks cdce(4)  ue[0-9] -- no 
documentation (solution provided)
Confidential:   no
Severity:   non-critical
Priority:   low
Responsible:freebsd-usb
State:  open
Quarter:
Keywords:   
Date-Required:
Class:  update
Submitter-Id:   current-users
Arrival-Date:   Sun Dec 16 01:30:00 UTC 2012
Closed-Date:
Last-Modified:
Originator: Chris H
Release:RELENG_8 and RELENG_9
Organization:
Environment:
8.3-STABLE/1386
9.0-STABLE/i386

Description:
I am evaluating a new ISP. The modem they provide has 2 ethernet ports --
one of which is USB. The modem caches the first device attached, and
as a result, given that BSD creates random (fake) a MAC address for
the USB port, I had to find a way to maintain a fixed MAC, that was
the same as the one I used when installing FreeBSD from a net-install
CD. Linux provides a clone MAC option in their Network Management. I
had expected to find it in BSD. But my experiences were pretty dismal.
I was unable to accomplish my need via any means of RC(8). It was
possible manually, via a CLI. So I scoured the net, BSD forums, handbook.
All without joy. So I subscribed to the net@ mailing list. While presented
with several suggestions. None were fruitful. So, determined, I worked
with both RELENG_8  RELENG_9. Installing one, or the other, and
experimenting until I could successfully get connected to the internet
with the correct stanza's in rc.conf(5).
I finally figured out how to make it always work (with DHCP, or STATIC IP).
given there is no documentation on this. I'd like to present it here, so
that it might make it to the handbook/man page.

How-To-Repeat:
attempt to keep the same MAC address when using usb ethernet
Fix:
 ORDER IS IMPORTANT 

--- begin rc,conf --

ifconfig_ue0=ether ##:##:##:##:##:##

ifconfig_ue0_alias0=DHCP

*** or ***

ifconfig_ue0_alias0=inet ip4.add.ress.anticipated netmask kno.wn.net.mask

followed by

defaultrouter=kno.wn.gate.way --applies only if using static IPv4

--- end rc,conf --

Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/122813: [udbp] [request] udbp driver should be removed in favour of cdce

[n_hibma]

Synopsis: [udbp] [request] udbp driver should be removed in favour of cdce

State-Changed-From-To: open-closed
State-Changed-By: n_hibma
State-Changed-When: Thu Nov 8 20:42:10 UTC 2012
State-Changed-Why: 
The driver has been removed from the GENERIC kernel config.

http://www.freebsd.org/cgi/query-pr.cgi?pr=122813
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/169459: [cdce] umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE

[linimon]

Old Synopsis: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 
9-STABLE
New Synopsis: [cdce] umodem/ppp/3g stopped working after update from 
9.0-RELEASE to 9-STABLE

Responsible-Changed-From-To: freebsd-bugs-freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Jun 26 19:50:42 UTC 2012
Responsible-Changed-Why: 
reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=169459
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/169459: [cdce] umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE

[Matthias Apitz]

El día Tuesday, June 26, 2012 a las 07:51:05PM +, lini...@freebsd.org 
escribió:

 Old Synopsis: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 
 9-STABLE
 New Synopsis: [cdce] umodem/ppp/3g stopped working after update from 
 9.0-RELEASE to 9-STABLE
 
 Responsible-Changed-From-To: freebsd-bugs-freebsd-usb
 Responsible-Changed-By: linimon
 Responsible-Changed-When: Tue Jun 26 19:50:42 UTC 2012
 Responsible-Changed-Why: 
 reclassify.
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=169459

IMHO the used ppp.conf file looks completely broken and the log of the
ppp chat proofs this;

matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e g...@unixarea.de - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

[CFR 4/n] removes uether dependency of cdce(4)

[Weongyo Jeong]

Hello,

This patch is to remove a uether dependency of cdce(4) and some style(9)
changes.  The change logs would be as follows:

  o removes uether dependency.
  o defines CDCE_DEV to clean up the supported device list.
  o uses bzero instead of memset.
  o style(9) - get rid of extra spaces and parentheses.

Please reviews.

regards,
Weongyo Jeong

Index: if_cdce.c
===
--- if_cdce.c   (revision 214604)
+++ if_cdce.c   (working copy)
@@ -61,6 +61,8 @@ __FBSDID($FreeBSD$);
 #include sys/lock.h
 #include sys/mutex.h
 #include sys/condvar.h
+#include sys/socket.h
+#include sys/sockio.h
 #include sys/sysctl.h
 #include sys/sx.h
 #include sys/unistd.h
@@ -68,6 +70,14 @@ __FBSDID($FreeBSD$);
 #include sys/malloc.h
 #include sys/priv.h
 
+#include net/if.h
+#include net/if_arp.h
+#include net/if_dl.h
+#include net/if_media.h
+#include net/if_types.h
+#include net/bpf.h
+#include net/ethernet.h
+
 #include dev/usb/usb.h
 #include dev/usb/usbdi.h
 #include dev/usb/usbdi_util.h
@@ -77,6 +87,7 @@ __FBSDID($FreeBSD$);
 #defineUSB_DEBUG_VAR cdce_debug
 #include dev/usb/usb_debug.h
 #include dev/usb/usb_process.h
+#include dev/usb/usb_sleepout.h
 #include usb_if.h
 
 #include dev/usb/net/usb_ethernet.h
@@ -99,14 +110,16 @@ static usb_callback_t cdce_ncm_bulk_write_callback
 static usb_callback_t cdce_ncm_bulk_read_callback;
 #endif
 
-static uether_fn_t cdce_attach_post;
-static uether_fn_t cdce_init;
-static uether_fn_t cdce_stop;
-static uether_fn_t cdce_start;
-static uether_fn_t cdce_setmulti;
-static uether_fn_t cdce_setpromisc;
-
 static uint32_tcdce_m_crc32(struct mbuf *, uint32_t, uint32_t);
+static int cdce_ioctl(struct ifnet *, u_long, caddr_t);
+static voidcdce_start(struct ifnet *);
+static voidcdce_start_locked(struct ifnet *);
+static voidcdce_init(void *);
+static voidcdce_init_locked(struct cdce_softc *);
+static voidcdce_stop_locked(struct cdce_softc *);
+static int cdce_rxmbuf(struct cdce_softc *, struct mbuf *, unsigned int);
+static struct mbuf *cdce_newbuf(void);
+static voidcdce_rxflush(struct cdce_softc *);
 
 #ifdef USB_DEBUG
 static int cdce_debug = 0;
@@ -120,7 +133,6 @@ SYSCTL_INT(_hw_usb_cdce, OID_AUTO, interval, CTLFL
 #endif
 
 static const struct usb_config cdce_config[CDCE_N_TRANSFER] = {
-
[CDCE_BULK_RX] = {
.type = UE_BULK,
.endpoint = UE_ADDR_ANY,
@@ -174,7 +186,6 @@ static const struct usb_config cdce_config[CDCE_N_
 
 #if CDCE_HAVE_NCM
 static const struct usb_config cdce_ncm_config[CDCE_N_TRANSFER] = {
-
[CDCE_BULK_RX] = {
.type = UE_BULK,
.endpoint = UE_ADDR_ANY,
@@ -255,29 +266,21 @@ MODULE_DEPEND(cdce, uether, 1, 1, 1);
 MODULE_DEPEND(cdce, usb, 1, 1, 1);
 MODULE_DEPEND(cdce, ether, 1, 1, 1);
 
-static const struct usb_ether_methods cdce_ue_methods = {
-   .ue_attach_post = cdce_attach_post,
-   .ue_start = cdce_start,
-   .ue_init = cdce_init,
-   .ue_stop = cdce_stop,
-   .ue_setmulti = cdce_setmulti,
-   .ue_setpromisc = cdce_setpromisc,
-};
-
 static const struct usb_device_id cdce_devs[] = {
-   {USB_VPI(USB_VENDOR_ACERLABS, USB_PRODUCT_ACERLABS_M5632, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_AMBIT, USB_PRODUCT_AMBIT_NTL_250, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_COMPAQ, USB_PRODUCT_COMPAQ_IPAQLINUX, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_GMATE, USB_PRODUCT_GMATE_YP3X00, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_MOTOROLA2, USB_PRODUCT_MOTOROLA2_USBLAN, 
CDCE_FLAG_ZAURUS | CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_MOTOROLA2, USB_PRODUCT_MOTOROLA2_USBLAN2, 
CDCE_FLAG_ZAURUS | CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_NETCHIP, USB_PRODUCT_NETCHIP_ETHERNETGADGET, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2501, 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SL5500, CDCE_FLAG_ZAURUS)},
-   {USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SL5600, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLA300, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLC700, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
-   {USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLC750, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
+#defineCDCE_DEV(v,p,i) { USB_VPI(USB_VENDOR_##v, 
USB_PRODUCT_##v##_##p, i) }
+   CDCE_DEV(ACERLABS, M5632, CDCE_FLAG_NO_UNION),
+   CDCE_DEV(AMBIT, NTL_250, CDCE_FLAG_NO_UNION),
+   CDCE_DEV(COMPAQ, IPAQLINUX, CDCE_FLAG_NO_UNION),
+   CDCE_DEV(GMATE, YP3X00, CDCE_FLAG_NO_UNION),
+   CDCE_DEV(MOTOROLA2, USBLAN, CDCE_FLAG_ZAURUS | CDCE_FLAG_NO_UNION),
+   CDCE_DEV(MOTOROLA2, USBLAN2, CDCE_FLAG_ZAURUS | CDCE_FLAG_NO_UNION),
+   CDCE_DEV(NETCHIP, ETHERNETGADGET, CDCE_FLAG_NO_UNION),
+   CDCE_DEV(PROLIFIC, PL2501

Re: usb/143620: [cdce] the module if_cdce doesn't support my Openmoko Neo FreeRunner anymore [regression]

[linimon]

Old Synopsis: the module if_cdce doesn't support my Openmoko Neo FreeRunner 
anymore
New Synopsis: [cdce] the module if_cdce doesn't support my Openmoko Neo 
FreeRunner anymore [regression]

State-Changed-From-To: open-feedback
State-Changed-By: linimon
State-Changed-When: Mon Feb 8 06:23:16 UTC 2010
State-Changed-Why: 
To submitter: does the workaround fix your problem?

http://www.freebsd.org/cgi/query-pr.cgi?pr=143620
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

patch: (newusb) cdce failed to attach, was ignoring quirks

[Juergen Lock]

I'd say the broader matches must come after the specific ones here or
the quirks may not be found...  (This makes at least my zaurus attach and
pingable again.)

Index: sys/dev/usb/net/if_cdce.c
@@ -197,9 +197,6 @@
 };
 
 static const struct usb_device_id cdce_devs[] = {
-   {USB_IF_CSI(UICLASS_CDC, UISUBCLASS_ETHERNET_NETWORKING_CONTROL_MODEL, 
0)},
-   {USB_IF_CSI(UICLASS_CDC, UISUBCLASS_MOBILE_DIRECT_LINE_MODEL, 0)},
-
{USB_VPI(USB_VENDOR_ACERLABS, USB_PRODUCT_ACERLABS_M5632, 
CDCE_FLAG_NO_UNION)},
{USB_VPI(USB_VENDOR_AMBIT, USB_PRODUCT_AMBIT_NTL_250, 
CDCE_FLAG_NO_UNION)},
{USB_VPI(USB_VENDOR_COMPAQ, USB_PRODUCT_COMPAQ_IPAQLINUX, 
CDCE_FLAG_NO_UNION)},
@@ -213,6 +210,9 @@
{USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLA300, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
{USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLC700, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
{USB_VPI(USB_VENDOR_SHARP, USB_PRODUCT_SHARP_SLC750, CDCE_FLAG_ZAURUS | 
CDCE_FLAG_NO_UNION)},
+
+   {USB_IF_CSI(UICLASS_CDC, UISUBCLASS_ETHERNET_NETWORKING_CONTROL_MODEL, 
0)},
+   {USB_IF_CSI(UICLASS_CDC, UISUBCLASS_MOBILE_DIRECT_LINE_MODEL, 0)},
 };
 
 static int
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: patch: (newusb) cdce failed to attach, was ignoring quirks

[Hans Petter Selasky]

On Wednesday 05 August 2009 18:54:32 Juergen Lock wrote:
 I'd say the broader matches must come after the specific ones here or
 the quirks may not be found...  (This makes at least my zaurus attach and
 pingable again.)

Right!

Thanks for reporting.

Committed to USB P4:

http://perforce.freebsd.org/chv.cgi?CH=167039

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: patch: (newusb) cdce failed to attach, was ignoring quirks

[Juergen Lock]

On Wed, Aug 05, 2009 at 08:00:53PM +0200, Hans Petter Selasky wrote:
 On Wednesday 05 August 2009 18:54:32 Juergen Lock wrote:
  I'd say the broader matches must come after the specific ones here or
  the quirks may not be found...  (This makes at least my zaurus attach and
  pingable again.)
 
 Right!
 
 Thanks for reporting.
 
 Committed to USB P4:
 
 http://perforce.freebsd.org/chv.cgi?CH=167039

You're welcome!
Juergen

(I was glad I was able to spot the bug myself too, given how little I
know about usb... :)
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/133896: [cdce] [newusb] panic when disconnecting cdce device just before powering off PC

[brucec]

Synopsis: [cdce] [newusb] panic when disconnecting cdce device just before 
powering off PC

State-Changed-From-To: open-closed 
State-Changed-By: brucec
State-Changed-When: Tue May 5 16:48:24 UTC 2009
State-Changed-Why: 
Fixed in -current.

http://www.freebsd.org/cgi/query-pr.cgi?pr=133896
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/133896: [cdce] panic when disconnecting cdce device just before powering off PC

[Hans Petter Selasky]

On Tuesday 21 April 2009, Bruce Cran wrote:
 Number: 133896
 Category:   usb
 Synopsis:   [cdce] panic when disconnecting cdce device just before
  powering off PC Confidential:   no
 Severity:   serious
 Priority:   low
 Responsible:freebsd-usb
 State:  open
 Quarter:
 Keywords:
 Date-Required:
 Class:  sw-bug
 Submitter-Id:   current-users
 Arrival-Date:   Tue Apr 21 19:50:00 UTC 2009
 Closed-Date:
 Last-Modified:
 Originator: Bruce Cran
 Release:8.0-CURRENT
 Organization:
 Environment:

 FreeBSD 8.0-CURRENT amd64

 Description:

 Running -current from mid-April 2009 I got a panic when shutting
 down.  I'd pressed the power button on my GTA02 and at about the same
 time pressed the power button on my PC too.  It seems the GTA02
 CDCE device powered off first, just before FreeBSD was going to power
 off:

 Waiting (max 60 seconds) for system process 'vnlru' to stop...done
 Waiting (max 60 seconds) for system process 'bufdaemon' to stop...done
 Waiting (max 60 seconds) for system process 'syncer' to stop...
 Syncing disks, vnodes remaining...1 1 1 0 0 0 done
 All buffers synced.
 Uptime: 10h12m10s
 ugen3.2: Linux 2.6.29-rc3 with s3c2410_udc at usbus3 (disconnected)
 cdce0: at uhub3, port 2, addr 2 (disconnected)


 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address  = 0x288
 fault code = supervisor read data, page not present
 instruction pointer= 0x20:0x80343d3e
 stack pointer  = 0x28:0xfffe4001c8a0
 frame pointer  = 0x28:0xfffe4001c8c0
 code segment   = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags   = interrupt enabled, resume, IOPL = 0
 current process= 1 (init)
 [thread pid 1 tid 12 ]
 Stopped at _mtx_lock_sleep+0x4e:   movl   0x288(%rcx),%esi
 db bt
 Tracing pid 1 tid 12 td 0xff00014d7a80
 _mtx_lock_sleep() at _mtx_lock_sleep+0x4e
 _sleep() at _sleep+0x232
 usb2_proc_mwait() at usb2_proc_mwait+0x46
 usb2_ether_ifshutdown() at usb2_ether_ifshutdown+0xaf
 cdce_shutdown() at cdce_shutdown+0x11
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 acpi_shutdown() at acpi_shutdown+0x9
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 bus_generic_shutdown() at bus_generic_shutdown+0x1a
 root_bus_module_handler() at root_bus_module_handler+0x11b
 module_shutdown() at module_shutdown+0x84
 boot() at boot+0x37b
 reboot() at reboot+0x46
 syscall() at syscall+0x264
 Xfast_syscall() at Xfast_syscall+0xd0
 --- syscall (55, FreeBSD ELF64, reboot), rip = 0x40897c, rsp =
 0x7fffe738, rbp = 0x402420 ---

 How-To-Repeat:
 
 Fix:
 
 
 Release-Note:
 Audit-Trail:
 Unformatted:


I'm working on this issue.

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/133896: [cdce] panic when disconnecting cdce device just before powering off PC

[Hans Petter Selasky]

The following reply was made to PR usb/133896; it has been noted by GNATS.

From: Hans Petter Selasky hsela...@c2i.net
To: freebsd-usb@freebsd.org
Cc: Bruce Cran br...@cran.org.uk,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/133896: [cdce] panic when disconnecting cdce device just 
before powering off PC
Date: Thu, 23 Apr 2009 09:02:10 +0200

 On Tuesday 21 April 2009, Bruce Cran wrote:
  Number: 133896
  Category:   usb
  Synopsis:   [cdce] panic when disconnecting cdce device just before
   powering off PC Confidential:   no
  Severity:   serious
  Priority:   low
  Responsible:freebsd-usb
  State:  open
  Quarter:
  Keywords:
  Date-Required:
  Class:  sw-bug
  Submitter-Id:   current-users
  Arrival-Date:   Tue Apr 21 19:50:00 UTC 2009
  Closed-Date:
  Last-Modified:
  Originator: Bruce Cran
  Release:8.0-CURRENT
  Organization:
  Environment:
 
  FreeBSD 8.0-CURRENT amd64
 
  Description:
 
  Running -current from mid-April 2009 I got a panic when shutting
  down.  I'd pressed the power button on my GTA02 and at about the same
  time pressed the power button on my PC too.  It seems the GTA02
  CDCE device powered off first, just before FreeBSD was going to power
  off:
 
  Waiting (max 60 seconds) for system process 'vnlru' to stop...done
  Waiting (max 60 seconds) for system process 'bufdaemon' to stop...done
  Waiting (max 60 seconds) for system process 'syncer' to stop...
  Syncing disks, vnodes remaining...1 1 1 0 0 0 done
  All buffers synced.
  Uptime: 10h12m10s
  ugen3.2: Linux 2.6.29-rc3 with s3c2410_udc at usbus3 (disconnected)
  cdce0: at uhub3, port 2, addr 2 (disconnected)
 
 
  Fatal trap 12: page fault while in kernel mode
  cpuid = 0; apic id = 00
  fault virtual address  = 0x288
  fault code = supervisor read data, page not present
  instruction pointer= 0x20:0x80343d3e
  stack pointer  = 0x28:0xfffe4001c8a0
  frame pointer  = 0x28:0xfffe4001c8c0
  code segment   = base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
  processor eflags   = interrupt enabled, resume, IOPL = 0
  current process= 1 (init)
  [thread pid 1 tid 12 ]
  Stopped at _mtx_lock_sleep+0x4e:   movl   0x288(%rcx),%esi
  db bt
  Tracing pid 1 tid 12 td 0xff00014d7a80
  _mtx_lock_sleep() at _mtx_lock_sleep+0x4e
  _sleep() at _sleep+0x232
  usb2_proc_mwait() at usb2_proc_mwait+0x46
  usb2_ether_ifshutdown() at usb2_ether_ifshutdown+0xaf
  cdce_shutdown() at cdce_shutdown+0x11
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  acpi_shutdown() at acpi_shutdown+0x9
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  bus_generic_shutdown() at bus_generic_shutdown+0x1a
  root_bus_module_handler() at root_bus_module_handler+0x11b
  module_shutdown() at module_shutdown+0x84
  boot() at boot+0x37b
  reboot() at reboot+0x46
  syscall() at syscall+0x264
  Xfast_syscall() at Xfast_syscall+0xd0
  --- syscall (55, FreeBSD ELF64, reboot), rip = 0x40897c, rsp =
  0x7fffe738, rbp = 0x402420 ---
 
  How-To-Repeat:
  
  Fix:
  
  
  Release-Note:
  Audit-Trail:
  Unformatted:
 
 
 I'm working on this issue.
 
 --HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: usb/122813: [udbp] [request] udbp driver should be removed in favour of cdce

[vwe]

Synopsis: [udbp] [request] udbp driver should be removed in favour of cdce

Responsible-Changed-From-To: freebsd-bugs-freebsd-usb
Responsible-Changed-By: vwe
Responsible-Changed-When: Sun May 11 16:34:19 UTC 2008
Responsible-Changed-Why: 

Over to maintainer(s).
Believing nobody uses code because no bug has been reported,
is a nice assumption :)
Probably it's a sign of good code?

http://www.freebsd.org/cgi/query-pr.cgi?pr=122813
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: CDCE

[Hans Petter Selasky]

On Friday 23 March 2007 08:29, Anne wrote:
 Hi again,
 Am I on the correct list for this question?

Yes.


 New peice of hardware, no specs, is a HPSDA wireless modem from Cmotech
 device id 0x6280. Cmotech have not yet listed it.

 I have modified if_cdce.c to recognise the new hardware, I have 3 cdcd
 ifaces.

 I need to treat the virtuel ethernet (cdce) as a serial device.
 I have to attach a tty with cua?? to the CDCE.

 How do I do it.
 PPPoE wont work. I have to create ttys.

 I have spent 4 days on this a solution would make my day.

 John

Hi John,

Could you maybe install /usr/ports/sysutils/udesc_dump

Then kldload ugen. Make sure that your device attaches like ugen, and post 
the USB descriptors of your device? That is the output from udesc_dump.

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]