From: <jasper.lowell@bt.com>
To: <balaton@eik.bme.hu>
Cc: jsnow@redhat.com, mark.cave-ayland@ilande.co.uk, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/ide: Remove status register read side effect
Date: Wed, 4 Mar 2020 00:58:20 +0000 [thread overview]
Message-ID: <2eaad5b9fffb507a1dfabedcfb6c249d7c291353.camel@bt.com> (raw)
In-Reply-To: <alpine.BSF.2.22.395.2002271235120.21840@zero.eik.bme.hu>
I'm happy to do this. It will take a while for me to collect the
results though. I'll chime in once I have the results.
> That should give the ultimate answer to our guessing.
Agreed.
Thanks,
Jasper Lowell.
On Thu, 2020-02-27 at 12:38 +0100, BALATON Zoltan wrote:
> On Thu, 27 Feb 2020, jasper.lowell@bt.com wrote:
> > I've since looked at a Ultra 5 board and can confirm that it
> > shipped
> > with a CMD646U chip like the Ultra 10.
>
> If you have access to an Ultra 5 maybe you could try testing what it
> does
> with irqs. That should give the ultimate answer to our guessing. It
> may
> need patching a Linux driver to log more info and recompile the
> kernel so
> not sure you have time for that but maybe it would help if you can do
> it.
>
> Regards,
> BALATON Zoltan
next prev parent reply other threads:[~2020-03-04 0:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 6:50 [PATCH] hw/ide: Remove status register read side effect jasper.lowell
2020-02-21 8:08 ` no-reply
2020-02-21 15:43 ` BALATON Zoltan
2020-02-22 2:07 ` jasper.lowell
2020-02-22 11:47 ` BALATON Zoltan
2020-02-22 17:50 ` BALATON Zoltan
2020-02-22 19:26 ` BALATON Zoltan
2020-02-22 19:32 ` Mark Cave-Ayland
2020-02-22 19:45 ` BALATON Zoltan
2020-02-22 20:05 ` BALATON Zoltan
2020-02-23 7:23 ` jasper.lowell
2020-02-23 15:16 ` BALATON Zoltan
2020-02-25 3:55 ` jasper.lowell
2020-02-25 15:08 ` BALATON Zoltan
2020-02-26 5:22 ` jasper.lowell
2020-02-26 11:07 ` BALATON Zoltan
2020-02-27 5:10 ` jasper.lowell
2020-02-27 5:56 ` jasper.lowell
2020-02-27 11:35 ` BALATON Zoltan
2020-03-04 0:55 ` jasper.lowell
2020-02-27 11:38 ` BALATON Zoltan
2020-03-04 0:58 ` jasper.lowell [this message]
2020-03-01 18:02 ` BALATON Zoltan
2020-03-04 3:11 ` jasper.lowell
2020-03-04 8:48 ` BALATON Zoltan
2020-03-04 21:07 ` Mark Cave-Ayland
2020-03-05 0:47 ` jasper.lowell
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=2eaad5b9fffb507a1dfabedcfb6c249d7c291353.camel@bt.com \
--to=jasper.lowell@bt.com \
--cc=balaton@eik.bme.hu \
--cc=jsnow@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).