home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!alpha.ces.cwru.edu!seshadri
- From: seshadri@ces.cwru.edu (Krishna Seshadri)
- Newsgroups: comp.unix.internals
- Subject: Re: HELP: kernel routines for device driver
- Date: 17 Dec 1992 04:24:07 GMT
- Organization: Computer Engineering and Science/CWRU
- Lines: 27
- Message-ID: <1govd7INN46n@usenet.INS.CWRU.Edu>
- References: <522@aldetec.oz.au> <144400004@hpcupt3.cup.hp.com>
- NNTP-Posting-Host: mapping.ces.cwru.edu
-
- In article <144400004@hpcupt3.cup.hp.com> sbmn@hpcupt3.cup.hp.com (S.Subramanian(contr)) writes:
- >/ hpcupt3:comp.unix.internals / hausler@aldetec.oz.au (Graham Hausler) / 12:45 am Nov 20, 1992 /
- >> 1. Can I access physical memory (not in IO space) directly from a
- >> device driver, assumming I have removed this memory from usage by unix?
- >> I want the physical memory at a fixed address, and hence cannot
- >> allocate in virtual address space and then derive the physical address
- >> (assuming I can even manage that !!)
- >
- >If your kernel has a sptalloc() / ptalloc() routine, you can make use of it.
- >It takes a base physical address maps it to a kernel virtual address and
- >returns this address.
-
-
-
- All you need to do is choose a physical address range (not used by
- UNIX) and plunk in a value in the TTRs (Transparent Translation
- Registers) so that the physical addresses are directly accessible from
- the driver. Pretty cool. I am assuming of course that you are using a
- 68040...
-
- Krishna
-
- --
-
- seshadri@alpha.ces.cwru.edu | A bachelor is a selfish,
- kps2@po.cwru.edu | undeserving guy who has cheated
- Work: (216)-368-5038 | some poor woman out of a divorce.
-