public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Wed, 4 Oct 2023 09:24:07 +0900	[thread overview]
Message-ID: <20231004002407.GA48535@workstation.local> (raw)
In-Reply-To: <9e335ce7-a4ac-45a0-afdf-9afca8a300d5@kernel.org>

Hi Jiri,

As long as seeing your recent conversation with your reporter, it looks
to be an issue specific to the reporter's 1394 OHCI hardware. I suspect
a quirk specific to it related to accessing to CYCLE_TIME register in
early time after powering on. It is the reason that I can regenerate the
issue in my set of hardware.

Would I ask you to request the reporter to inform the detail of
hardware? If possible, let the reporter open PC box and take some picture
of the hardware so that we can identify the ICs on the hardware?

Via pci.ids, we can see both 'ASM1083/1085' and 'VT6306/7/8' are used,
while I need to identify the IC to purchase an alternative so that I can
regenerate the issue.


Thanks

Takashi Sakamoto

  reply	other threads:[~2023-10-04  0:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 12:18 [GIT PULL] firewire updates for 6.5-rc1 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26  9:11 ` Jiri Slaby
2023-09-26 14:09   ` Takashi Sakamoto
2023-09-27  5:03     ` Jiri Slaby
2023-10-01  5:15       ` Takashi Sakamoto
2023-10-02 10:42         ` Jiri Slaby
2023-10-04  0:24           ` Takashi Sakamoto [this message]
2023-10-04  8:33             ` Jiri Slaby
2023-10-16 15:56               ` Takashi Sakamoto
2023-10-17  7:36                 ` Jiri Slaby
2023-09-27 13:15   ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04     ` Linux regression tracking #update (Thorsten Leemhuis)

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=20231004002407.GA48535@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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