From: Christian Kujau <evil@g-house.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: ohci1394: aborting transmission
Date: Mon, 10 Jul 2006 08:55:46 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0607100852390.13858@sheep.housecafe.de> (raw)
In-Reply-To: <44B203F4.1030903@s5r6.in-berlin.de>
On Mon, 10 Jul 2006, Stefan Richter wrote:
> Perhaps you should add a printk at the beginning of input's init
> function. The delay could happen during the startup of the input layer
> instead of the 1394 drivers.
yeah, I'll try to do this later on....getting some sleep first...
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm6/
> and start bisecting within the set of 1394 patches. Among them, the
> patches to sbp2, dv1394, and raw1394 are unrelated to the problem. Note
> that "origin.patch" touches drivers/ieee1394/ too.
OK, thanks for the hint.
> The VIA VT6306 OHCI controller which you have according to your lspci
> output is known to work; yours doesn't even have the small quirk
> mentioned in http://www.linux1394.org/view_device.php?id=713 .
yes, it worked before with no delay and even now all seems to be
fine after the delay....
Thanks,
Christian.
--
BOFH excuse #193:
Did you pay the new Support Fee?
next prev parent reply other threads:[~2006-07-10 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 4:29 Christian Kujau
2006-07-10 7:38 ` Stefan Richter
2006-07-10 7:55 ` Christian Kujau [this message]
2006-07-10 13:19 ` Stefan Richter
2006-07-12 12:02 ` [x86_64] strange delays since 2.6.15 (was: Re: ohci1394: aborting transmission) Christian Kujau
2006-07-12 21:01 ` Christian Kujau
2006-07-12 21:14 ` Kay Sievers
2006-07-13 3:36 ` Christian Kujau
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=Pine.LNX.4.64.0607100852390.13858@sheep.housecafe.de \
--to=evil@g-house.de \
--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®