From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bitsy bootldr
Date: Wed, 30 Oct 2002 12:47:22 +0100 [thread overview]
Message-ID: <0272c012080310ebcd3b6576a3c4cf92@plan9.escet.urjc.es> (raw)
> I added the offset of the fields in the comment.
> Shouldn't there be a ``hole /* 0x0c */'' between trim and status?
Hmm. Not sure, but if there's a hole there, then that's the bug that
prevents me from sending RTC interrupts, ugh.
> I added a ``ulong hole;'' in between, set rtar to 0x05
> in clockinit() (next to setting of rttr and rcnr fields)
> and saw the debug print statement of clockintr many many times.
thanks a lot. I'm an idiot. We can probably wake up the bitsy while
suspended with your fix.
> 2) I'm trying to understand (a bit) mapspecial.
> is its parameter the register size in bytes?
Yes. Unless I'm very mistaken.
> Reason I'm asking is that I noticed that this parameter
> is hardcoded in many places (which seems potentially dangerous?)
> (see example below, isn't sizeof(MemConfRegs) > 32?)
The map is done in mmu.c by _map(). Probably it's being mapped
anyway. But I think that's just another bug you've found.
> Just wondering: is there a stylistic or other reason to use
> the numbers, instead of e.g. using sizeof?
I think it'd be better to use sizeof.
Now that you've found the stupid reason why I didn't get rtc interrupts
I'll try to build a new kernel soon and fix those things to see what
happens.
If you do it before I could, it'd be great to merge our versions.
I wouldn't like to end up with three different versions of the bitsy
kernel.
thanks a lot.
next reply other threads:[~2002-10-30 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 11:47 Fco.J.Ballesteros [this message]
2002-10-30 12:42 ` Axel Belinfante
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 13:40 Fco.J.Ballesteros
2002-10-30 8:20 Fco.J.Ballesteros
2002-10-30 11:10 ` Axel Belinfante
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=0272c012080310ebcd3b6576a3c4cf92@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).