From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200210301242.g9UCgPL04637@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] bitsy bootldr In-reply-to: Your message of "Wed, 30 Oct 2002 12:47:22 +0100." <0272c012080310ebcd3b6576a3c4cf92@plan9.escet.urjc.es> References: <0272c012080310ebcd3b6576a3c4cf92@plan9.escet.urjc.es> From: Axel Belinfante Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Oct 2002 13:42:25 +0100 Topicbox-Message-UUID: 11f3c4f8-eacb-11e9-9e20-41e7f4b1d025 > > 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 to repeat: there are _many_ places with hardcoded numbers, and for example, with ``hole'' added, also the rtc clock regs gets too big (but it is in the OneMeg range of 0x9000whatever, so probably gets mapped anyway). > 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. I played a bit, but what I did did not ``magically'' make suspend/resume work (I even browsed Intel's SA1100 doc, but really don't know enough about these things). I think it's best if I wait for your work, try it, and if it works, fold in the (somewhat revised) dual pcmcia hacks, and see what happens then. (do we also have to think about sleeve support in general -- sleeve identification, software concept of sleeve as they have in bootldr and probably also in linux? or can it just be (hidden) part of the pcmcia card support etc. ) FYI: On friday I will be going on a one-and-half weeks vacation in (of all places) Spain, during which I won't have net.access (so, don't hurry only for my sake -- unless you would be able to build something to play with before/during thursday evening :-)