From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: Jonas Gorski <jonas.gorski@gmail.com>,
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Andrey Shevchenko <ashevchenko@quantenna.com>
Subject: Re: [PATCH v2 2/2] qtnfmac: add support for Topaz chipsets
Date: Thu, 23 May 2019 19:26:27 +0000 [thread overview]
Message-ID: <41b4f41f-37ae-ef5f-476c-eb616d6a3da1@quantenna.com> (raw)
In-Reply-To: <CAOiHx=nBWr4GNh61WV+SAY-++Z6es-HX3_pd70DB_N33bVK1tw@mail.gmail.com>
>
> A bit late of a review/question, but how does one obtain one of these
> files? There's nothing in linux-firmware, and I see only one aborted
> attempt for adding fmac_qsr10g.img from 2016, but none for the others.
> Searching for these filenames also didn't reveal any external
> locations.
>
>
> Regards
> Jonas
>
Hi Jonas, we're working towards a second attempt to get those accepted
to linux-firmware (fmac_qsr1000.img binary first) admittedly it takes us
a long time to do that. The main obstacle for us as developers is that
the binary contains 3-d party GPL code so we have to work with other
departments to satisfy all submission requirements (provide sources,
proper licensing/attribution etc). From a failed fmac_qsr10g.img attempt
it was clear that simply providing an contact email is not enough.
We're planning a second attempt to submit firmware binary patch
relatively soon, for now we expect device will boot from flash.
next prev parent reply other threads:[~2019-05-23 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 10:23 [PATCH v2 0/2] qtnfmac: add support for QSR1000/QSR2000 (aka Topaz) chipsets Sergey Matyukevich
2018-10-16 10:23 ` [PATCH v2 1/2] qtnfmac_pcie: use single PCIe driver for all platforms Sergey Matyukevich
2018-11-06 16:56 ` Kalle Valo
2018-10-16 10:23 ` [PATCH v2 2/2] qtnfmac: add support for Topaz chipsets Sergey Matyukevich
2019-05-18 17:54 ` Jonas Gorski
2019-05-23 19:26 ` Igor Mitsyanko [this message]
2019-11-19 16:12 ` Jonas Gorski
2019-11-21 2:27 ` Igor Mitsyanko
2019-11-21 12:16 ` Kalle Valo
2019-11-22 14:35 ` Bjørn Mork
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=41b4f41f-37ae-ef5f-476c-eb616d6a3da1@quantenna.com \
--to=igor.mitsyanko.os@quantenna.com \
--cc=ashevchenko@quantenna.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.com \
/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.