linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Thomas Richter <richter@rus.uni-stuttgart.de>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org,
	"Josep Lladonosa" <jlladono@gmail.com>,
	dahinds@users.sourceforge.net, linux-pcmcia@lists.infradead.org,
	"Tomáš Kováčik" <nail@nodomain.sk>
Subject: Re: [PCMCIA] Solved: No USB 2.0 (ehci) in PCMCIA slot on E7110
Date: Mon, 12 Aug 2013 23:25:07 +0200	[thread overview]
Message-ID: <20130812212507.GA12254@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <5207C8D4.1040609@rus.uni-stuttgart.de>

Hi,

that means we're talking this one (have you had a look at Bugzilla #15014?
Might be useful...):

commit 35169529093be3bbef70afd3c4125e35cece7e03
Author: Wolfram Sang <w.sang@pengutronix.de>
Date:   Sun Jan 10 09:41:24 2010 +0100

    pcmcia/yenta: add module parameter for O2 speedups
    
    O2-bridges can do read prefetch and write burst. However, for some combinations
    of older bridges and cards, this causes problems, so it is disabled for those
    bridges. Now, as some users know their setup works with the speedups enabled, a
    new parameter is introduced to the driver. Now, a user can specifically enable
    or disable these features, while the default is what we have today: detect the
    bridge and decide accordingly. Fixes Bugzilla entry 15014.
    
    Simplify and unify the printouts, fix a whitespace issue while we are here.
    
    Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
    Tested-by: frodone@gmail.com
    [linux@dominikbrodowski.net: whitespace fixes]
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>


And my

git log -p drivers/pcmcia/o2micro.h

also mentions

commit 1ff84890b62b20823b3697a6041bbec1b5280cee
Author: Tomas Kovacik <nail@nodomain.sk>
Date:   Sun Jul 26 22:04:58 2009 +0200

    pcmcia: disable prefetch/burst for OZ6933
    
    Problems have been reported [1], so disable prefetch/burst, to be on the safe
    side.
    
    [1] http://www.mail-archive.com/linux-pcmcia@lists.infradead.org/msg02048.html
    
    Signed-off-by: Tomáš Kováčik <nail@nodomain.sk>
    Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>



A useful idea would be to kindly ask Tomáš Kováčik (CC'd) about details of his system
(4 years later - but hopefully...), specifically lspci -vv -xxx or some such
(especially the revision of that controller might be *different*,
so perhaps only *some* 6933 remained affected, whereas newer ones of that
possibly more modern chipset ID started to get corrected).
Or quite likely there's some sufficiently detailed lspci log of that hardware
out on the internet somewhere...


Note that there's the comment
"for some bridges it is at 0x94, for others at 0xD4. it's
         * ok to write to both registers on all O2 bridges."
, yet our 6933 support lines were added *later*,
so there's a faint possibility that the compatibility statement
actually does not apply to this chipset.



And of course there remains the question *why* such slow communication
would then cause such severe USB HC communication trouble.
There might be some safeguard missing there as well...


And kudos to the patch submitters for having supplied
such nicely detailed commit logs!
(although mentioning the title of URLs probably would have been even better)



> Note that this is only a 1.7Ghz Pentium-4-M dinosaur.

That means you really don't want to know which kinds of machines I am using ;)
(yes, I'm sitting at a CardBus box here, too)
((TI CardBus controller))


Greetings,

Andreas Mohr (KA/S)

  reply	other threads:[~2013-08-12 21:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  6:00 [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110 Thomas Richter
2013-08-09 17:46 ` Alan Stern
2013-08-09 19:29   ` Thomas Richter
2013-08-09 19:35     ` Alan Stern
2013-08-09 23:14       ` Thomas Richter
2013-08-10  1:07         ` Alan Stern
2013-08-10  8:36           ` Thomas Richter
2013-08-10 11:26           ` Thomas Richter
2013-08-10 12:04             ` Alan Stern
2013-08-10 19:04               ` Josep Lladonosa
2013-08-10 19:52                 ` Thomas Richter
2013-08-10 19:58                   ` Josep Lladonosa
2013-08-10 20:03                     ` Josep Lladonosa
2013-08-10 20:05                       ` Thomas Richter
2013-08-10 20:05                     ` Thomas Richter
2013-08-11  1:40                 ` Alan Stern
2013-08-10 19:48               ` Thomas Richter
2013-08-11  1:46                 ` Alan Stern
2013-08-11  8:51                   ` Thomas Richter
2013-08-11 13:27                   ` Thomas Richter
2013-08-11 17:24                   ` [PCMCIA] Solved: No USB 2.0 (ehci) " Thomas Richter
2013-08-12 21:25                     ` Andreas Mohr [this message]
2013-08-13  5:57                       ` Tomas Kovacik

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=20130812212507.GA12254@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=dahinds@users.sourceforge.net \
    --cc=jlladono@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=nail@nodomain.sk \
    --cc=richter@rus.uni-stuttgart.de \
    --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;
as well as URLs for NNTP newsgroup(s).