From: Jarod Wilson <jwilson@redhat.com>
To: linux1394-devel@lists.sourceforge.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH update] firewire: fw-ohci: work around generation bug in TI controllers (fix AV/C and more)
Date: Mon, 14 Apr 2008 13:30:22 -0400 [thread overview]
Message-ID: <200804141330.22131.jwilson@redhat.com> (raw)
In-Reply-To: <tkrat.3e4f8089bffc4e81@s5r6.in-berlin.de>
On Saturday 12 April 2008 04:31:25 pm Stefan Richter wrote:
> Unlike the ohci1394 driver, fw-ohci uses the selfIDGeneration field of
> bus reset packets to determine the generation of incoming requests as
> per OHCI 1.1 clause 8.4.2.3. This is more precise --- provided that the
> controller inserts the correct generation. Texas Instruments chips
> often don't.
>
> This prevented the transmission of response packets, which for example
> broke AV/C transactions as used when communicating with miniDV cameras
> and any other AV/C devices.
>
> There is apparently no way to detect and adjust incorrect generations.
> Therefore we ignore the generation of bus reset packets from TI chips
> and use the generation of the self ID buffer instead. Alas this is
> received at a slightly wrong time. In rare cases, this could cause us
> to not respond to legitimate requests or to respond to expired requests.
> (The latter is less likely because the bus reset packet AR event is
> typically handled before the self ID complete event.)
>
> Bug reported by Mladen Kuntner, who was extraordinarily patient while
> dealing with the driver maintainers.
> https://bugzilla.redhat.com/show_bug.cgi?id=243081
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
>
> update: use a quirk flag for simpler code
The work-around looks good to me, just one question.
> @@ -2360,6 +2369,8 @@ pci_probe(struct pci_dev *dev, const str
> ohci->old_uninorth = dev->vendor == PCI_VENDOR_ID_APPLE &&
> dev->device == PCI_DEVICE_ID_APPLE_UNI_N_FW;
> #endif
> + ohci->bus_reset_packet_quirk = dev->vendor == PCI_VENDOR_ID_TI;
> +
I have a few cards with PCI_VENDOR_ID_CREATIVE with a TI TSB41AB2 chip on 'em
(SoundBlaster Audigy w/FireWire port). I've not had any issues on any of the
cards I've got, but do we want to add them to the work-around list just to be
safe?
--
Jarod Wilson
jwilson@redhat.com
next prev parent reply other threads:[~2008-04-14 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 19:26 [PATCH] " Stefan Richter
2008-04-12 20:31 ` [PATCH update] " Stefan Richter
2008-04-14 17:30 ` Jarod Wilson [this message]
2008-04-16 10:21 ` Stefan Richter
2008-04-17 22:47 ` Stefan Richter
2008-04-18 2:51 ` Jarod Wilson
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=200804141330.22131.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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®