public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Norbert Preining <preining@logic.at>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	linux-kernel@vger.kernel.org,
	USB development list <linux-usb@vger.kernel.org>
Subject: Re: Huawei E220 and usb storage
Date: Thu, 14 Feb 2008 11:05:01 -0800	[thread overview]
Message-ID: <20080214110501.ec400e10.zaitcev@redhat.com> (raw)
In-Reply-To: <20071116132256.GA19251@gamma.logic.tuwien.ac.at>

On Fri, 16 Nov 2007 14:22:56 +0100, Norbert Preining <preining@logic.at> wrote:

> > > The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
> > > Can you try zero length with the kernel? It's the second argument to the last.
> > 
> > I tried with the git patch plus changing the penultimage argument from
> > 0x1 to 0.
> 
> Ok, did new tests with 2.6.24-rc2:
> - with plain kernel the usb-storage modules attaches and detaches
>   permanently a virtual cd drive, I stopped after 30+ iterations.

It looks like between Dave Russel and I, we hit the same problem
that you did, after taking care of detection and initialization.
Look at his dmesg in comment #44 in this:
 https://bugzilla.redhat.com/show_bug.cgi?id=253096#c44

> - changing the penultimage argument in the usb_stor_huawei_e220_init
>   function from 0x1 to 0 stopped this misbehaviour, but
> 
> - with the change from 0x1 to 0 the initialization works automatically.

I may be able to test this.

As you recall, Huawei people themselves suggested nonzero length,
this is why we didn't want to change it. But perhaps they are
mistaken about the operation of their own hardware. Stranger
things happened...

-- Pete

  reply	other threads:[~2008-02-14 19:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 19:09 Huawei E220 and usb storage Norbert Preining
2007-10-30 22:00 ` Pete Zaitcev
2007-10-30 22:03   ` Norbert Preining
2007-10-31  4:17 ` Kristoffer Ericson
2007-10-30 20:47   ` Norbert Preining
2007-10-30 21:15     ` Chuck Ebbert
2007-10-30 21:22       ` Norbert Preining
2007-10-30 22:28         ` Pete Zaitcev
2007-10-31  6:15           ` Norbert Preining
2007-10-31  6:23             ` Norbert Preining
2007-10-31  6:45               ` Pete Zaitcev
2007-10-31  6:49                 ` Norbert Preining
2007-10-31  7:50                 ` Norbert Preining
2007-11-16 13:22             ` Norbert Preining
2008-02-14 19:05               ` Pete Zaitcev [this message]
2008-02-20  6:57                 ` Norbert Preining
2008-02-25 18:50                   ` Pete Zaitcev
2008-02-27  8:49                     ` Norbert Preining
2007-10-30 21:53       ` Norbert Preining
2007-10-31  6:48     ` Kristoffer Ericson
  -- strict thread matches above, loose matches on Subject: below --
2008-02-15 10:21 maximilian attems

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=20080214110501.ec400e10.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=cebbert@redhat.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=preining@logic.at \
    /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