All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Robin Cook <rcook@wyrms.net>, Clemens Ladisch <clemens@ladisch.de>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux1394-devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Issue with firewire from 2.6.35.9 to 2.6.36.1
Date: Tue, 7 Dec 2010 09:27:35 +0100	[thread overview]
Message-ID: <20101207092735.48b82c40@stein> (raw)
In-Reply-To: <1291673087.4022.2.camel@pheuri.wyrms.net>

On Dec 06 Robin Cook wrote:
> 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.

I wonder which of our options is preferable:
  - Change fw-ohci from MSI blacklisting to whitelisting.  Agere FW643
    rev 07 is the only chip that can be whitelisted.
  - Simply drop MSI support altogether.
-- 
Stefan Richter
-=====-==-=- ==-- --===
http://arcgraph.de/sr/

  reply	other threads:[~2010-12-07  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 23:37 Issue with firewire from 2.6.35.9 to 2.6.36.1 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 [this message]
2010-12-07  9:17         ` Clemens Ladisch
2010-12-07 14:04           ` Stefan Richter
2011-01-08 10:16       ` 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=20101207092735.48b82c40@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=clemens@ladisch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.