*BSD News Article 15381


Return to BSD News archive

Xref: sserve comp.os.os2.programmer:11333 comp.os.linux:36708 comp.os.mach:2825 comp.os.minix:22042 comp.periphs:3589 comp.unix.bsd:11941 comp.unix.pc-clone.32bit:2560 comp.os.386bsd.development:634
Newsgroups: comp.os.os2.programmer,comp.os.linux,comp.os.mach,comp.os.minix,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!decwrl!netcomsv!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: RFD on RTC (Real Time Clock) MC146818
Message-ID: <jmonroyC6A8t3.572@netcom.com>
Keywords: RTC Real time clock  
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
Date: Fri, 30 Apr 1993 06:03:02 GMT
Lines: 60

 
                Call For Development on RTC (Real Time Clock)
                --------------------------------------------
 
                PLEASE
                ------
                Please don't add to this and make it a thread.
                E-MAIL ME.
 
                What?
                -----
                This is a call for help on development on a RTC device
        driver for UNIX type systems.  The driver will be modular and
        transportable in form.  I would like to GAS (ouu) and ANSI-C.
 
                Who?
                ----
                I don't know what the needs of each group on the net.
        If you feel that the driver you have works well, then there
        is no need to write me.  If you need a better hook into this
        piece of hardware then, e-mail me (jmonroy@netcom.com).
 
                How?
                ----
                I may not have all the information I need, so if you
        feel there is some technical information I need, then by all
        means inform me.  If you know of any code that may apply, please
        let me know about it and a location for it, if you can.
 
                Why?
                ----
                I need a precision 1Khz alarm clock for the QIC-40/80.
        A "dead loop" will not work with current hardware limitations.
        A hardware clock is needed.
 
                Why me?
                -------
                If, you feel that maybe someone else is more capable than
        I please let me know.  I do not want to be considered a project
        hog.    I am will to let *ANYONE* else do this.
 
 
                Anything else?
                --------------
                Yes, but I have wasted too much bandwidth already. If
        you want to monitor this project watch comp.periphs for a
        newsletter. (Crowd: Yeah!)  It will not be like QIC NEW,
        but it will be similar.  QIC NEWS will contain notes on this
        effort but QIC NEWS will not go into depth.
 
 
 
                Thank you for your attention.
 
 
___________________________________________________________________________
Jesus Monroy Jr                                          jmonroy@netcom.com
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________