From: Simon Wunderlich <sw@simonwunderlich.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Sven Eckelmann <sven@narfation.org>,
linux-wireless@vger.kernel.org,
Pannirselvam Kanagaratnam <pannirk@gmail.com>
Subject: Re: Debugging RTL8192CU firmware loading on 3.12 powerpc
Date: Wed, 07 Sep 2016 10:23:17 +0200 [thread overview]
Message-ID: <1551808.YAuhaNDynd@prime> (raw)
In-Reply-To: <1d72a2ac-03e7-37d8-c367-68413595443e@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]
On Tuesday, September 6, 2016 8:29:32 AM CEST Larry Finger wrote:
> On 09/06/2016 08:09 AM, Sven Eckelmann wrote:
> > On Dienstag, 6. September 2016 09:40:41 CEST Sven Eckelmann wrote:
> >> On Freitag, 2. September 2016 12:53:28 CEST Larry Finger wrote:
> >> [...]
> >>
> >>> The patch I included in my previous E-mail, and attached here, does get
> >>> the firmware loaded correctly. There is still a problem that prevents
> >>> authentication. I'm still looking for that issue.
> >>
> >> Thanks for the fast update. I am currently testing your patch. It looks
> >> like the initial error is now gone. The hostapd also starts but
> >> beaconing doesn't seem to work at all (no error from the kernel/hostapd
> >> but the device is not sending anything). I am currently checking how
> >> beaconing is supposed to work in your driver. Maybe I will spot
> >> something useful.>
> > Yes, found something similar in the checksumming algorithm. See the
> > attached patch for details.
>
> Just for the record, this is not "my" driver. It was provided by Realtek. My
> contribution has only been to clean it up.
>
> Thanks for the patch. I too had found that checksum code, but I had not sent
> it as there are still problems on BE machines. These difficulties are
> running the NIC in STA mode. I have not tried AP mode. Scan data seem to be
> read OK, but it never authenticates. I do not know if there are further
> errors in setting up the transmit buffer, or if the problem is in the
> encryption/decryption code. I'm still looking.
just as a connected question here - do you know if those devices support
MultiSSID? The capabilities currently don't allow that, but I'm wondering if
that could be implemented, or if there are any hardware/firmware limitations?
Thanks,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2016-09-07 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 8:50 Debugging RTL8192CU firmware loading on 3.12 powerpc Simon Wunderlich
2016-09-02 11:13 ` Arend Van Spriel
2016-09-02 11:26 ` Sven Eckelmann
2016-09-02 17:17 ` Larry Finger
2016-09-02 17:53 ` Larry Finger
2016-09-06 7:40 ` Sven Eckelmann
2016-09-06 13:09 ` Sven Eckelmann
2016-09-06 13:29 ` Larry Finger
2016-09-07 8:23 ` Simon Wunderlich [this message]
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=1551808.YAuhaNDynd@prime \
--to=sw@simonwunderlich.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pannirk@gmail.com \
--cc=sven@narfation.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.