home *** CD-ROM | disk | FTP | other *** search
- Niklas Hallqvist <niklas@appli.se> wrote:
-
- > >>>>> "Markus W" == Markus Wild <mw@eunet.ch> writes:
-
- > Niklas> A2000. I also established that it is non-interlace that is the
- > Niklas> culprit when you get a steady grey or blue screen. I put interlace
- > Niklas> in my
-
- > Markus W> This is awefully strange.. Although I do install an
- > Markus W> interlaced copperlist, I thought I set up anything to have
- > Markus W> this working from any possible previous screen
- > Markus W> mode. Hmm.. perhaps some custom chip register not
- > Markus W> initialized that makes the machine lockup if an interlaced
- > Markus W> display is installed without updating that register?
-
- > Your first display driver did not have this problem (you know the one
- > that thrashed the font for some of us). Maybe that fact helps.
-
- I finally tried booting netbsd in interlace mode and it works. I
- still have problems trying to explain why none of the background color
- changesI attempted after enabling the MMU worked. Markus, reading
- through the code, the custom chip registers are mapped pa==va, aren't
- they? I'm just poking a value into 0xdff180. Maybe you should take a
- look into this.
-
- BTW, how do you create /dev/reboot? What are the major and minor
- device numbers?
-
- =========================================================================
- Eduardo Horvath eeh@btr.com
- ..!{decwrl,mips,fernwood}!btr!eeh
- "Trust me, I am cognizant of what I am doing." - Hammeroid
-
-
-