All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Support for RTL8188FU
Date: Wed, 4 Mar 2020 11:21:52 +0100	[thread overview]
Message-ID: <20200304102152.a25cczvat2mujxwa@linutronix.de> (raw)
In-Reply-To: <b958b669-a683-d7cd-6bbf-bfe3e674f62d@lwfinger.net>

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.

> Larry

Sebastian

  parent reply	other threads:[~2020-03-04 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 16:03 Support for RTL8188FU Sebastian Andrzej Siewior
2019-10-01 16:47 ` Larry Finger
2019-10-01 17:46   ` Sebastian Andrzej Siewior
2019-10-01 18:52     ` Larry Finger
2019-10-01 20:48       ` Sebastian Andrzej Siewior
2020-03-04 10:21       ` Sebastian Andrzej Siewior [this message]
2020-03-04 18:16         ` Larry Finger
2020-03-10 14:48           ` Sebastian Andrzej Siewior
2020-03-10 14:54             ` Greg Kroah-Hartman

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=20200304102152.a25cczvat2mujxwa@linutronix.de \
    --to=bigeasy@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.