Date: Thu, 07 Oct 2010 12:34:21 -0500 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: mdf@FreeBSD.org Cc: Kostik Belousov <kostikbel@gmail.com>, FreeBSD Arch <freebsd-arch@freebsd.org> Subject: Re: freebsd32_ioctl.c Message-ID: <4CAE049D.2090603@freebsd.org> In-Reply-To: <AANLkTinHbtZbHWVf-CucjmJusCHpGzGsjxN%2BMQru4xVd@mail.gmail.com> References: <AANLkTinYascWzAn8dWMsKaDqcD0WuMr40=SJ_KX3Dfn0@mail.gmail.com> <20101007161338.GK2392@deviant.kiev.zoral.com.ua> <AANLkTinHbtZbHWVf-CucjmJusCHpGzGsjxN%2BMQru4xVd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/07/10 12:02, mdf@FreeBSD.org wrote: >>> Should we >>> just be adding ioctl argument munging as we go along and not worry >>> about the size? Or is there simple way to keep the munging inside the >>> driver? Perhaps my making the driver's ioctl look something like: >>> >> I think that in-driver variant is the best. >> > Okay, I am trying this approach. > > >> if (SV_CURPROC_FLAG(SV_ILP32)) >> > That's what I get for doing development on stable/7. I miss out on > the existence of such handy things. > Also bear in mind that freebsd32 is also used on powerpc64 to run 32-bit ppc binaries, so testing for IA32 probably isn't what you want, anyway. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CAE049D.2090603>