From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Aleš Voda" <AVoda@descartes.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath6kl-devel@qca.qualcomm.com" <ath6kl-devel@qca.qualcomm.com>
Subject: Re: AR6103G Linux kernel 3.4.5 problems
Date: Fri, 8 Mar 2013 09:27:00 +0200 [thread overview]
Message-ID: <87ppzas663.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <62813611608FC749AC8F3F91AEAF5F89417512DD@CPEXM03.corp.dsg.local> ("Aleš Voda"'s message of "Fri, 28 Dec 2012 11:35:34 +0000")
Hi,
Aleš Voda <AVoda@descartes.com> writes:
> We have some custom board equipped with AR6103G using SDIO as hif and
> are having problems with AR6103 not starting after downloading the
> firmware. Linux kernel being used is 3.4.5. As it is apparent from the
> console output attached, the fw related files are downloaded and a
> timeout occurs after uploading data patch file to the chip. After
> removing ath6kl_sdio driver and renaming fw-2 and fw-3
Why do you need to rename the firmware files? What version of ath6kl are
you using? Where did you get it?
> are so they can not be found and loaded, timeout during fw uploads
> doesn't occur anymore after insertion of the ath6kl_sdio module, but
> there is a HW startup failure while awaiting CTRL message from the
> chip (err = -EIO). The firmware for the chip has been downloaded from
> the kernel firmware git repository.
>
> http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=tree;f=
> ath6k/AR6003/hw2.1.1;hb=HEAD
You should be using fw-3.bin. Better to remove athwlan.bin and fw-2.bin
altogether from your platform.
> What could be the problem? If you need any additional info please do
> not hesitate to contact me.
I think I don't have AR6103 myself. I'm not sure if it has some
differences compared to AR6003, that's one possibility as well.
--
Kalle Valo
next parent reply other threads:[~2013-03-08 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62813611608FC749AC8F3F91AEAF5F89417512DD@CPEXM03.corp.dsg.local>
2013-03-08 7:27 ` Kalle Valo [this message]
2013-03-08 8:26 ` AR6103G Linux kernel 3.4.5 problems Aleš Voda
2013-03-11 11:26 ` Aleš Voda
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=87ppzas663.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=AVoda@descartes.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--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.