From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] FireWire fixes
Date: Sat, 18 Sep 2010 01:06:13 +0200 [thread overview]
Message-ID: <1284764773.2804.7.camel@maxim-laptop> (raw)
In-Reply-To: <tkrat.b186ea3830d71c45@s5r6.in-berlin.de>
On Fri, 2010-09-17 at 14:47 +0200, Stefan Richter wrote:
> Linus, please pull from the for-linus branch at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git for-linus
>
> to receive a hardware quirk entry and a small makefile correction.
> Thanks.
>
> Heikki Lindholm (1):
> firewire: ohci: activate cycle timer register quirk on Ricoh chips
That did it, the strange oops I had with new firewire stack is gone.
(I have the Ricoh chip in the laptop)
However the new stack is still very much unusable:
Running new stack on the laptop + old stack on the desktop gave me about
18-30 Mbit/s speeds varying all the time.
Running both with the new stack results in corrupted packets and sftp
exits immediately.
The problems I so hoped to be fixed in new stack still persist:
Cable disconection/reconnection still results in the link loss till
ifconfig down/up.
Suspend/resume also results in the link loss.
Driver still has panics on some occasions.
Best regards,
Maxim Levitsky
>
> Stefan Richter (1):
> firewire: nosy: fix build when CONFIG_FIREWIRE=N
>
> drivers/Makefile | 2 +-
> drivers/firewire/ohci.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletions(-)
>
>
> Full log and diff:
>
> commit 8702d33aa6e6d753ef99163afe48aba1323374ef
> Author: Stefan Richter <stefanr@s5r6.in-berlin.de>
> Date: Wed Sep 15 13:02:44 2010 +0200
>
> firewire: nosy: fix build when CONFIG_FIREWIRE=N
>
> drivers/firewire/nosy* is a stand-alone driver that does not depend on
> CONFIG_FIREWIRE. Hence let make descend into drivers/firewire/ also
> if that option is off.
>
> The stand-alone driver drivers/ieee1394/init_ohci1394_dma* will soon be
> moved into drivers/firewire/ too and will require the same makefile fix.
>
> Side effect:
> As mentioned in https://bugzilla.novell.com/show_bug.cgi?id=586172#c24
> this influences the order in which either firewire-ohci or ohci1394 is
> going to be bound to an OHCI-1394 controller in case of a modular build
> of both drivers if no modprobe blacklist entries are configured.
> However, a user of such a setup cannot expect deterministic behavior
> anyway. The Kconfig help and the migration guide at
> ieee1394.wiki.kernel.org recommend blacklist entries when a dual
> IEEE 1394 stack build is being used. (The coexistence period of the two
> stacks is planned to end soon.)
>
> Cc: Michal Marek <mmarek@suse.cz>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
>
> diff --git a/drivers/Makefile b/drivers/Makefile
> index 91874e0..0bbb456 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -50,7 +50,7 @@ obj-$(CONFIG_SPI) += spi/
> obj-y += net/
> obj-$(CONFIG_ATM) += atm/
> obj-$(CONFIG_FUSION) += message/
> -obj-$(CONFIG_FIREWIRE) += firewire/
> +obj-y += firewire/
> obj-y += ieee1394/
> obj-$(CONFIG_UIO) += uio/
> obj-y += cdrom/
>
> commit 970f4be85ae6ecf97b711a3a2a1d5cecd3ea0534
> Author: Heikki Lindholm <holin@iki.fi>
> Date: Mon Sep 6 22:30:45 2010 +0300
>
> firewire: ohci: activate cycle timer register quirk on Ricoh chips
>
> The Ricoh FireWire controllers appear to have the non-atomic cycle
> timer register access bug, so, activate the driver workaround by
> default.
>
> The behaviour was observed on:
> Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] and
> Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04).
>
> Signed-off-by: Heikki Lindholm <holin@iki.fi>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
>
> diff --git a/drivers/firewire/ohci.c b/drivers/firewire/ohci.c
> index be29b0b..1b05896 100644
> --- a/drivers/firewire/ohci.c
> +++ b/drivers/firewire/ohci.c
> @@ -263,6 +263,7 @@ static const struct {
> {PCI_VENDOR_ID_JMICRON, PCI_DEVICE_ID_JMICRON_JMB38X_FW, QUIRK_NO_MSI},
> {PCI_VENDOR_ID_NEC, PCI_ANY_ID, QUIRK_CYCLE_TIMER},
> {PCI_VENDOR_ID_VIA, PCI_ANY_ID, QUIRK_CYCLE_TIMER},
> + {PCI_VENDOR_ID_RICOH, PCI_ANY_ID, QUIRK_CYCLE_TIMER},
> {PCI_VENDOR_ID_APPLE, PCI_DEVICE_ID_APPLE_UNI_N_FW, QUIRK_BE_HEADERS},
> };
>
>
next prev parent reply other threads:[~2010-09-17 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 12:47 [git pull] FireWire fixes Stefan Richter
2010-09-17 23:06 ` Maxim Levitsky [this message]
2010-09-17 23:41 ` Stefan Richter
2010-09-18 0:00 ` Maxim Levitsky
2010-09-18 0:00 ` Peter Stuge
2010-09-18 0:02 ` Maxim Levitsky
-- strict thread matches above, loose matches on Subject: below --
2016-11-05 16:17 Stefan Richter
2014-05-30 13:41 Stefan Richter
2014-03-08 9:37 Stefan Richter
2011-08-15 14:01 Stefan Richter
2010-11-28 13:07 Stefan Richter
2010-11-05 20:04 Stefan Richter
2010-08-29 9:54 Stefan Richter
2010-03-02 18:45 [git pull] FireWire updates post 2.6.33 Stefan Richter
2010-03-26 13:05 ` [git pull] FireWire fixes Stefan Richter
2010-04-15 15:59 ` [git pull] FireWire fixes and documentation update Stefan Richter
2010-04-22 19:45 ` [git pull] FireWire fixes Stefan Richter
2009-12-06 17:56 [git pull] FireWire updates post 2.6.32 Stefan Richter
2009-12-11 20:59 ` [git pull] FireWire fix Stefan Richter
2009-12-31 18:55 ` [git pull] FireWire fixes; new firewire stack is recommended to distributors and users Stefan Richter
2010-01-28 17:05 ` [git pull] FireWire fixes Stefan Richter
2010-02-15 22:19 ` Stefan Richter
2009-11-28 0:50 Stefan Richter
2009-09-05 15:18 Stefan Richter
2007-08-25 16:24 [GIT PULL] " Stefan Richter
2007-08-02 18:52 Stefan Richter
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=1284764773.2804.7.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.org \
/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