public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ville Herva <vherva@viasys.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1-mm2 breaks vmware
Date: Mon, 23 Aug 2004 00:19:03 +0300	[thread overview]
Message-ID: <20040822211903.GO23741@viasys.com> (raw)
In-Reply-To: <20040822143112.GB24092@vana.vc.cvut.cz>

On Sun, Aug 22, 2004 at 04:31:12PM +0200, you [Petr Vandrovec] wrote:
> 
> During weekend I was able to create binary patch for VMware Workstation
> 3.2.1 (patch available at
> http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update82.tar.gz)
> which turns that messy ioctl & /dev/mem mmap to simpler, safer and better
> /dev/vmmon mmap (and unmap + ioctl to simple unmap) (as used by
> WS4+/GSX3+).  After that WS 3.2.1 works on your 2.6.8.1-mm3 without
> problems (after applying two patches I'm sending you separately to get
> -mm3 to work at all on my notebook).

Incredible. 

I was sure I was out of look with the aged vmware 3.2.0, and now suddenly
there is patch for both the kernel and the application :).
 
> Ville, please try applying vmware-any-any-update82.tar.gz.  During
> application it must say that it found 'VMware Workstation 3.2.1-build
> 2242'.  If it will say that it found build-2230 to 2242, new binary
> pattern was not recognized and I'll need your vmware binary, as I did not
> find build 2230 in my archive. Or you can upgrade to the build 2242.

I didn't even realize 2242 had been released ;). (As I said, I've lately
been using vmware less and less.)

I just upgraded to 2242 + any2any82 and it works fine (*). I'm still using
the 2.6.8.1-mm2 with the updated dev-mem restriction patch. I'll retest this
as soon as I get to upgrade my kernel again to something that doesn't
contain Arjan's new dev-mem patch. I'll let you know.

*) Apart from that even 3.2.1 2242 does not fix the altgr key that does not
   seem to work with 2.6 new input system. I presume the new input layer is
   the reason; I do know altgr used to work with 2.4 host kernel and winxp
   guest.



-- v -- 

v@iki.fi



  parent reply	other threads:[~2004-08-22 21:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 10:42 2.6.8.1-mm2 breaks vmware Ville Herva
2004-08-20 10:51 ` Andrew Morton
2004-08-20 13:18   ` Ville Herva
2004-08-20 14:43     ` Ville Herva
2004-08-20 15:16       ` Ville Herva
2004-08-20 18:45         ` Andrew Morton
2004-08-20 18:49           ` Arjan van de Ven
2004-08-20 19:30             ` Ville Herva
2004-08-22 11:42               ` Tonnerre
2004-08-22 13:59                 ` Petr Vandrovec
2004-08-22 14:15                   ` Alan Cox
2004-08-20 19:25           ` Ville Herva
2004-08-21  6:29           ` Ville Herva
     [not found]             ` <20040821134918.GA1585@devserv.devel.redhat.com>
     [not found]               ` <20040821190027.GQ3024@viasys.com>
     [not found]                 ` <20040821190730.GA25932@devserv.devel.redhat.com>
2004-08-22 14:31                   ` Petr Vandrovec
2004-08-22 15:07                     ` Arjan van de Ven
2004-08-22 21:19                     ` Ville Herva [this message]
2004-08-23  5:53                       ` [OT] vmware, 2.6 kernel and altgr key (Re: 2.6.8.1-mm2 breaks vmware) Ville Herva
2004-08-20 12:11 ` 2.6.8.1-mm2 breaks vmware Arjan van de Ven

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=20040822211903.GO23741@viasys.com \
    --to=vherva@viasys.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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