From: Pavel Machek <pavel@ucw.cz>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>, linux-kernel@vger.kernel.org
Subject: Re: VMware-workstation-4.5.1 on linux-2.6.4-x86_64 host fai
Date: Tue, 30 Mar 2004 14:33:31 +0200 [thread overview]
Message-ID: <20040330123331.GB461@elf.ucw.cz> (raw)
In-Reply-To: <200403241955.38489.hpj@urpla.net>
Hi!
> Hmm, it's a SuSE issue then, nice to know (and easily fixable ;-).
>
> > On 2.6.x kernels additionally (problem you are hitting now)
> > SIO*BRIDGE ioctls were moved from "compatible" to "not so
> > compatible" group. If you'll just mark them as "compatible", it
> > will work sufficiently well to get networking in VMware.
>
> I found it. Fixed it with this patch:
>
> --- include/linux/compat_ioctl.h~ 2004-03-12 18:37:26.000000000 +0100
> +++ include/linux/compat_ioctl.h 2004-03-24 12:34:30.000000000 +0100
> @@ -247,10 +247,10 @@
> COMPATIBLE_IOCTL(SIOCSIFENCAP)
> COMPATIBLE_IOCTL(SIOCGIFENCAP)
> COMPATIBLE_IOCTL(SIOCSIFNAME)
> -/* FIXME: not compatible
> +/* FIXME: not compatible */
> COMPATIBLE_IOCTL(SIOCSIFBR)
> COMPATIBLE_IOCTL(SIOCGIFBR)
> -*/
> +/* reactivated for vmware */
> COMPATIBLE_IOCTL(SIOCSARP)
> COMPATIBLE_IOCTL(SIOCGARP)
> COMPATIBLE_IOCTL(SIOCDARP)
Marking ioctl compatible when it is not is pretty nasty, right? What
about writing conversion functions?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-30 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 11:59 VMware-workstation-4.5.1 on linux-2.6.4-x86_64 host fai Petr Vandrovec
2004-03-24 18:55 ` Hans-Peter Jansen
2004-03-30 12:33 ` Pavel Machek [this message]
2004-03-30 21:17 ` Hans-Peter Jansen
2004-03-30 21:44 ` Petr Vandrovec
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=20040330123331.GB461@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=VANDROVE@vc.cvut.cz \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
/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