Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: dcbw@redhat.com (Dan Williams)
To: linux-arm-kernel@lists.infradead.org
Subject: about HAL and USB EVDO usbserial problem
Date: Thu, 10 Sep 2009 13:33:09 -0700	[thread overview]
Message-ID: <1252614789.13201.42.camel@localhost.localdomain> (raw)
In-Reply-To: <14959928.480571252500507211.JavaMail.coremail@bj126app76.126.com>

On Wed, 2009-09-09 at 20:48 +0800, tommy.hong wrote:
> hi,all!
> 
> Now i met a problem with usb evdo card!
> 
> When i insmod usbserial with vendor id and product id,pppd connect OK
> with ttyUSB1 and can access internet with ppp0!

You really, really want to add that card's IDs to the proper kernel
drivers.  Doing so will allow NetworkManager to see and manage the
interface.  *Plus* you'll get much higher speeds.  usbserial simply
isn't capable of nor designed for the higher speeds of 3G cards.

What card is it?  If I know that, I can suggest what driver to add the
IDs to.

> But I want to use Networkmanager with ppp,because ppp0 isn't a
> standard platform device ,it is kernel virtual net
> (/sys/device/virtual/net/ppp0),causes HAL can't know it is a real
> network,Networkmanager depend on HAL!
> 
> Serveral days ago i have fix marvell8686 driver kernel hotplug
> bug,does usbserial driver miss similiar issue ?

Marvell vendor driver, or the upstream libertas driver?  Upstream
drivers are the only ones we guarantee to really support since they have
been vetted by kernel developers and tested by numerous people.  I test
the libertas driver regularly and it works well with NM.  I don't know
anything about the state of the marvell vendor driver.

Dan

           reply	other threads:[~2009-09-10 20:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <14959928.480571252500507211.JavaMail.coremail@bj126app76.126.com>]

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=1252614789.13201.42.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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