From: Kalle Valo <kvalo@kernel.org>
To: Drew G <gottagit@pm.me>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Missing hw2.1 symlink for WCN6855 in the kernel.org linux-firmware repo.
Date: Thu, 19 Sep 2024 22:48:34 +0300 [thread overview]
Message-ID: <87o74jbf1p.fsf@kernel.org> (raw)
In-Reply-To: <Wfrop8a7fA9t_i7gKRGWjgRBFd5f33ZojAUWrpnEEj6lhw0ciTgw6uOgXSGBR79ni2LaRvKMnU0FgPRxLum6jlssu-M71_67G1s1afnlmPs=@pm.me> (Drew G.'s message of "Thu, 19 Sep 2024 18:54:45 +0000")
Drew G <gottagit@pm.me> writes:
> This simple symlink was added over 2 years ago but still hasn't made
> it into the upstream linux-firmware.git in kernel.org? What is the
> process to make this happen as it means WiFi is broken for people who
> use regularly update from the kernel.org repo? How often are these
> upstream files updated with the latest blobs in this codelinaro repo?
> Thanks
>
> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/commit/c90fbaf6224b73aaebd523e102fe7c78f6a542ad
In linux-firmware the links are created from WHENCE file:
Link: ath11k/WCN6855/hw2.1/regdb.bin -> ../hw2.0/regdb.bin
Link: ath11k/WCN6855/hw2.1/board-2.bin -> ../hw2.0/board-2.bin
Link: ath11k/WCN6855/hw2.1/amss.bin -> ../hw2.0/amss.bin
Link: ath11k/WCN6855/hw2.1/m3.bin -> ../hw2.0/m3.bin
So when you do 'make install' it should create the symlinks.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-09-19 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 18:54 Missing hw2.1 symlink for WCN6855 in the kernel.org linux-firmware repo Drew G
2024-09-19 19:48 ` Kalle Valo [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=87o74jbf1p.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=gottagit@pm.me \
/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.