netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Marcel Holtmann <marcel@holtmann.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: cdc_ether.c: Add SE J105i to device whitelist
Date: Thu, 07 Jan 2010 08:21:20 -0800	[thread overview]
Message-ID: <1262881280.23268.50.camel@localhost.localdomain> (raw)
In-Reply-To: <874omyqoxy.fsf@nemi.mork.no>

On Thu, 2010-01-07 at 09:50 +0100, Bjørn Mork wrote:
> Dan Williams <dcbw@redhat.com> writes:
> 
> > Here's the difference:
> >
> > F3507g: requires AT command setup before cdc-ether port is usable
> > SE j105i: does not require AT command setup before port is usable
> >
> > Same on my TM-506; you can simply run DHCP on the 'usb0' port and it
> > works, because the phone is pretending to be a usb-ethernet device and
> > transparently bridge between the ethernet and the cellular network.
> > That's simply not the case with the F3507g or any other WWAN card.
> >
> > Phones are fundamentally different than WWAN cards and shouldn't be
> > treated like one, at least at this time.
> 
> OK, then I misunderstood the request.  I thought that this phone behaved
> like a WWAN card since it presumably advertised the same CDC "Mobile
> Direct Line" class as the Ericsson WWAN cards, maybe even with the same
> GUID in the MDLM header?

Interesting.  But I'd be very, very skeptical if the phone really acted
just like an MBM card.  My TM-506 has *some* of the same commands that
the F3507g and the F3607gw do but certainly not all of them.

> If it really behaves like you describe (which is what the other Sony
> Ericsson phones I've seen does too), then I don't understand why it
> doesn't just advertise a CDC Ethernet class device.  That's what the
> other phones do, and as you of course know, the reason why we don't have
> a gazillion phone VID/PID entries in cdc_ether.c..

Good question; though I've seen enough hardware that I'll simply just
assume they did it differently just because they could, not for any
specific reason.  Don't over-estimate the intelligence of firmware
people, they are just as human as the rest of us :)

Dan



      reply	other threads:[~2010-01-07 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 20:56 [PATCH] net: cdc_ether.c: Add SE J105i to device whitelist Thomas Loo
2009-12-23 21:48 ` Marcel Holtmann
2010-01-04 14:50   ` Bjørn Mork
2010-01-04 21:10     ` Marcel Holtmann
2010-01-05  7:34       ` Bjørn Mork
2010-01-05 11:31         ` Marcel Holtmann
2010-01-05 12:46           ` Bjørn Mork
2010-01-05 20:52             ` Marcel Holtmann
2010-01-07  6:38             ` Dan Williams
2010-01-07  8:50               ` Bjørn Mork
2010-01-07 16:21                 ` Dan Williams [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=1262881280.23268.50.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=bjorn@mork.no \
    --cc=marcel@holtmann.org \
    --cc=netdev@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 NNTP newsgroup(s).