From: Greg KH <greg@kroah.com>
To: Rory Filer <rfiler@SierraWireless.com>
Cc: Ralf Nyren <ralf@nyren.net>,
Stephen Clark <sclark46@earthlink.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kevin Lloyd <klloyd@SierraWireless.com>
Subject: Re: Sierra Wireless (MC8780) HSDPA speed issue
Date: Tue, 17 Mar 2009 09:13:41 -0700 [thread overview]
Message-ID: <20090317161341.GA27956@kroah.com> (raw)
In-Reply-To: <8F90F944E50427428C60E12A34A309D21C40221D59@carmd-exchmb01.sierrawireless.local>
On Tue, Mar 17, 2009 at 09:04:22AM -0700, Rory Filer wrote:
> Hi Ralf,
>
> I wonder whether you could do a little experiment for me. Issue the following AT command to both ports you've identified:
>
> ATI
>
> And note which of the AT ports provides the most information. They will both respond, but one will be more verbose than the others.
>
> Another thing of interest is to record how many files appear in response to the following command:
>
> ls /dev/ttyU*
>
> when the modem is running, of course.
>
> Question - at what point should we stop including linux-kernel in this thread, if at all?
If it's related to the driver like this, you should not stop including
linux-kernel.
By copying the list, it provides a well archived history of the problem
so that anyone who runs across it in the future can easily find it by
searching the web.
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-17 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:01 Sierra Wireless (MC8780) HSDPA speed issue Ralf Nyren
2009-03-14 4:03 ` Greg KH
2009-03-14 19:34 ` Ralf Nyren
2009-03-14 20:32 ` Greg KH
2009-03-15 1:32 ` Stephen Clark
2009-03-15 20:11 ` Ralf Nyren
2009-03-15 22:30 ` Rory Filer
2009-03-16 4:33 ` Greg KH
2009-03-16 12:48 ` Ralf Nyren
2009-03-16 15:52 ` Rory Filer
2009-03-17 15:54 ` Ralf Nyren
2009-03-17 16:04 ` Rory Filer
2009-03-17 16:13 ` Greg KH [this message]
2009-03-17 16:38 ` Ralf Nyren
2009-03-17 17:24 ` Rory Filer
2009-03-25 14:49 ` Ralf Nyren
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=20090317161341.GA27956@kroah.com \
--to=greg@kroah.com \
--cc=klloyd@SierraWireless.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@nyren.net \
--cc=rfiler@SierraWireless.com \
--cc=sclark46@earthlink.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