9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Dorman eld@jewel.ucsd.edu
Subject: [9fans] Plan9 commercial licenses
Date: Tue, 30 Sep 1997 14:45:53 -0700	[thread overview]
Message-ID: <19970930214553.-1GsPPIXi6HhvWQV8_5Jv4WpuKjcheuGgB4wyvQp5yE@z> (raw)


> 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
> 





             reply	other threads:[~1997-09-30 21:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-30 21:45 Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-10-01  7:45 elliott
1997-09-30 21:19 jmk
1997-09-30 21:07 Eric
1997-09-30 20:02 Eric
1997-09-30 19:56 jmk
1997-09-30 19:11 Scott
1997-09-30 19:09 David
1997-09-30 18:44 Eric
1997-09-30 18:20 Scott
1997-09-30 16:41 Eric
1997-09-30 16:23 Frank
1997-09-30 15:14 G.David

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19970930214553.-1GsPPIXi6HhvWQV8_5Jv4WpuKjcheuGgB4wyvQp5yE@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).