linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
	Mikhail Karpenko <mkarpenko@quantenna.com>
Subject: Re: [PATCH 2/2] qtnfmac: add support for the new revision of QSR10g chip
Date: Mon, 27 Jan 2020 08:34:11 +0000	[thread overview]
Message-ID: <20200127083404.jr6k2clfxgv7vxz7@bars> (raw)
In-Reply-To: <20191126075150.e2rrz3jqx627l3g2@bars>

> > > Add support for the new minor revision of QSR10g chip. Major changes from
> > > the driver perspective include PCIe data path modifications. Setup is now
> > > more complicated, but finally more things have been offloaded to hardware.
> > > As a result, less driver boilerplate operations are needed after Tx/Rx
> > > descriptors queues have been configured. Besides, restrictions on
> > > descriptors queue lengths have been relaxed.
> > >
> > > Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
> > 
> > What about the firmware, is that available for this new revision?
> 
> Hello Kalle,
> 
> There are two drivers: pearl_qtnfmac for QSR10G and topaz_qtnfmac for
> QSR1000. Firmware for QSR1000 chips has a higher priority since those
> devices have been in production for quite a while now and there are
> multiple products available. From the engineering perspective we are
> ready to release firmware and SDK for QSR1000/QSR2000 devices. Now we
> are waiting for the ACK from legal team. This was delayed by the
> acquisition of Quantenna by On Semiconductor.  
> 
> As for the latest QSR10G chips, we are not yet ready to release SDK.
> The main reason is that platform is under active development.

Hello Kalle,

I noticed that you marked these two patches as deferred in patchwork.
Is there anything else I have to do here ?

Regards,
Sergey

  reply	other threads:[~2020-01-27  8:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 13:53 [PATCH 0/2] qtnfmac: add support for the new revision of qsr10g chip Sergey Matyukevich
2019-11-21 13:53 ` [PATCH 1/2] qtnfmac: prepare for the next chip revision Sergey Matyukevich
2019-11-21 13:53 ` [PATCH 2/2] qtnfmac: add support for the new revision of QSR10g chip Sergey Matyukevich
2019-11-21 20:15   ` Kalle Valo
2019-11-26  7:51     ` Sergey Matyukevich
2020-01-27  8:34       ` Sergey Matyukevich [this message]
2020-04-24 10:17         ` Sergey Matyukevich
2020-11-11  9:04           ` Kalle Valo

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=20200127083404.jr6k2clfxgv7vxz7@bars \
    --to=sergey.matyukevich.os@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mkarpenko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).