From: Sven Eckelmann <sven@narfation.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Simon Wunderlich <sw@simonwunderlich.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
Pannirselvam Kanagaratnam <pannirk@gmail.com>
Subject: Re: Debugging RTL8192CU firmware loading on 3.12 powerpc
Date: Fri, 02 Sep 2016 13:26:26 +0200 [thread overview]
Message-ID: <6578938.N4SWO0a2Ic@bentobox> (raw)
In-Reply-To: <8cae6bb9-0465-9210-b543-61136836c263@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Freitag, 2. September 2016 13:13:20 CEST Arend Van Spriel wrote:
[...]
> > Do you have any recommendations where the firmware loading problems could
> > come from, and where we could start to debug? Any pointers would be
> > appreciated.
> Hi Simon,
>
> Could it be an endian issue?
Yes, it could be one (at least I've also guessed this - I could still be
completely wrong). But the problem is now to find a good starting point for
the debugging effort.
I've only looked at Simon's screen once while he gather USB dumps but didn't
spot any obvious at that time. There was also the problem that the comparison
dump looked already a lot different due to some timing differences.
I think Simon can give you later more details (when required).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-02 11:26 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 [this message]
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
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=6578938.N4SWO0a2Ic@bentobox \
--to=sven@narfation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pannirk@gmail.com \
--cc=sw@simonwunderlich.de \
/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