9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] patch for installation in vmware
Date: Wed, 23 Jul 2008 11:43:55 +0200	[thread overview]
Message-ID: <ba0d3bc70807230243k6bbbdef6qe47a9b73bc43bc1b@mail.gmail.com> (raw)
In-Reply-To: <5d375e920807200555v5b21196pe2a25bd740c830f@mail.gmail.com>

On 7/20/08, Uriel <uriel99@gmail.com> wrote:
> I thought I had submitted a patch for this a while ago (which as
> accepted), but maybe I missed the installer. In any case, using
> patch(1) will have a better chance of getting in.

I believe the best solution would be to change /sys/lib/dist/pc/sub/vmware from

    #!/bin/rc

    if(aux/isvmware -s){
           echo -n off >'#P/i8253timerset'
           for(i in '#S'/sd??)
                   if(test -f $i/ctl)
                           echo dma on >$i/ctl
    }

to

    if(aux/isvmware -s){
           echo -n off >'#P/i8253timerset'
           echo hwaccel off >'#v/vgactl'
    }

That is, add the line that disables hardware acceleration, and remove the lines that set dma on (this is handled by /sys/lib/dist/pc/sub/termrc already).

I do have one question though: when setting dma on, /sys/lib/dist/pc/sub/termrc iterates over /dev/sd*/ctl, while /sys/lib/dist/pc/sub/vmware iterates over '#S'/sd??; is there a specific reason vmware needs to use '#S' rather than /dev? (Or to formulate the question a bit different: I'd expect that '#S' is bound to /dev at that point regardless of whether we're using vmware or not; is this correct?)

Greetings, Sander.



      reply	other threads:[~2008-07-23  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 20:07 Antonin Vecera
2008-07-19  7:30 ` Sander van Dijk
2008-07-19 13:50   ` Russ Cox
2008-07-19 15:48     ` Sander van Dijk
2008-07-20  8:11       ` Sander van Dijk
2008-07-20 12:55 ` Uriel
2008-07-23  9:43   ` Sander van Dijk [this message]

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=ba0d3bc70807230243k6bbbdef6qe47a9b73bc43bc1b@mail.gmail.com \
    --to=a.h.vandijk@gmail.com \
    --cc=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).