From: Blue Swirl <blauwirbel@gmail.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: target-sparc/TODO
Date: Fri, 20 Aug 2010 20:19:17 +0000 [thread overview]
Message-ID: <AANLkTimH94RCPoofHpb0d3mt=qmVVTubjW+R5PJjfAFy@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin2_q0204btRyg_x0HtEMFSGT8rAAMVN7KoY1u7@mail.gmail.com>
On Fri, Aug 20, 2010 at 7:59 PM, Artyom Tarasenko
<atar4qemu@googlemail.com> wrote:
> 2010/8/19 Blue Swirl <blauwirbel@gmail.com>:
>
>>> Is there a list of what is missing? You mentioned the pci bridges
>>> before. What else?
>>> Shall we maintain the TODO file for everything we find? Including
>>> things we may fix within a few days after finding?
>>
>> Actually, we have a TODO file, see under target-sparc. Thanks for
>> reminding me. ;-)
>
> I know that we have it. I asked you about a year ago whether the
> things in it were up to date. ;-)
Yes, but I had sort of forgotten.
> What I mean is that we should update it really every time we find or
> fix missing things. For example my current list of sun4m
> features/fixes which may or may not be implemented in the near or far
> future:
>
> - esp: improve "Select with Attention" / "Select without Attention",
> so that it's compatible with NetBSD 1.6-3.0.
bug
> - mxcc: implement missing registers so that SS-10/SS-20 OBPs would
> work with the default CPU model
bug?
> - le: improve for passing OBP loopback test. This would allow the
> network boot (which is the default option for OBP when running under
> qemu because NVRAM contents is invalid).
bug or feature, I don't know
> - nvram: add possibility to back it up with a file.
feature
> - add option rom file load for graphic card or for any SBus slot (the
> second variant is preferable because it can be used to provide SS-20
> OBP with fake or real dbri rom).
feature
> - slavio_timer: make it closer to the real HW than to specification.
> NeXTStep OS relies on register contents after the mode change although
> the documentation states it to be undefined.
bug
> - fix Solaris 2.2-2.5.1 boot hanging if the day of month is >20 (am
> currently at it).
bug?
>
> the list is unsorted. The "option rom file" point is already in the
> TODO file but without reasoning.
I think small bugs could be reported to the bugzilla and only new
features (and maybe bugs that need a big fix) should be added to TODO.
> I think one point in the current TODO is resolved:
>
> - Interrupt routing does not match real HW
>
> I think we are pretty good there at least for the single CPU machines.
This was probably from the time that CPU timer interrupts were
delivered with the IRQ bit (0x80 in the master register) that Linux
used to clear the interrupt which was not correct.
Level 15 handling may still be incorrect and as you reported, IOMMU
probably is too trigger happy with NMI which may not even be the
correct IRQ. Likewise with unassigned_mem.
next prev parent reply other threads:[~2010-08-20 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 19:59 [Qemu-devel] target-sparc/TODO Artyom Tarasenko
2010-08-20 20:19 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-17 10:52 Artyom Tarasenko
2009-08-17 17:35 ` [Qemu-devel] target-sparc/TODO Blue Swirl
2009-08-19 10:17 ` Artyom Tarasenko
2009-08-19 16:43 ` Blue Swirl
2009-08-20 9:44 ` Artyom Tarasenko
2009-08-20 19:15 ` Blue Swirl
2009-08-21 9:58 ` Artyom Tarasenko
2009-08-21 12:40 ` Artyom Tarasenko
2009-08-21 19:45 ` Blue Swirl
2009-08-21 21:01 ` Artyom Tarasenko
2009-08-21 21:10 ` Igor Kovalenko
2009-08-21 21:17 ` Artyom Tarasenko
2009-08-22 6:51 ` Blue Swirl
2009-08-22 12:40 ` Artyom Tarasenko
2009-08-22 13:30 ` Robert Reif
2009-08-22 17:25 ` Artyom Tarasenko
2009-08-22 18:46 ` Robert Reif
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='AANLkTimH94RCPoofHpb0d3mt=qmVVTubjW+R5PJjfAFy@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=atar4qemu@googlemail.com \
--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).