From: quan <qeed.quan@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, Bernhard Beschow <shentey@gmail.com>,
philmd@linaro.org
Subject: Re: Using parallel port on the Pegasos 2
Date: Sun, 28 Jul 2024 15:59:32 -0500 [thread overview]
Message-ID: <CACUh7aGb7pQUAyWSj8UuWaYJVA8ZYs1HAM0kUsQ736K-mLLHeQ@mail.gmail.com> (raw)
In-Reply-To: <e8832eee-01fe-4cef-d6c4-31fb63677d5c@eik.bme.hu>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
I have tried this on qemu 8.2.0 (I downloaded it and compiled with
--enable-debug), this build does not seem to hit the breakpoint
portio_write function when writing to 0x3bc while it does on the latest
qemu git version.
Using the trace:memory_region_ops_write option for 8.2.0, the other
devices like serial and rtc does get hit, but it never prints a write for
'parallel', as if its disabled somehow.
Quan
On Sun, Jul 28, 2024 at 2:17 PM BALATON Zoltan <balaton@eik.bme.hu> wrote:
> On Sun, 28 Jul 2024, quan wrote:
> > I am playing around with the parallel port on the pegasos 2 and I noticed
> > the following issue:
> > The parallel port on startup is set to iobase 0x378, then later it gets
> > remapped to iobase 0x3bc.
> > When I tried writing to the 0x3bc location with
> > trace:memory_region_ops_write on, I get logs about writing to the
> location
> > 'parallel', so far so good, but the writes don't make it through (it
> never
> > calls parallel_ioport_write* functions)
> >
> > I traced it through where it calls portio_write, and inside the
> > portio_write code:
> > This line always fails for me:
> > const MemoryRegionPortio *mrp = find_portio(mrpio, addr, size, true);
> > This is due to the mrpio has the offset of 0x44 (0x3bc-0x378) in the
> list,
> > and the 'addr' in the code ranges from (0-15) (address relative to
> 0x3bc),
> > so it can never match the parallel io function to execute.
> >
> > This seems like a bug to me. I think there is some issue where the
> > portio_list is not getting updated properly after the remapping to 0x3bc.
> >
> > The other devices (Serial, RTC, PM, VGA) responds properly for me, so it
> is
> > only the parallel port that has this issue.
>
> Is this something that broke recently or can the same be reproduced with
> QEMU v8.2.0. The relocation of these devices was implemented around commit
> 35a6380b4ed27f (and the ones before that). Adding Bernhard to cc as well.
>
> Regards,
> BALATON Zoltan
>
[-- Attachment #2: Type: text/html, Size: 2473 bytes --]
next prev parent reply other threads:[~2024-07-28 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 14:59 Using parallel port on the Pegasos 2 quan
2024-07-28 19:17 ` BALATON Zoltan
2024-07-28 20:59 ` quan [this message]
2024-07-28 22:33 ` BALATON Zoltan
2024-07-28 22:43 ` quan
2025-05-25 0:03 ` BALATON Zoltan
2025-05-26 9:59 ` Bernhard Beschow
2025-05-26 11:47 ` BALATON Zoltan
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=CACUh7aGb7pQUAyWSj8UuWaYJVA8ZYs1HAM0kUsQ736K-mLLHeQ@mail.gmail.com \
--to=qeed.quan@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.com \
/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).