* drivers/staging/ks7010 hardware test
@ 2017-05-25 5:11 Tobin C. Harding
2017-05-25 7:18 ` Wolfram Sang
0 siblings, 1 reply; 2+ messages in thread
From: Tobin C. Harding @ 2017-05-25 5:11 UTC (permalink / raw)
To: Wolfram Sang; +Cc: linux-wireless, devel
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Hi Wolfram,
I began testing the card you sent today. I'm getting a firmware load
error like you mentioned.
I checked out code from when you originally merged into staging,
however I built the module in a 4.9 kernel.
To help me track down the issue could you please tell me what testing
you managed to do successfully in the past, and if you can,
approximately the date you were doing the tests or the git commit of
the code you tested.
Thanks. Oh, also could you please indicate your level of interest my
continued efforts. I don't want to send you copious emails if you
would rather me not.
For anyone on the lists reading this, the hardware is
Spectec SDW-823 microSD (SDIO) Wi-Fi card
The error code is -EILSEQ (Illegal byte sequence). It is returned by
sdio_memcpy_fromio(). I do not know what it signifies?
thanks,
Tobin.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: drivers/staging/ks7010 hardware test
2017-05-25 5:11 drivers/staging/ks7010 hardware test Tobin C. Harding
@ 2017-05-25 7:18 ` Wolfram Sang
0 siblings, 0 replies; 2+ messages in thread
From: Wolfram Sang @ 2017-05-25 7:18 UTC (permalink / raw)
To: Tobin C. Harding; +Cc: linux-wireless, devel
[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]
Hi Tobin,
> I began testing the card you sent today. I'm getting a firmware load
> error like you mentioned.
Nice. Firstly, that means the card is alive and survived the mailing.
> I checked out code from when you originally merged into staging,
> however I built the module in a 4.9 kernel.
I think building a vanilla 4.9 kernel is a good choice. I did test the
card with v4.9. I am quite (but not perfectly) sure, I also tested it
with v4.10.
> To help me track down the issue could you please tell me what testing
> you managed to do successfully in the past, and if you can,
> approximately the date you were doing the tests or the git commit of
> the code you tested.
The tests I did are described here:
http://elinux.org/Tests:SDIO-KS7010
The branch I used is mentioned there
https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/log/?h=renesas/topic/gen3-sdio
but it is based on a branch called renesas-drivers (which is some kind
of stripped down linux-next targeted for Renesas R-Car hardware), so I'd
think v4.9 is the better choice.
The tests were all done End of May 2016.
> Thanks. Oh, also could you please indicate your level of interest my
> continued efforts. I don't want to send you copious emails if you
> would rather me not.
I'm definately interested. I might not be able to review patches, but
for high level questions like this, please CC me. However, give me a few
days for a response.
> The error code is -EILSEQ (Illegal byte sequence). It is returned by
> sdio_memcpy_fromio(). I do not know what it signifies?
I use it rarely, but in this case, I'd think bisecting from v4.9 onwards
is a good choice to tackle this down (given that v4.9 works; otherwise
we'll have to check the MMC layer).
Thanks and all the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-25 7:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-05-25 5:11 drivers/staging/ks7010 hardware test Tobin C. Harding
2017-05-25 7:18 ` Wolfram Sang
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).