From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: FYI - new compat-wireless based on 2.6.33-rc4
Date: Wed, 20 Jan 2010 12:13:26 -0800 [thread overview]
Message-ID: <43e72e891001201213x6a2c203dl7121f2dde6d61fb9@mail.gmail.com> (raw)
The compat_firmware_class was having some issues which should now be
hopefully addressed:
* Use a different subsystem name for sysfs registration, now compat_firmware
* The new subsystem name change required a new udev rule to be added
The new compat-wireless for 2.6.33-rc4 has been pushed out with the
new changes. Unfortunately 2.6.33-rc5 hasn't been pushed out yet so I
just overwrote the old rc4 package (next time I'll just add an extra
extra version when this happens). The new sha1sum for this release is:
c007d7c8649d6149f415ea87dc7a34d4ee808766 compat-wireless-2.6.33-rc4.tar.bz2
Just kicked out a bleeding edge release with the same fixes:
65bb3cd6565f1788a2c63bfe8ccfdd8dfc1fb368 compat-wireless-2010-01-20.tar.bz2
Please let us know if there are any issues. I should note that the new
compat_firmware_class will be used *every time* compat-wireless is
used firmware needs to be uploaded, not just for the new
request_firmware_nowait().
Luis
next reply other threads:[~2010-01-20 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:13 Luis R. Rodriguez [this message]
2010-01-21 0:21 ` FYI - new compat-wireless based on 2.6.33-rc4 Richard Farina
2010-01-21 18:07 ` Adam Wozniak
2010-01-21 18:12 ` Luis R. Rodriguez
2010-01-21 19:32 ` [PATCH] compat: fix build on arm Hauke Mehrtens
2010-01-21 19:53 ` Luis R. Rodriguez
2010-01-21 20:16 ` Adam Wozniak
2010-01-21 20:08 ` FYI - new compat-wireless based on 2.6.33-rc4 Adam Wozniak
2010-01-21 20:17 ` Luis R. Rodriguez
2010-01-21 21:24 ` Adam Wozniak
2010-01-21 21:39 ` Adam Wozniak
2010-01-21 22:21 ` Luis R. Rodriguez
2010-01-22 23:46 ` Adam Wozniak
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=43e72e891001201213x6a2c203dl7121f2dde6d61fb9@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).