All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>,
	"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, 21 Nov 2019 12:16:30 +0000	[thread overview]
Message-ID: <0101016e8de4774f-c81ce2c1-f2c7-40d4-83b2-f8f8a49b1f8a-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <37ee7285-5856-6a77-3a29-92b86886c48c@quantenna.com> (Igor Mitsyanko's message of "Thu, 21 Nov 2019 02:27:17 +0000")

Igor Mitsyanko <igor.mitsyanko.os@quantenna.com> writes:

> On 11/19/19 8:12 AM, Jonas Gorski wrote:
>> Any update on this? The support now had its first anniversary, and
>> still no firmware available for it.
>> 
>> Maybe you could put it up in a (temporary) download location at
>> Quantenna until you get around to the second attempt?
>
> Hi Jonas, Quantenna was recently acquired by ON Semiconductor and this 
> was put on hold during the integration. I have gone back to our legal / 
> IT department to work on this again.

Thanks, and please put priority on this. It's really bad that if there's
an upstream driver but users can't use it because of lack of firmware.

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2019-11-21 12:16 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
2019-11-19 16:12       ` Jonas Gorski
2019-11-21  2:27         ` Igor Mitsyanko
2019-11-21 12:16           ` Kalle Valo [this message]
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=0101016e8de4774f-c81ce2c1-f2c7-40d4-83b2-f8f8a49b1f8a-000000@us-west-2.amazonses.com \
    --to=kvalo@codeaurora.org \
    --cc=ashevchenko@quantenna.com \
    --cc=igor.mitsyanko.os@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.