public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andy Gay <andy@andynet.net>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: USB driver for Sierra Wireless EM5625/MC5720 1xEVDO modules
Date: Wed, 28 Jun 2006 17:11:11 -0700	[thread overview]
Message-ID: <44A31A9F.3030102@goop.org> (raw)
In-Reply-To: <1151537247.3285.278.camel@tahini.andynet.net>

Andy Gay wrote:
> - these modules present 3 bulk EPs, the 2nd & 3rd can be used for
> control & status monitoring while data transfer is in progress on the
> 1st EP. This is useful (and necessary for my application) so we need to
> increase the port count.
>   
Ooh, can you share the details of those EPs?  Is your application public?

> So what should I do next? I see a few possibilities, assuming anyone is
> interested in this:
>
> - I could post a diff from Greg's driver. But I don't have hardware to
> test whether my changes will break it for the other devices that it
> supports;
>   
Well, it is specifically an airprime driver.  My card also presents 
another two endpoints, but I don't know what to do with them, so I 
haven't worried about them too much.  If they all talk the same thing, 
then they may as well be in the same driver.

Are you proposing adding some more protocol knowledge to airprime, or 
just make those EPs appear as more serial ports?

Thanks,
    J

  reply	other threads:[~2006-06-29  0:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 23:27 USB driver for Sierra Wireless EM5625/MC5720 1xEVDO modules Andy Gay
2006-06-29  0:11 ` Jeremy Fitzhardinge [this message]
2006-06-29  2:31   ` Andy Gay
2006-06-29  3:00 ` [linux-usb-devel] " Ken Brush
2006-06-30  2:13 ` Greg KH
2006-06-30  2:40   ` Roland Dreier
2006-06-30  2:51     ` Andy Gay
2006-06-30  3:02       ` Greg KH

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=44A31A9F.3030102@goop.org \
    --to=jeremy@goop.org \
    --cc=andy@andynet.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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