The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Loading both ehci-hcd and uhci-hcd drivers causes my printer to fail
Date: Mon, 09 Mar 2009 17:57:33 +0200	[thread overview]
Message-ID: <1236614253.17511.5.camel@maxim-laptop> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0903091050280.3778-100000@iolanthe.rowland.org>

On Mon, 2009-03-09 at 10:53 -0400, Alan Stern wrote:
> On Mon, 9 Mar 2009, Maxim Levitsky wrote:
> 
> > Sorry, sorry, sorry.
> > 
> > is was the CONFIG_USB_EHCI_TT_NEWSCHED that did it.
> > I confused both options, without the above option printer works
> > flawlessly.
> 
> Is your printer connected directly to the computer, or does it go 
> through a hub?  (If it is connected directly then EHCI_TT_NEWSCHED 
> should not affect it at all.)
> 
> If it does go through a hub, does it behave better when you attach it 
> directly?
> 
> Alan Stern
> 
No, it is connected directly.
Just tried 'bad' driver, and firmware upload failed

Do you mean that CONFIG_USB_EHCI_TT_NEWSCHED doesn't affect the driver
at all when no hub is presented?

Btw, at least according to lsusb -t, there are no internal hubs in the
printer.


But it can be a coincidence, it seems that with 'bad' driver printer
works 'better' to as it failed back few days ago much more often, maybe
cable is bad, don't know, but according to the web these printers
1018/1020.. have usb problems, there is even a readme for that in
foo2zjz  

I try to use the 'good' driver 
(without CONFIG_USB_EHCI_TT_NEWSCHED) for some time.


Best regards,
	Maxim Levitsky


  reply	other threads:[~2009-03-09 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07 19:20 [BUG] Loading both ehci-hcd and uhci-hcd drivers causes my printer to fail Maxim Levitsky
2009-03-07 19:52 ` Greg KH
2009-03-07 20:22   ` Maxim Levitsky
2009-03-07 20:23     ` Maxim Levitsky
2009-03-08  0:55     ` Maxim Levitsky
2009-03-08  3:27     ` Alan Stern
2009-03-08 16:09       ` Maxim Levitsky
2009-03-08 16:58         ` Alan Stern
2009-03-09 10:07           ` Maxim Levitsky
2009-03-09 12:26             ` Maxim Levitsky
2009-03-09 14:53               ` Alan Stern
2009-03-09 15:57                 ` Maxim Levitsky [this message]
2009-03-09 16:15                   ` Alan Stern
2009-03-09 18:59                     ` Maxim Levitsky
2009-03-09 19:12                       ` Alan Stern
2009-03-09 19:51                         ` Maxim Levitsky
2009-03-09 20:02                           ` Maxim Levitsky

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=1236614253.17511.5.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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