Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Oleksij Rempel <bug-track@fisher-privat.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] open firmware for ath9k_htc
Date: Mon, 22 Oct 2012 17:23:35 +0200	[thread overview]
Message-ID: <508564F7.2050502@fisher-privat.net> (raw)
In-Reply-To: <CAJ-VmomhiT9gT-Upk3NNg6Euup8oqyHSZ5ZMAFWdZ6fhiPQfkw@mail.gmail.com>

Hi Luis,

one more try :)

Am 22.10.2012 16:31, schrieb Adrian Chadd:
> On 20 October 2012 23:24, Oleksij Rempel <bug-track@fisher-privat.net> wrote:
>> Hallo all,
>>
>> i would like to work on open firmware for ath9k_htc.
>>
>> i can C and and have Linux kernel driver development experience. But no
>> Embedded Linux experience - it is the reason why I would like to do it.
>>
>> I tried to contact Luis R. Rodriguez but got no response.
>> What should i do to obtain firmware source?
>
> Hi!
>
> Try again. He's just been busy. :-)
>
>
>
> Adrian
>


-- 
Regards,
Oleksij

  reply	other threads:[~2012-10-22 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21  6:24 [ath9k-devel] open firmware for ath9k_htc Oleksij Rempel
2012-10-22 14:31 ` Adrian Chadd
2012-10-22 15:23   ` Oleksij Rempel [this message]
2012-11-02 18:05     ` Oleksij Rempel

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=508564F7.2050502@fisher-privat.net \
    --to=bug-track@fisher-privat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox