From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Robin Cook <rcook@wyrms.net>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: Issue with firewire from 2.6.35.9 to 2.6.36.1
Date: Sat, 08 Jan 2011 11:16:22 +0100 [thread overview]
Message-ID: <4D283976.4070809@s5r6.in-berlin.de> (raw)
In-Reply-To: <1291673087.4022.2.camel@pheuri.wyrms.net>
Robin Cook wrote on 2010-12-06:
> Output from lspci -nn on the firewire controller.
>
> 07:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403]
>
> The modprobe firewire-ohci quirks=17 worked to get the devices being
> created again.
Thanks Robin,
the regression fix has been released in 2.6.36.3 now.
--
Stefan Richter
-=====-==-== ---= -=---
http://arcgraph.de/sr/
prev parent reply other threads:[~2011-01-08 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 23:37 Robin Cook
2010-12-06 0:11 ` Maxim Levitsky
2010-12-06 7:29 ` Stefan Richter
2010-12-06 9:40 ` Clemens Ladisch
2010-12-06 22:04 ` Robin Cook
2010-12-07 8:27 ` Stefan Richter
2010-12-07 9:17 ` Clemens Ladisch
2010-12-07 14:04 ` Stefan Richter
2011-01-08 10:16 ` Stefan Richter [this message]
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=4D283976.4070809@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=maximlevitsky@gmail.com \
--cc=rcook@wyrms.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
all inboxes | Powered by JetHome®