Date: Wed, 04 Jun 1997 11:08:49 +0300 From: Ruslan Shevchenko <rssh@cki.ipri.kiev.ua> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: hackers@FreeBSD.ORG, Larry Lile <lile@stdio.com> Subject: Re: Tropic token ring driver Message-ID: <33952291.654E@cki.ipri.kiev.ua> References: <3392FC14.41C6@stdio.com> <19970602223654.XZ56494@uriah.heep.sax.de>
index | next in thread | previous in thread | raw e-mail
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. ;-)
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33952291.654E>