From owner-freebsd-hackers Wed Jun 4 03:18:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA14843 for hackers-outgoing; Wed, 4 Jun 1997 03:18:54 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA14811 for ; Wed, 4 Jun 1997 03:18:40 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id MAA21043; (8.8.3/zah/2.1) Wed, 4 Jun 1997 12:57:51 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id KAA19484; (8.6.11/zah/2.1) Wed, 4 Jun 1997 10:28:50 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id MAA05574; (8.6.9/zah/1.1) Wed, 4 Jun 1997 12:14:54 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id MAA02582; Wed, 4 Jun 1997 12:07:43 +0300 (EET DST) Message-ID: <33952291.654E@cki.ipri.kiev.ua> Date: Wed, 04 Jun 1997 11:08:49 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Joerg Wunsch CC: hackers@FreeBSD.ORG, Larry Lile Subject: Re: Tropic token ring driver References: <3392FC14.41C6@stdio.com> <19970602223654.XZ56494@uriah.heep.sax.de> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Larry Lile wrote: > > > Right now I am picking up the shared ram address > > from the foo->id_maddr in the probe routine and kvtop(foo->id_maddr) > > gives the correct physical address. What I would like to do is > > pick up the address from 0x0a20 (Which after some math is usually > > either 0xcc000 or 0xdc000) and get a kvm address to it, ie the > > inverse of kvtop. > > Do you only need the KVA of it (i.e., you don't need it for things > like DMA)? If the shared memory is always in the ISA hole, there's a > fixed mapping for it (i think you need to add 0xf000000 to the > physical address). For devices that go into the higher memory area > (like PCI), you need to map it yourself anyway. > > > Also, how do you get your driver registered into the boot-up > > config? (Right now it would be helpful for debugging) > > That's still handwork, to go into /sys/i386/i386/userconfig.c. > In principle, all would be work without touching it. (in boot config you can configure misc/unknown device ) and about patching userconfig --- look on READMe to ppa3 driver: http://www.prism.uvsq.fr/~son/ppa3.html > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-)