From owner-freebsd-questions@FreeBSD.ORG Tue Mar 18 21:24:55 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E154E106566C for ; Tue, 18 Mar 2008 21:24:54 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.186]) by mx1.freebsd.org (Postfix) with ESMTP id 699D18FC1E for ; Tue, 18 Mar 2008 21:24:54 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by gv-out-0910.google.com with SMTP id n40so68558gve.39 for ; Tue, 18 Mar 2008 14:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=W/KNVSQfztOnq4EhCMztpIKzfC0VVoRWHUrzJ8/7SLg=; b=O9rlf9h0R8q8BIm/wWOWt2JoXYvqFIxLjhYijl7OVbsrXWCi92vhVGOWNoOO5K8VoGoUKAOjxWYI1AyzFI2RtHWM6/xgoWgIV49iPGHMILVTNBIZoG/FYjsBWfN3FRXVBwoP2rnzLB9RBrqa5VSN/stsq1gpYBIZ4h/eznlDaOo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oxq6cC3d/TeJ2W7hbLNIPT9dvX4GfZxZmBmW7BsYoe5jrXpisLYMm3hjhgsdTcr6Z+EmbNOJHts2p37VvMOLJoglQUfNaAsYOKxaWJIeLYh44JgLpXsmAskInIo8ZUg803TQrw/X3W4friOdcOZqzJbrAEv6XB6oE80OpDe3HKc= Received: by 10.151.82.3 with SMTP id j3mr1297141ybl.57.1205875491564; Tue, 18 Mar 2008 14:24:51 -0700 (PDT) Received: by 10.150.230.16 with HTTP; Tue, 18 Mar 2008 14:24:51 -0700 (PDT) Message-ID: <3c0b01820803181424p7457ea44oda2da277803d2ecc@mail.gmail.com> Date: Tue, 18 Mar 2008 17:24:51 -0400 From: "Alexander Sack" To: "Paul Schmehl" In-Reply-To: <6E62D7035DF48B1A8F3ED1DE@utd65257.utdallas.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47DF39A7.1070307@boosten.org> <49903.203.127.42.92.1205811904.squirrel@www.superhero.nl> <47DF43AD.2020100@boosten.org> <46570.125.214.252.140.1205850870.squirrel@webmail.superhero.nl> <65A9476B618244C571C4EAC7@utd65257.utdallas.edu> <3c0b01820803180836x2f3a13batf181e1b2e6c9bf9c@mail.gmail.com> <52506.125.214.252.140.1205856838.squirrel@webmail.superhero.nl> <3c0b01820803181224x5f64daadt58041d2bfa2db3fd@mail.gmail.com> <6E62D7035DF48B1A8F3ED1DE@utd65257.utdallas.edu> Cc: freebsd-questions@freebsd.org Subject: Re: FW: VMWare Tools for FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Mar 2008 21:24:55 -0000 Paul: I'd have to look at this some more. I got much further in the porting when I hit another snag with the vmblock driver (the inline assembly needs to be __asm__ instead of asm or something needs to process it that way for it to work, I also hacked around a vfsops issue which I'm not 100% sure what should really be there) and then all of it needs to be devtested. I use VMWare Fusion and have installed the existing vmtools that come with the product along with installing the individual X11 vmware driver which works for me but I agree it would be nice to have full port to FreeBSD 7.0-RELEASE. I'm sorry for not giving you patch files its just I was doing this on and off as a exercise to learn a little bit more about it.... I believe at least now as you said, the userland stuff builds fine now. Thanks! -aps On Tue, Mar 18, 2008 at 4:58 PM, Paul Schmehl wrote: > --On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack > wrote: > > > > > bus_setup_intr() kernel API seems to have either changed or handled > > differently in 7.0. I believe you can add a NULL after the flags > > (INTR_MPSAFE) which tells BSD to use the standard interrupt handler > > instead of a top-level handler. > > > > _ac_enaddr is because arpcom as defined in net/if_arp.h no longer > > exists. Typically the protocol bits are stuffed in if_l2com (layer > > 2). > > > > I made the macro in net_compat.h > > > ># define VXN_SC2ENADDR(softc) (IF_LLADDR(VXN_SC2IFP(softc)) > > > > and then removed the "&" from both references in if_vxn.c as this > > macro already returns a pointer to char. > > > > That got me past this problem. Btw, this isn't an official port since > > I didn't really rectify the net_compat.h stuff (I suppose you could > > make the 600000 to 700055, etc.). > > > > I'm still getting some further issues with vnodeops and vfsops with > > some modules (I believe vops_lcok should be vops_lock1) but I don't > > know about the other problem. > > > > Well, you're way beyond my skill level now. I'll be happy to create a port for > this, but someone with a much deeper knowledge of FreeBSD and C is going to > have to resolve the problems with the modules. > > If someone is interested in doing that, I'll submit the patches to the > developers *and* add them to the port so that it can be committed. (Other than > the kernel modules, the software builds fine from what I can tell.) > > -- > > > Paul Schmehl (pauls@utdallas.edu) > Senior Information Security Analyst > The University of Texas at Dallas > http://www.utdallas.edu/ir/security/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson