ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Ursella <stefan.ursella@wolfvision.net>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k kernel drive p2p support
Date: Mon, 17 Oct 2022 12:07:05 +0200	[thread overview]
Message-ID: <Y00pSZh5d7f477BZ@wolfvision.net> (raw)
In-Reply-To: <20221013070747.GA1602317@wolfvision.net>

Hi Kalle,

> > Unfortunately it's not really possible to give any good answer as plans
> > can always change, though feature requests are very welcome and I will
> > read all of them. It will also help if you can provide more info like
> > the hardware you are interested in (QCA6390, WCN6855 etc) and why you
> > need it (use cases etc).
> > 
> We are working on a new product which needs miracast support.
> For this product we are interested in the QCA6391.
> 
is it possible to pay for this feature so that you can accelerate the 
implementation?


--
Best
Stefan

Stefan Ursella 
Research and Development

Wolfvision GmbH 
Oberes Ried 14 | 6833 Klaus | Austria 
Tel: +43 5523 52250 <tel:+43552352250> | Mail: stefan.ursella@wolfvision.net <mailto:stefan.ursella@wolfvision.net>

Website: wolfvision.com <www.wolfvision.com> 
Firmenbuch / Commercial Register: FN283521v Feldkirch/Austria


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      reply	other threads:[~2022-10-17 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <366bffb7-34a7-4cd5-9c38-aaed66f66e8d.e0c24246-04d4-485f-8d5f-1cc8fbefd095.9ab7b34d-219e-4d9b-9875-0a3089c8bf4f@emailsignatures365.codetwo.com>
2022-10-12  6:09 ` ath11k kernel drive p2p support Stefan Ursella
2022-10-12  6:33   ` Kalle Valo
2022-10-13  7:07     ` Stefan Ursella
2022-10-17 10:07       ` Stefan Ursella [this message]

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=Y00pSZh5d7f477BZ@wolfvision.net \
    --to=stefan.ursella@wolfvision.net \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.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