All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andy Gay <andy@andynet.net>
Cc: Roland Dreier <rdreier@cisco.com>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net,
	Ken Brush <kbrush@gmail.com>
Subject: Re: [PATCH] Airprime driver improvements to allow full speed EvDO transfers
Date: Mon, 03 Jul 2006 09:28:14 -0700	[thread overview]
Message-ID: <44A9459E.9070303@goop.org> (raw)
In-Reply-To: <1151936484.3285.497.camel@tahini.andynet.net>

Andy Gay wrote:
>> I think if the hardware has the EPs, they should be exposed by the 
>> driver.  You can tweak usermode as to whether they get device nodes, 
>> what they're called, etc.
>>     
> I tend to agree. I'm thinking for now I should leave it as is, so it
> defaults to configuring 3 EPs. Perhaps later I'll try to collect #EP
> info for all the supported devices.
>   

Why not just expose all the EPs the hardware presents?  Is there a 
chance they might not be a serial connection?

> This is curious. I saw that '0218' in Greg's code, and 'corrected' it to
> 0018, because here's what I get with my MC5720:
>   

Yes, that patch was from me.

> P:  Vendor=1199 ProdID=0018 Rev= 0.01
> S:  Manufacturer=Sierra Wireless
> S:  Product=Sierra Wireless MC5720 Modem
>
> So evidently there are also multiple variants of each modem.
>   
My came embedded in a Thinkpad X60, and I think it is locked to 
Verizon.  The product ID might reflect either or both of those states.

    J

  reply	other threads:[~2006-07-03 16:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30  5:48 [PATCH] Airprime driver improvements to allow full speed EvDO transfers Andy Gay
2006-06-30  7:10 ` Andrew Morton
2006-06-30  8:52   ` Pete Zaitcev
2006-06-30 16:59     ` Andy Gay
2006-06-30 10:51   ` Sergei Organov
2006-06-30 12:13     ` [linux-usb-devel] " Alan Cox
2006-06-30 12:02       ` Arjan van de Ven
2006-06-30 13:34         ` Alan Cox
2006-06-30 16:35   ` Andy Gay
2006-07-07 17:23   ` Sergei Organov
2006-07-07 20:07     ` Alan Cox
2006-07-10 10:36       ` Sergei Organov
2006-07-10 11:10         ` Alan Cox
2006-07-10 15:54           ` Sergei Organov
2006-07-10 17:31             ` Alan Cox
2006-07-10 17:24               ` Sergei Organov
2006-07-13 14:17               ` Sergei Organov
2006-07-13 15:40                 ` Alan Cox
2006-07-13 18:20                   ` Sergei Organov
2006-07-13 19:08                     ` Greg KH
2006-07-14 10:13                       ` Sergei Organov
2006-06-30 20:04 ` Roland Dreier
2006-06-30 20:13   ` Andy Gay
2006-07-02 18:48 ` Roland Dreier
2006-07-02 20:29   ` Andy Gay
2006-07-02 20:47     ` Roland Dreier
2006-07-03  7:00     ` Jeremy Fitzhardinge
2006-07-03 14:21       ` Andy Gay
2006-07-03 16:28         ` Jeremy Fitzhardinge [this message]
2006-07-03 17:00           ` Andy Gay
2006-07-03 17:00     ` Greg KH
2006-07-03 17:55       ` Andy Gay
2006-07-03 18:08         ` Jeremy Fitzhardinge
2006-07-03 18:16         ` Greg KH
2006-07-03 22:43           ` Andy Gay
2006-07-03 15:43 ` [linux-usb-devel] " Ken Brush
2006-07-03 16:19   ` Andy Gay
2006-07-11 18:31 ` Sergei Organov
2006-07-11 18:55   ` Andy Gay
2006-07-12  9:20     ` Sergei Organov

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=44A9459E.9070303@goop.org \
    --to=jeremy@goop.org \
    --cc=andy@andynet.net \
    --cc=gregkh@suse.de \
    --cc=kbrush@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rdreier@cisco.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.