From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 30 Sep 1997 14:45:53 -0700
From: Eric Dorman eld@jewel.ucsd.edu
Subject: [9fans] Plan9 commercial licenses
Topicbox-Message-UUID: 6782271e-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19970930214553.-1GsPPIXi6HhvWQV8_5Jv4WpuKjcheuGgB4wyvQp5yE@z>


> From: jmk@plan9.bell-labs.com
> Date: Tue, 30 Sep 1997 17:19:28 -0400
> Subject: Re: [9fans] Plan9 commercial licenses
> 
> 	[ I'll have to think hard about hacking mmu.c :) .. You're probably
> 	[ right about it being good to force the cards to some base address
> 	[ rather than accepting what PCI autoconf gave us.
> 
> i know this doesn't do you any good (i wish it did) but 10 minutes ago
> i finished hacking the mmu code to let us map the pci devices where the
> bios leaves them. you're pretty much forced to do that if you have pci
> bridges. 

Actually it's good food for thought.  I hadn't thought about bridges
and how they are referred to.  I've been (perhaps unwisely) avoiding
staring real hard at pci as it seems one has to pay for a copy of
the spec.  If it were $25us it wouldn't bug me, but the only thing
i've seen is $100, which is enough to slow me down a bit :)

> the brazil code also has to deal with synchronising the changes to the
> kernel mappings for multiple processors and it still doesn't use 
> interprocessor interrupts.

? Hmm thot one would have to force the cpus to reload their page
tables when they were changed by other cpus, but I'm not sure how 
much table state the average P5 or P6 keeps on-chip.

> --jim
>