From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Realtek rtl8188 support?
Date: Thu, 28 Oct 2010 23:48:13 +0200 [thread overview]
Message-ID: <201010282348.16673.s.L-H@gmx.de> (raw)
In-Reply-To: <4CC9C067.9040105@lwfinger.net>
Hi
On Thursday 28 October 2010, Larry Finger wrote:
> On 09/21/2010 02:20 PM, Stefan Lippers-Hollmann wrote:
[...]
> As part of the inclusion of r8712u in staging, Greg KH asked for a TODO item to
> convert the firmware to an external binary. I see this as a 2 step process: (1)
> get the firmware binary accepted into linux-firmware, and (2) make it work with
> the external loading mechanism. Step 1 has been completed with the following
> commit message:
>
> commit c500ee5be41b7954ba9630d7e5d409a24efaf249
> Author: Larry Finger <Larry.Finger@lwfinger.net>
> Date: Wed Oct 20 11:49:59 2010 -0500
>
> Convert firmware for Realtek RTL8192SU (rtl8712u) from embedded to
> an external file.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>
> The code for step 2 is running locally. I'm waiting for the new version of
> linux-firmware to propagate through the distros before I submit the patch. If
I assume you refer to rtl8712u.bin in your r8712u_firmware tree:
http://git.kernel.org/?p=linux/kernel/git/lwfinger/r8712u_firmware.git;a=blob_plain;f=rtl8712u.bin
200fd952db3cc9259b1fd05e3e51966f *rtl8712u.bin
> you want to grab the new firmware package, I can send you a copy of the patch.
I'd very much like to test the patch(2) needed for rtl8712, if possible.
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2010-10-28 21:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 17:45 Realtek rtl8188 support? Paul Thomas
2010-03-06 18:07 ` Gábor Stefanik
2010-03-07 8:16 ` Pavel Roskin
2010-03-07 15:36 ` Gábor Stefanik
2010-03-10 1:59 ` Pavel Roskin
2010-03-10 3:16 ` Pavel Roskin
2010-03-29 22:19 ` Paul Thomas
2010-03-29 23:32 ` Gábor Stefanik
2010-05-25 0:16 ` Paul Thomas
2010-05-25 23:00 ` Frederic Leroy
2010-05-26 22:06 ` Pavel Roskin
2010-05-26 22:21 ` Gábor Stefanik
2010-05-28 16:35 ` Pavel Roskin
2010-09-10 11:29 ` Claus Ried
2010-09-18 3:37 ` Hin-Tak Leung
2010-09-18 13:43 ` Stefan Lippers-Hollmann
[not found] ` <AANLkTimz6bR7mLnEgeBzBZrbKC+jp2bx3VTya=YL2KjV@mail.gmail.com>
[not found] ` <201009212120.07914.s.L-H@gmx.de>
2010-10-28 18:26 ` Larry Finger
2010-10-28 21:48 ` Stefan Lippers-Hollmann [this message]
2010-10-28 22:10 ` Larry Finger
2010-10-29 20:02 ` Stefan Lippers-Hollmann
2010-10-29 20:03 ` staging: r8712u: Fix external firmware loading Stefan Lippers-Hollmann
2010-10-29 20:26 ` Realtek rtl8188 support? Walter Goldens
2010-10-29 21:27 ` Gábor Stefanik
2010-10-30 4:06 ` Larry Finger
2010-10-30 14:49 ` John W. Linville
2010-10-30 18:11 ` Gábor Stefanik
2010-10-31 3:44 ` Larry Finger
2010-10-31 11:30 ` Walter Goldens
2010-10-31 15:04 ` Larry Finger
2010-12-16 13:25 ` Walter Goldens
2010-12-16 14:10 ` Larry Finger
2011-01-25 7:57 ` Brian Prodoehl
2010-09-18 23:02 ` Paul Thomas
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=201010282348.16673.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=Larry.Finger@lwfinger.net \
--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).