From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] Fix IDE commands issued, fix endian issues, fix non MMIO
Date: Mon, 19 Apr 2021 13:52:47 +0200 [thread overview]
Message-ID: <23bedbed-75dd-1b2f-dbf6-8aeb62583e57@gmx.de> (raw)
In-Reply-To: <YDbLO72XgMRMurGZ@dropje.13thmonkey.org>
On 24.02.21 22:55, Reinoud Zandijk wrote:
> Dear Heinrich,
>
> On Wed, Feb 24, 2021 at 06:57:08PM +0100, Heinrich Schuchardt wrote:
>> On 24.02.21 17:44, Reinoud Zandijk wrote:
>>>
>>> Fixes IDE issues found on the Malta board under Qemu:
>>>
>>> 1) DMA implied commands were sent to the controller in stead of the PIO
>>> variants. The rest of the code is DMA free and written for PIO operation.
>>>
>>> 2) direct pointer access was used to read and write the registers instead
>>> of the inb/inw/outb/outw functions/macros. Registers don't have to be
>>> memory mapped and ATA_CURR_BASE() does not have to return an offset from
>>> address zero.
>>>
>>> 3) Endian isues in ide_ident() and reading/writing data in general. Names
>>> were corrupted and sizes misreported.
>>
>> It is preferable to have each issue fixed in a separate patch.
>
> They are related; 2 and 3 are really one and 1 could in theory be separate but
> it won't work on its own.
Thanks for the background.
>
>>> Tested malta_defconfig and maltael_defconfig to work again in Qemu.
>>
>> What about the other architectures which can use the driver?
>
> As for testing, I compile tested an ARM board, edminiv2, successfully, but
> don't know how to invoke qemu for it. As for running the tests, my setup is
> not capable of running the tests since they seem to be for linux only.
>
> Does the automatic testing check if disks are indeed found correctly and
> checking reading or writing to a disk image?
qemu-x86_64_defconfig and qemu-x86_defconfig have CONFIG_CMD_IDE=y.
Actually without your patch qemu-x86 cannot read the partition table
from an IDE device. With your patch it works fine.
This was my QEMU command:
qemu-system-i386 -bios u-boot.rom -nographic sct-i386.img
Tested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
next prev parent reply other threads:[~2021-04-19 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:44 [PATCH] Fix IDE commands issued, fix endian issues, fix non MMIO Reinoud Zandijk
2021-02-24 17:57 ` Heinrich Schuchardt
2021-02-24 19:41 ` Tom Rini
2021-02-24 21:55 ` Reinoud Zandijk
2021-04-16 13:42 ` Reinoud Zandijk
2021-04-19 9:44 ` Reinoud Zandijk
2021-04-19 11:52 ` Heinrich Schuchardt [this message]
2021-04-20 14:19 ` Tom Rini
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=23bedbed-75dd-1b2f-dbf6-8aeb62583e57@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=u-boot@lists.denx.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