Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!cgs
From: cgs@umd5.umd.edu (Chris G. Sylvain)
Newsgroups: comp.os.minix
Subject: readclock (v1.5.10)
Keywords: broke, (unsigned), CPU_TYPE_SEGMENT
Message-ID: <7373@umd5.umd.edu>
Date: 29 Sep 90 02:54:26 GMT
Organization: University of Maryland, College Park
Lines: 19


'scuse me -- who's got a working readclock on their pcAT?

Mine wouldn't even identify PC_AT properly until I cast the constant
CPU_TYPE_SEGMENT (== 0xFFFF) to 'unsigned'. Yes, I have /dev/port ..
MINIX crashes somewhere in port_out() when running in protected mode.

I looked over kernel/memory.c very carefully, and it seems just fine.
I'm stumped. Who's got an idea where to go from here?

PS: not all the lseek()s in portio and peekpoke use SEEK_SET, some still
    use a bare '0' as a parameter. For that matter, sometimes the
    read() or write() count parameter isn't (size_t), but is (unsigned)
    instead. In other words, it's sorta ANSI-fied, but not consistently.
-- 
--==---==---==--
Toves: Animals something like badgers, lizards, and corkscrews
--   ARPA: cgs@umd5.UMD.EDU     BITNET: cgs%umd5@umd2   --
--   UUCP: ..!uunet!umd5.umd.edu!cgs                    --