From: Oleksij Rempel <fishor@gmx.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc firmware
Date: Sat, 4 Jun 2016 22:25:03 +0200 [thread overview]
Message-ID: <5753391F.7030200@gmx.net> (raw)
In-Reply-To: <CAArymCm7SgKyK_cy+MucMb5-8nDZshiOCu-mPVyKR6WnNCm5Lg@mail.gmail.com>
Am 04.06.2016 um 21:44 schrieb bruce m beach:
>>> I'm looking for some kind of simple request in the ath9k_htc driver, through
>>> the usb ep0, like a memory read on the card, where a urb is sent with
>>> the resulting chain of events. The simpler the better. The simplest.
>
>> For EP0 on drivers site:
>> static int ath9k_hif_usb_download_fw(struct hif_device_usb *hif_dev)
>> {
>> int transfer, err;
>> const void *data = hif_dev->fw_data;
>> size_t len = hif_dev->fw_size;
>> u32 addr = AR9271_FIRMWARE;
>> u8 *buf = kzalloc(4096, GFP_KERNEL);
>> u32 firm_offset;
>> ...
>
> What about the code for setting and resetting leds ???
>
> Bruce
>
It is EP3/EP4 and it is not working without firmware.
Here is one example how you can add new command to firmware:
https://github.com/olerem/open-ath9k-htc-firmware/commit/c73c159303e30a28e2d3dc05ba0d2d15504e5fad
And for kernel driver:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8badb50cfab6d433622dbfd5a90b6adf27333107
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <fishor@gmx.net>
To: bruce m beach <brucembeach@gmail.com>
Cc: ath9k-devel@lists.ath9k.org, ath9k_htc_fw@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: ath9k_htc firmware
Date: Sat, 4 Jun 2016 22:25:03 +0200 [thread overview]
Message-ID: <5753391F.7030200@gmx.net> (raw)
In-Reply-To: <CAArymCm7SgKyK_cy+MucMb5-8nDZshiOCu-mPVyKR6WnNCm5Lg@mail.gmail.com>
Am 04.06.2016 um 21:44 schrieb bruce m beach:
>>> I'm looking for some kind of simple request in the ath9k_htc driver, through
>>> the usb ep0, like a memory read on the card, where a urb is sent with
>>> the resulting chain of events. The simpler the better. The simplest.
>
>> For EP0 on drivers site:
>> static int ath9k_hif_usb_download_fw(struct hif_device_usb *hif_dev)
>> {
>> int transfer, err;
>> const void *data = hif_dev->fw_data;
>> size_t len = hif_dev->fw_size;
>> u32 addr = AR9271_FIRMWARE;
>> u8 *buf = kzalloc(4096, GFP_KERNEL);
>> u32 firm_offset;
>> ...
>
> What about the code for setting and resetting leds ???
>
> Bruce
>
It is EP3/EP4 and it is not working without firmware.
Here is one example how you can add new command to firmware:
https://github.com/olerem/open-ath9k-htc-firmware/commit/c73c159303e30a28e2d3dc05ba0d2d15504e5fad
And for kernel driver:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8badb50cfab6d433622dbfd5a90b6adf27333107
next prev parent reply other threads:[~2016-06-04 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 17:26 ath9k_htc firmware bruce m beach
2016-06-04 5:54 ` Oleksij Rempel
2016-06-04 5:58 ` [ath9k-devel] Fwd: " Oleksij Rempel
2016-06-04 5:58 ` Oleksij Rempel
2016-06-04 19:44 ` [ath9k-devel] " bruce m beach
2016-06-04 19:44 ` bruce m beach
2016-06-04 20:25 ` Oleksij Rempel [this message]
2016-06-04 20:25 ` Oleksij Rempel
2016-06-04 20:27 ` [ath9k-devel] " Oleksij Rempel
2016-06-04 20:27 ` Oleksij Rempel
2016-06-09 15:14 ` bruce m beach
-- strict thread matches above, loose matches on Subject: below --
2016-06-03 17:59 [ath9k-devel] " bruce m beach
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=5753391F.7030200@gmx.net \
--to=fishor@gmx.net \
--cc=ath9k-devel@lists.ath9k.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.