linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: 32bit emulation of wireless ioctls
Date: Mon, 3 Feb 2003 15:17:40 -0800	[thread overview]
Message-ID: <20030203231740.GA29267@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030203224619.GA6405@wotan.suse.de>

On Mon, Feb 03, 2003 at 11:46:19PM +0100, Andi Kleen wrote:
> 
> > 	Anyway, I believe that 64 bit platforms will need to become
> > mainstream before the issue of wireless on 64 bit is pressing, and by
> > that time most distro will have made the jump.
> 
> Hmm, not so sure. I guess people will sooner than later plug wireless
> cards into 64bit boxes, especially with x86-64 which will hopefully
> be quite "mainstream".

	But I content that when it is that much mainstream, you will
have 64 bit distros.

> > > That is currently done (-EINVAL), but the emulation layer logs an 
> > > warning.
> > 
> > 	It's just a shame that it's not more distinctive, because the
> > error message wouldn't lead me to think "doh, I need a recompile".
> 
> Do you have a better suggestion?

	I checked the errno list, and there was not one obvious
candidate. Potentially we could abuse ENOEXEC, but I must admit my
knowledge of errnos is too superficial.

> 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>

> 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.

> -Andi

	Have fun...

	Jean

  reply	other threads:[~2003-02-03 23:33 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 [this message]
2003-02-03 23:51                       ` Andi Kleen
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=20030203231740.GA29267@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).