From: "John W. Linville" <linville@tuxdriver.com>
To: Daniel Golle <dgolle@allnet.de>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
juhosg@openwrt.org, john@phrozen.org
Subject: Re: [rt2x00-users] [PATCH 0/3] introduce rt2x00_platform
Date: Mon, 7 Jan 2013 15:00:06 -0500 [thread overview]
Message-ID: <20130107200005.GA2203@tuxdriver.com> (raw)
In-Reply-To: <20121211100336.GA7807@earthship.arig>
On Tue, Dec 11, 2012 at 12:03:39PM +0200, Daniel Golle wrote:
> On embedded systems built-in or PCIe connected WiFi modules usually lack their
> own EEPROM and use a mtd partition instead of that. In OpenWrt, this is solved
> by requesting a firmware and the handling the resulting hotplug call in
> userspace which will then extract the needed file from mtd and supply it to
> the driver.
> In other cases, PCIe modules might come with an actual EEPROM, but yet some
> board-specific hacks are required, such as disabling bands or overriding the
> modules MAC address with a board-supplied one.
>
> The original author of those patches is Gabor Juhos.
> According to his remarks, 3 patches related to overriding the whole eeprom and
> introducing rt2x00_platform.h were merged into a single patch.
>
> Daniel Golle (3):
> rt2x00: allow overriding eeprom through platform_data
> rt2x00: allow disabling bands through platform_data
> rt2x00: add platform_data mac address
>
> drivers/net/wireless/rt2x00/Kconfig | 4 ++
> drivers/net/wireless/rt2x00/Makefile | 1 +
> drivers/net/wireless/rt2x00/rt2800pci.c | 34 ++++++-----
> drivers/net/wireless/rt2x00/rt2x00.h | 10 +++
> drivers/net/wireless/rt2x00/rt2x00dev.c | 37 +++++++++++
> drivers/net/wireless/rt2x00/rt2x00eeprom.c | 98 ++++++++++++++++++++++++++++++
> drivers/net/wireless/rt2x00/rt2x00lib.h | 16 +++++
> drivers/net/wireless/rt2x00/rt2x00pci.c | 7 +++
> drivers/net/wireless/rt2x00/rt2x00soc.c | 1 +
> drivers/net/wireless/rt2x00/rt61pci.c | 5 ++
> include/linux/rt2x00_platform.h | 23 +++++++
> 11 files changed, 222 insertions(+), 14 deletions(-)
> create mode 100644 drivers/net/wireless/rt2x00/rt2x00eeprom.c
> create mode 100644 include/linux/rt2x00_platform.h
It looks like we need a repost of this series? I'm dropping the old series...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-01-07 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 10:03 [PATCH 0/3] introduce rt2x00_platform Daniel Golle
2013-01-07 20:00 ` John W. Linville [this message]
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=20130107200005.GA2203@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dgolle@allnet.de \
--cc=john@phrozen.org \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).