From: "Suresh Kumar N." <suri.injun@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Clarification regarding USB Data Card (Dongle) enumeration in Linux udev
Date: Tue, 06 May 2014 03:19:47 +0000 [thread overview]
Message-ID: <CALR+S1hhbP=XgCXBULnKJ2pppgEf3xBQpkmn0OK47HX3XQuNHg@mail.gmail.com> (raw)
In-Reply-To: <CALR+S1ivJ88=kEhKOPancq-GzJdApsV_DaJOV3djPZSQhETV7Q@mail.gmail.com>
On Mon, May 5, 2014 at 10:39 PM, Greg KH <greg@kroah.com> wrote:
> On Mon, May 05, 2014 at 09:13:08AM +0530, Suresh Kumar N. wrote:
>> Dear Greg,
>>
>> Data Card here refers to 3G Dongle.
>
> There is not any "standard" for these.
>
>> Yes, it is right; device enumeration depends on the device itself.
>> But, there must be some guideline defined regarding the same.
>>
>> As per the link (http://www.linux-usb.org/usb.devices.txt) USB device
>> cannot be enumerated as Network controllers, please correct me if
>> something has been overlooked.
>
> Not true, I have a usb network device right here.
In such a case, who configures or should configure IP address to this
network device?.
>
>> Would all 3G Dongle devices be enumerated as "ACM USB modems"?
>
> Not at all, some show up as a custom USB to serial device, some as a
> network device, and others as a ACM modem.
So it all depends on the Vendor (providing the 3G Dongle) about how
the device gets enumerated (again based on the USB descriptors in the
device).
>
> Again, look at the USB descriptors in the device, that will tell you how
> the device is to be communicated with.
Thanks for the information Greg.
>
> greg k-h
prev parent reply other threads:[~2014-05-06 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 9:34 Clarification regarding USB Data Card (Dongle) enumeration in Linux udev Suresh Kumar N.
2014-05-04 16:16 ` Greg KH
2014-05-05 3:55 ` Suresh Kumar N.
2014-05-05 17:09 ` Greg KH
2014-05-06 3:19 ` Suresh Kumar N. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALR+S1hhbP=XgCXBULnKJ2pppgEf3xBQpkmn0OK47HX3XQuNHg@mail.gmail.com' \
--to=suri.injun@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).