All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Huacai Chen <chenhuacai@kernel.org>, John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, Guenter Roeck <linux@roeck-us.net>,
	f4bug@amsat.org
Subject: Re: [PATCH v2 2/2] via-ide: Fix fuloong2e support
Date: Tue, 29 Dec 2020 12:49:08 +0000	[thread overview]
Message-ID: <454e0750-7141-6daf-7917-259b2cb77cfa@ilande.co.uk> (raw)
In-Reply-To: <bc626ee4-f748-f1f-9a60-2477c35f752@eik.bme.hu>

On 29/12/2020 12:01, BALATON Zoltan via wrote:

>> Fortunately with PCI_CLASS_PROG at 0x8a Linux will keep the VIA IDE in compatible 
>> mode and not attempt to switch to native mode: therefore if you keep this as-is and 
>> add the legacy IDE ioports back, that just leaves the problem with BAR4 (BMDMA). In 
>> effect your patch isn't setting compatible mode anymore, it is just disabling BMDMA.
> 
> It's actually Guenter's patch so you're now bashing him not me...

This is a deliberately misleading comment, and not a good introduction for someone 
external becoming involved with the project. Guenter's patch was a PoC demonstrating 
how to fix the fuloong2e machine, which is really appreciated since it clearly 
locates the problems to allow a fix to be applied upstream.

> (But I also think your time could be better spent than getting rid of this hack when 
> there are much more hacks or missing functionalities to get rid of in the part you 
> maintain.)

And comments like this are not appropriate for a technical mailing list either. I've 
done my best to review your patch in good faith (including reading related 
specifications and testing your pegasos2 model) and explain why it isn't reporting 
the correct information to the guest.

Phil - I hope you find that found my review comments useful and that they explain why 
the patchset is wrong by always claiming legacy IDE ioports exist but not providing 
them unless the new option is set (and indeed indicating some of the shortcomings of 
QEMU related to PCI BARs in this area that can be improved in future). As I feel 
comments in this thread have become directed at me personally, I am going to take a 
step back from this.


ATB,

Mark.


  reply	other threads:[~2020-12-29 12:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 22:13 [PATCH v2 0/2] Fix via-ide for fuloong2e BALATON Zoltan via
2020-12-27 22:13 ` [PATCH v2 2/2] via-ide: Fix fuloong2e support BALATON Zoltan via
2020-12-28 12:27   ` Jiaxun Yang
2020-12-28 19:43   ` Mark Cave-Ayland
2020-12-28 20:50     ` BALATON Zoltan via
2020-12-29 10:56       ` Philippe Mathieu-Daudé
2020-12-29 11:35         ` BALATON Zoltan via
2020-12-29 11:24       ` Mark Cave-Ayland
2020-12-29 12:01         ` BALATON Zoltan via
2020-12-29 12:49           ` Mark Cave-Ayland [this message]
2020-12-29 14:10             ` BALATON Zoltan via
2020-12-29 11:43       ` Mark Cave-Ayland
2020-12-29 12:07         ` BALATON Zoltan via
2020-12-27 22:13 ` [PATCH v2 1/2] ide: Make room for flags in PCIIDEState and add one for legacy mode BALATON Zoltan via
2020-12-28 19:30   ` Mark Cave-Ayland
2020-12-28 20:23     ` BALATON Zoltan via
2020-12-29 10:52     ` Philippe Mathieu-Daudé

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=454e0750-7141-6daf-7917-259b2cb77cfa@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=balaton@eik.bme.hu \
    --cc=chenhuacai@kernel.org \
    --cc=f4bug@amsat.org \
    --cc=jsnow@redhat.com \
    --cc=linux@roeck-us.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.