From: Andi Kleen <ak@suse.de>
To: jt@hpl.hp.com
Cc: jt@bougret.hpl.hp.com, davem@redhat.com, hch@infradead.org,
ak@colin2.muc.de, netdev@oss.sgi.com
Subject: Re: [PATCH] Add 32bit emulation for wireless
Date: Mon, 19 Jan 2004 21:01:32 +0100 [thread overview]
Message-ID: <20040119210132.0c52df58.ak@suse.de> (raw)
In-Reply-To: <20040119194943.GA9360@bougret.hpl.hp.com>
On Mon, 19 Jan 2004 11:49:43 -0800
Jean Tourrilhes <jt@bougret.hpl.hp.com> wrote:
> However, this is my prefered way to do things. I would much
> prefer to see you using native version of the Wireless Tools,
> especially that the tools and the kernel need to be in sync as far as
> version is concerned. It should be a simple matter of recompiling the
> tools package.
I don't use wireless at all[1] - I was just annoyed at the storm of
unimplemented ioctl messages when booting up 32bit userland.
SuSE 9.0 boot up calls iwconfig by default.
[1] I actually have a Samsung wireless card, but it's not working
due to missing support for the Cirrus 6729 PCMCIA bridge on there.
> One of the main strength of OpenSource is that you can
> recompile for your platform, and I think we should fully exploit this
> advantage, especially for the base system. Otherwise, why not enable
> 16bit compatibility on i386 for ELKS packages ?
I maintain the 32bit emulation on x86-64 and booting an unmodified 32bit distribution
is an important test case for me. Your suggestion is like someone suggesting
to you to just use ethernet with cables instead of this unreliable wireless stuff...
>
> It seems that the BK->Web stuff has not yet picked your
> updates, because I don't see them (and of course the snapshot on
> kernel.org is too old).
It's actually there, just hidden in a large batch of network updates.
-Andi
next prev parent reply other threads:[~2004-01-19 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 12:33 [PATCH] Add 32bit emulation for wireless Andi Kleen
2004-01-19 12:39 ` Christoph Hellwig
2004-01-19 13:10 ` Andi Kleen
2004-01-19 13:56 ` David S. Miller
2004-01-19 14:39 ` Andi Kleen
2004-01-19 14:39 ` David S. Miller
2004-01-19 14:54 ` Andi Kleen
2004-01-19 19:49 ` Jean Tourrilhes
2004-01-19 20:01 ` Andi Kleen [this message]
2004-01-19 20:19 ` Jean Tourrilhes
2004-01-19 20:26 ` David S. Miller
2004-01-19 20:40 ` Jean Tourrilhes
2004-01-19 20:50 ` Andi Kleen
2004-01-19 20:35 ` Andi Kleen
2004-01-19 20:51 ` Jean Tourrilhes
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=20040119210132.0c52df58.ak@suse.de \
--to=ak@suse.de \
--cc=ak@colin2.muc.de \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
/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).