public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.25-rc2: ohci1394 problem
Date: Mon, 25 Feb 2008 19:23:26 +0100	[thread overview]
Message-ID: <47C3079E.9080309@m3y3r.de> (raw)
In-Reply-To: <47C05A51.7000209@s5r6.in-berlin.de>

Stefan Richter schrieb:
>
> My conclusion so far:  There is something wrong with your system which 
> is below/ before the control of the ieee1394 or firewire stack.
Yes. I agree with you. So i did a "make clean" and a "make" (not a make 
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works again. 
Case closed under strange error. Thanks for your support.
>
> BTW, there was a single change to ohci1394 after v2.6.24 and that does 
> not affect the initialization code of ohci1394.  (Patch name is 
> "ieee1394: ohci1394: don't schedule IT tasklets on IR events".)  Did 
> you ever use kernels before 2.6.25-rc2 and had both of ohci1394 and 
> firewire-ohci inserted?
Yes. 2.6.24 works with the same config, i.e. both drivers are build as 
modules.

mfg
thomas


  reply	other threads:[~2008-02-25 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  7:47 2.6.25-rc2: ohci1394 problem Thomas Meyer
2008-02-20  9:48 ` Stefan Richter
2008-02-20 17:53   ` Thomas Meyer
2008-02-20 18:15     ` Stefan Richter
2008-02-20 18:18       ` Stefan Richter
2008-02-23 16:53         ` Thomas Meyer
2008-02-23 17:39           ` Stefan Richter
2008-02-25 18:23             ` Thomas Meyer [this message]
2008-02-25 18:58               ` Stefan Richter
2008-02-25 19:07                 ` 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=47C3079E.9080309@m3y3r.de \
    --to=thomas@m3y3r.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