On 2/5/2025 2:12 PM, Dmitry Baryshkov wrote: > On Wed, 5 Feb 2025 at 20:46, Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxx> wrote: >> >> On 2/4/2025 3:05 PM, Dmitry Baryshkov wrote: >>> Hello, >>> >>> With the hopes of getting this into the February linux-firmware release: >>> Please add the following BDF file to the archive. >>> >>> Changes since v1: added regdb from the same archive >>> >>> * description for what hardware this is >>> - Qualcomm Robotics RB3 gen2 platform >>> - WCN6750 WiFi/BT chip controlled via the remoteproc (DSP) >>> * origin of the board file >>> - It has been provided by Qualcomm as a part of the RB3gen2 firmware >>> release, licenced under LICENSE.qcom >>> * ids to be used with the board file >>> - WCN6750 / hw 1.0 >>> bus=ahb,qmi-chip-id=1,qmi-board-id=25,variant=Qualcomm_rb3gen2 >>> * md5sum of each new board file to add >>> >>> 39b270f43cb6d733cde607bf2b23e2be >>> bus=ahb,qmi-chip-id=1,qmi-board-id=25,variant=Qualcomm_rb3gen2.bin >>> bfbd247fe961dffc4e7fb413703fb284 >>> regdb-bus=ahb,qmi-chip-id=1,qmi-board-id=25,variant=Qualcomm_rb3gen2.bin >>> >>> >> >> staged... >> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/commit/ae4407c02a434534590dec3e0ef26b371fd7888b > > It's proably not worth it now, but it might be nice to have a > changelog of any kind. Like 'added BDF for Foo Bar' / 'updated BDF for > Foo Baz'. If that's not too troublesome ;-) > The problem is that our workflow from CLO to our ath fork of linux-firmware doesn't maintain any history, so any description in CLO would not show up in linux-wireless. I actually had a descriptive commit message for the CLO patch, but I was convinced to drop it in favor of the boilerplate messages that our tooling produces. I'm thinking that in the future for community-contributed patches that I'll insert myself into the workflow and rewrite the commit text before pushing to ath/linux-wireless. /jeff
