ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Kalle Valo <kvalo@kernel.org>
Cc: Francesco Dolcini <francesco@dolcini.it>, ath11k@lists.infradead.org
Subject: Re: Silex SX-PCEAX BDF
Date: Tue, 3 Sep 2024 00:59:49 +0200	[thread overview]
Message-ID: <ZtZDZXY04PEYiuCj@gaggiata.pivistrello.it> (raw)
In-Reply-To: <87ikvekoww.fsf@kernel.org>

On Mon, Sep 02, 2024 at 07:20:47PM +0300, Kalle Valo wrote:
> Francesco Dolcini <francesco@dolcini.it> writes:
> > I am using a Silex SX-PCEAX wireless module (QCA2066), and I would
> > like to understand how to get the board file merged into the wireless
> > repository so that this module can just work with ath11k driver.
> >
> > I have some files I received from Silex, but they do not look suitable
> > for integration as they are (board-2_US_EU_JP.bin).
> >
> > Can you help? What should I do?
> 
> Board files are tricky, we should write some documentation about that.

If you have anything available, even if this is not polished, feel free to
share.

> But for starters I recommend filing a new bug to bugzilla:
> 
> https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
> 
> Also include output of these commands:
> 
> strings board-2_US_EU_JP.bin | head -1
> ls -l board-2_US_EU_JP.bin

There was already a bug report opened for what looked like the exact device,
I did update https://bugzilla.kernel.org/show_bug.cgi?id=217509#c9

Please let me know whatever else is needed to make this progress.

Thanks,
Francesco



      reply	other threads:[~2024-09-02 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 12:00 Silex SX-PCEAX BDF Francesco Dolcini
2024-08-29 21:32 ` Francesco Dolcini
2024-09-02 16:20 ` Kalle Valo
2024-09-02 22:59   ` Francesco Dolcini [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=ZtZDZXY04PEYiuCj@gaggiata.pivistrello.it \
    --to=francesco@dolcini.it \
    --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