From: David Runge <dave@sleepmap.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Ahmed S. Darwish" <a.darwish@linutronix.de>,
linux-rt-users@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24]
Date: Sun, 14 Feb 2021 20:16:02 +0100 [thread overview]
Message-ID: <YCl28sXo7LEyCK8y@hmbx> (raw)
In-Reply-To: <20210208091940.csuyf7l73n4ofpmz@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On 2021-02-08 10:19:40 (+0100), Sebastian Andrzej Siewior wrote:
> On 2021-02-07 10:58:13 [+0100], David Runge wrote:
> > With 5.10.12-rt26 the controller still does not initialize at all
> > though (/dev/fw0 does not appear):
> > https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.10.12-rt26-kernel.log
>
> So it is either config or chipset specific. Did you posted a link to
> your .config?
The current config can be found on the AUR [1].
The equivalent mainline kernel config (note, that it states it is for
5.10.13, but is actually used for 5.10.14 as well) where initialization
of the controller works (but the initialization of a connected device
does not, when using threadirqs) is here [2].
[1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-rt
[2] https://github.com/archlinux/svntogit-packages/blob/37abf96cac628b7f516c266a8c0288671ed96a2a/trunk/config
--
https://sleepmap.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-14 19:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 11:59 firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24] David Runge
2021-01-28 6:28 ` Ahmed S. Darwish
2021-01-28 21:41 ` David Runge
2021-01-29 17:04 ` Sebastian Andrzej Siewior
2021-01-30 11:46 ` David Runge
2021-02-01 8:34 ` Sebastian Andrzej Siewior
2021-02-05 11:26 ` Sebastian Andrzej Siewior
2021-02-05 23:22 ` David Runge
2021-02-07 9:58 ` David Runge
2021-02-08 9:19 ` Sebastian Andrzej Siewior
2021-02-14 19:16 ` David Runge [this message]
2021-02-18 8:38 ` Sebastian Andrzej Siewior
2021-02-18 9:27 ` Sebastian Andrzej Siewior
2021-03-08 14:12 ` Sebastian Andrzej Siewior
2021-03-10 18:15 ` David Runge
2021-09-07 23:17 ` David Runge
2021-09-08 2:17 ` Takashi Sakamoto
2021-09-08 17:30 ` David Runge
2021-09-09 0:46 ` Takashi Sakamoto
2021-09-12 18:44 ` David Runge
2021-09-10 11:55 ` Sebastian Andrzej Siewior
2021-09-11 9:46 ` Takashi Sakamoto
2021-09-12 18:53 ` David Runge
2022-01-05 21:01 ` Holger Dehnhardt
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=YCl28sXo7LEyCK8y@hmbx \
--to=dave@sleepmap.de \
--cc=a.darwish@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).