linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Reto Schneider <code@reto-schneider.ch>
To: Josh Boyer <jwboyer@kernel.org>, Chris Chiu <chiu@endlessm.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Jes.Sorensen@gmail.com
Cc: Reto Schneider <code@reto-schneider.ch>,
	Linux Firmware <linux-firmware@kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] rtlwifi: v88.2 firmware files for RTL8192CU
Date: Sun, 20 Sep 2020 05:00:09 +0200	[thread overview]
Message-ID: <744509e3-d3f6-21bd-3f6b-83a93d88d7df@reto-schneider.ch> (raw)
In-Reply-To: <CA+5PVA7WLAGP6oL8pxGvjqHS030LoDTcz5-YDHVjYaYVHOZD2g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On 9/14/20 3:19 PM, Josh Boyer wrote:
>> On Tue, Mar 24, 2020 at 6:58 AM Reto Schneider <code@reto-schneider.ch> wrote:
>>>
>>> The vendor driver rtl8188C_8192C_usb_linux_v4.0.1_6911.20130308 includes
> 
> Where can one get that driver?  It's unclear to me what the terms and
> conditions around its usage are, and therefore I can't tell if
> deriving values from this driver are permitted.

This driver was available on the official Realtek servers before they
prevented accessing their FTP servers [0][1]. Luckly, someone mirrored
its content on GitHub [2], which is also where I got the driver from [3].

> If you can get an Ack from someone from Realtek, or someone that

I have no contacts to anyone at Realtek. Not sure if "cold" e-mailing
random people there would be helpful.

> normally maintains the upstream drivers, that would go a long way.

Jes Sorensen, the maintainer of rtl8xxxu redirected me to Chris Chiu in
order to get (paid) work done on rtl8xxxu (which includes testing this
FW). Does this help?

Kind regards,
Reto

[0]
https://forums.mydigitallife.net/threads/ftp3-realtek-com-tw.72385/#post-1581267
[1] https://github.com/lwfinger/rtl8188eu/issues/275
[2] https://github.com/XAIOThaifeng/realtek-linux
[3]
https://github.com/XAIOThaifeng/realtek-linux/tree/370738ceb9efa42c31ecdcb4db90ee0d6d064004/RTL8188C_8192C/USB/v4.0

[-- Attachment #2: 0xBFB93E8F422586E0.asc --]
[-- Type: application/pgp-keys, Size: 2415 bytes --]

  reply	other threads:[~2020-09-20  3:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  2:45 [PATCH] rtlwifi: v88 firmware files for rtl8192cu Reto Schneider
2020-03-23  2:45 ` Reto Schneider
2020-03-23 14:57 ` Larry Finger
2020-03-23 14:57   ` Larry Finger
2020-03-23 22:58 ` [PATCH v2 0/1] Updating RTL8192CU firmware Reto Schneider
2020-03-23 22:58   ` Reto Schneider
2020-03-23 22:58   ` [PATCH v2 1/1] rtlwifi: v88.2 firmware files for RTL8192CU Reto Schneider
2020-03-23 22:58     ` Reto Schneider
2020-09-06  3:39     ` Chris Chiu
2020-09-06  3:39       ` Chris Chiu
2020-09-14 13:19       ` Josh Boyer
2020-09-20  3:00         ` Reto Schneider [this message]
2020-09-03 17:57   ` [PATCH v2 0/1] Updating RTL8192CU firmware Reto Schneider
2020-09-03 17:57     ` Reto Schneider

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=744509e3-d3f6-21bd-3f6b-83a93d88d7df@reto-schneider.ch \
    --to=code@reto-schneider.ch \
    --cc=Jes.Sorensen@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chiu@endlessm.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@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).