Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: Support for RTL8188FU
To:     Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc:     linux-wireless@vger.kernel.org
References: <20191001160305.qrl4nt2jmdsogaaz@linutronix.de>
 <3af284c7-ee46-dd42-9549-de55feae2528@lwfinger.net>
 <20191001174612.4kj3mt3h5epidyyk@linutronix.de>
 <b958b669-a683-d7cd-6bbf-bfe3e674f62d@lwfinger.net>
 <20200304102152.a25cczvat2mujxwa@linutronix.de>
From:   Larry Finger <Larry.Finger@lwfinger.net>
Message-ID: <9c6717de-5ffc-47dc-6db7-7e070cbc41b9@lwfinger.net>
Date:   Wed, 4 Mar 2020 12:16:54 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200304102152.a25cczvat2mujxwa@linutronix.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On 3/4/20 4:21 AM, Sebastian Andrzej Siewior wrote:
> On 2019-10-01 13:52:30 [-0500], Larry Finger wrote:
>> The first thing I would do is clone the v5.2.2.4 branch of
>> lwfinger/rtl8188eu at GitHub, add the USB ID for your device, and see if
>> that works. I expect it will. If so, that would get you quite a ways toward
>> the changes needed to get that driver into staging.
> 
> Adding the id didn't help. I added "hal/Hal8188FPwrSeq.o" next to
> "hal/Hal8188EPwrSeq.o". Some parts were different.
> After loading the firmware the driver said that the firmware wasn't
> active. So I tweaked the firmware loading part a little. The signature
> of the firmware in my driver is 0x88F0 instead of 0x88E0 and the
> "normal-nic" firmware has 20306 bytes. By loading the "other" firmware
> the firmware and driver says that it is "alive".
> I disabled the "IOL" bits (like rtw_IOL_applied() which returns false).
> It took long and didn't seem to succeed. My driver lacks most of the
> code, rtw_IOL_applied() isn't referenced anyway and the ifdef isn't set.
> 
> I would continue to add more pieces in order to get it working unless
> you have a different advice.

I have no further advice. There are quite likely a number of routines that will 
differ as the 8188FU chip is quite likely a lot different from the 8188EU, even 
though both are 802.11n devices.

Larry