From: Andi Kleen <ak@suse.de>
To: jt@hpl.hp.com
Cc: Andi Kleen <ak@suse.de>, Mikael Pettersson <mikpe@csd.uu.se>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: 32bit emulation of wireless ioctls
Date: Tue, 4 Feb 2003 00:51:50 +0100 [thread overview]
Message-ID: <20030203235150.GA22202@wotan.suse.de> (raw)
In-Reply-To: <20030203231740.GA29267@bougret.hpl.hp.com>
On Mon, Feb 03, 2003 at 03:17:40PM -0800, Jean Tourrilhes wrote:
> > Anyways: for me it is just slightly annoying to not have 32bit
> > emulation for something, but for other ports like sparc64/ppc64/mips64
> > it can be show stopper because they only have 32bit userland.
>
> <Puzzled of why you would *not* want a 64 bit userland>
Of course I want to have a 64bit userland. In fact I have one.
Just we offer the users the choice to boot 32bit distributions with
64bit kernels too, in case they only need a single application
that needs 64bit or similar. I'm also prepared to rip out or ignore
very obscure parts of the 32bit emulation (in fact I did that already),
but if it's used commonly or even called in bootup it should be supported.
Short term I will just settle on getting that message away so that
RedHat users won't bother me anymore. Can you suggest a good way to
handle SIOCGIWNAME? Should I just make it return -EINVAL?
> > Expect trouble when DaveM wants to plug a wireless card into one of
> > his sparc64 boxes ;-)
>
> I want to see that ;-)
> I've always been telling David and Stephane here that they
> should loan me an Itanium box to make sure IrDA and Wireless LAN work
> properly, for the day we will release a PDA with an Itanium processor.
I understand why you don't see much point to run 32bit on Itanium
because of the performance. But that's not a problem on all 64bit ports...
-Andi
next prev parent reply other threads:[~2003-02-03 23:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 19:16 two x86_64 fixes for 2.4.21-pre3 Mikael Pettersson
2003-01-24 19:37 ` Andi Kleen
2003-01-28 20:51 ` Mikael Pettersson
2003-01-28 21:27 ` Andi Kleen
2003-01-29 15:39 ` Mikael Pettersson
2003-01-29 16:28 ` Andi Kleen
2003-02-03 19:17 ` Mikael Pettersson
2003-02-03 19:49 ` Jean Tourrilhes
2003-02-03 20:12 ` Andi Kleen
2003-02-03 21:43 ` Jean Tourrilhes
2003-02-03 22:46 ` 32bit emulation of wireless ioctls Andi Kleen
2003-02-03 23:17 ` Jean Tourrilhes
2003-02-03 23:51 ` Andi Kleen [this message]
2003-02-04 0:09 ` Jean Tourrilhes
2003-02-03 23:58 ` David Woodhouse
2003-02-04 0:04 ` David Mosberger
2003-02-04 0:11 ` Anton Blanchard
2003-02-07 10:58 ` two x86_64 fixes for 2.4.21-pre3 Pavel Machek
2003-02-07 14:32 ` Alan Cox
2003-02-07 22:58 ` Erik Mouw
2003-02-04 3:13 ` Ton Hospel
2003-02-04 13:11 ` Mikael Pettersson
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=20030203235150.GA22202@wotan.suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.