From owner-freebsd-hackers  Fri Aug  1 21:02:07 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA00383
          for hackers-outgoing; Fri, 1 Aug 1997 21:02:07 -0700 (PDT)
Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA00376
          for <FreeBSD-Hackers@FreeBSD.ORG>; Fri, 1 Aug 1997 21:02:00 -0700 (PDT)
Received: (qmail 12998 invoked by uid 1000); 2 Aug 1997 04:02:15 -0000
Message-ID: <XFMail.970801210215.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199708020326.MAA08876@genesis.atrad.adelaide.edu.au>
Date: Fri, 01 Aug 1997 21:02:15 -0700 (PDT)
Organization: Atlas Telecom
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Subject: Re: Kernel howto, Second Request
Cc: FreeBSD-Hackers@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Michael Smith;  On 02-Aug-97 you wrote: 

> Simon Shapiro stands accused of saying:
> [Charset iso-8859-8 unsupported, filtering to ASCII...]
> > Old, unanswered question:
> 
> I responded to these.  Let me know if you didn't get the rsponse, but
> more importantly _why_ do you want them?  

I didn't get the response :-(
I do not want these.  I need them.  The DPT raid manager requires these.
They do not do anything dramatic with them, but the application (originally
DOS) expects them in reply to an IOCTL.  

> > Next Question:  What is the equivalent of SysV physmap()?
> >     Physmap takes a physical memory address and returns a virtual
> address.
> > I am trying to access certain memory location only known by physical
> > addresses.
> 
> Are you trying to perform this operation in userspace or in the
> kernel?  Do you know the the physical address range in question has
> been mapped yet?  If it has, by whom?  If not, then you will need to
> establish a mapping, which will give you this information.

Kernel, of course.  The addresses are all BIOS data pages and the DPT
BIOS and firmware addresses.  The code is really, really not portable
(I am being very kind with my words here :-)  If I an have the values
for the struct, I will gladly avoid writing all these nasty inb/outb
and funny memory accesses.

I really do not knowif this memory has been mapped or not.  What I need
to do is probe certain location, in BIOS ranges for certain signatures.
This probing should not be destructive.

Simon