Date: Tue, 03 Jun 2008 13:27:55 -0700 (PDT)
Message-Id: <20080603.132755.262737024.davem@davemloft.net>
To: linux-wireless@vger.kernel.org
CC: linville@tuxdriver.com, mokuno@sm.sony.co.jp, netdev@vger.kernel.org,
       linux-kernel@vger.kernel.org
Subject: [PATCH 0/12]: Proper compat WEXT support.
From: David Miller <davem@davemloft.net>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1724
Lines: 41


This is a refresh of my previous WEXT compat patch set.

I've actually tested these exact patches on sparc64 with a RNDIS based
USB wireless device from Linksys.  I was able to perform iwconfig
commands, check iwlist, bring up the interface and use it properly.
All with 32-bit tools.  I've also done an allmodconfig sanity
build check on sparc64.

The one thing I was not able to test yet is wpa_supplicant use, and
that likely doesn't work properly yet, but we can fix that on top and
these patches do not break native non-compat binaries.  They do make a
lot of compat stuff work which wasn't the case before.  So applying
this stuff makes sense, and we can get wpa_supplicant working if it
isn't working using follow-on patches.

The patch set starts by cleaning up the code so that we can avoid
having multiple copies of the WEXT main dispatch routines, one for
compat and one for the non-compat case.

Next, basic compat level handling of the WEXT ioctl is added, and the
equivalent code in the compat_ioctl.c file is removed.

Finally, compat IWE stream munging is added for the wireless layer.
When we get a compat WEXT ioctl request, we set a bit in the request
info blob, and the stream building helpers tip off this to format the
stream entries properly.

These patches are against net-next-2.6 and are also available as
a GIT tree at:

	master.kernel.org:/pub/scm/linux/kernel/git/davem/wireless-2.6.git

John, please pull or apply as you deem appropriate.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/