Date: Tue, 18 Mar 2008 15:58:02 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-questions@freebsd.org Subject: Re: FW: VMWare Tools for FreeBSD Message-ID: <6E62D7035DF48B1A8F3ED1DE@utd65257.utdallas.edu> In-Reply-To: <3c0b01820803181224x5f64daadt58041d2bfa2db3fd@mail.gmail.com> References: <BMEDLGAENEKCJFGODFOCOEIACFAA.tedm@toybox.placo.com> <47DEE8D6.9080708@sucked-in.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack <pisymbol@gmail.com> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6E62D7035DF48B1A8F3ED1DE>