From: Robert Marko <firstname.lastname@example.org>
To: Thibaut <email@example.com>
Cc: Christian Lamparter <firstname.lastname@example.org>,
Kalle Valo <email@example.com>,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
email@example.com, open list <firstname.lastname@example.org>
Subject: Re: [PATCH] ath10k: support bus and device specific API 1 BDF selection
Date: Wed, 2 Feb 2022 19:49:43 +0100 [thread overview]
Message-ID: <CAOX2RU7FOdSuo2Jgo0i=8e-4bJwq7ahvQxLzQv_zNCz2HCTBwA@mail.gmail.com> (raw)
What is your opinion on this?
I would really love to see this get merged as we are having more and
more devices that are impacted without it.
On Fri, 17 Dec 2021 at 13:25, Thibaut <email@example.com> wrote:
> > Le 17 déc. 2021 à 13:06, Robert Marko <firstname.lastname@example.org> a écrit :
> > On Wed, 8 Dec 2021 at 15:07, Christian Lamparter <email@example.com> wrote:
> >> Isn't the only user of this the non-upstreamable rb_hardconfig
> >> mikrotik platform driver?
> The driver could be upstreamed if desirable.
> Yet I think it’s quite orthogonal to having the possibility to dynamically load a different BDF via API 1 for each available radio, which before this patch couldn’t be done and is necessary for this particular hardware.
> >> So, in your case the devices in question
> >> needs to setup a detour through the userspace firmware (helper+scripts)
> >> to pull on the sysfs of that mikrotik platform driver? Wouldn't it
> >> be possible to do this more directly?
> > Yes, its the sole current user as its the only vendor shipping the BDF
> > as part of the
> > factory data and not like a userspace blob.
> > I don't see how can it be more direct, its the same setup as when
> > getting pre-cal
> > data for most devices currently.
> Indeed, not sure how it could be more direct than it already is. I’m open to suggestions though.
> > I am adding Thibaut who is the author of the platform driver.
next prev parent reply other threads:[~2022-02-02 18:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 22:17 [PATCH] ath10k: support bus and device specific API 1 BDF selection Robert Marko
2021-10-14 11:54 ` Christian Lamparter
2021-10-14 12:01 ` Robert Marko
2021-10-14 13:23 ` Christian Lamparter
2021-12-07 18:06 ` Kalle Valo
2021-12-07 18:09 ` Kalle Valo
2021-12-08 12:21 ` Robert Marko
2021-12-08 14:07 ` Christian Lamparter
2021-12-17 12:06 ` Robert Marko
2021-12-17 12:25 ` Thibaut
2022-02-02 18:49 ` Robert Marko [this message]
2022-02-16 13:38 ` Robert Marko
2022-02-16 21:19 ` Christian Lamparter
2022-02-16 21:55 ` Thibaut
2022-05-03 15:58 ` Robert Marko
2022-05-04 7:48 ` Kalle Valo
2022-05-06 6:19 ` Kalle Valo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).