public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: david Atkins <david@3adesign.co.uk>,
	 "ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: QCN9274 - x64 - AMD or Intel
Date: Thu, 11 Apr 2024 11:35:23 +0300	[thread overview]
Message-ID: <87jzl4z48k.fsf@kernel.org> (raw)
In-Reply-To: <3ff953f9-d6ce-4e96-9d16-401ddb9ad1d6@quicinc.com> (Jeff Johnson's message of "Wed, 10 Apr 2024 09:57:44 -0700")

Jeff Johnson <quic_jjohnson@quicinc.com> writes:

> On 4/10/2024 7:52 AM, david Atkins wrote:
>
>> 
>> I just built the ath-next branch for my AMD Ryzen 3 4300U system
>> with an 8devices QCN9274 module, it appears to have a new message
>> 
>> memory type 10 not supported
>> 
>> in the dmesg logs
>> 
>> [    2.705656] ath12k_pci 0000:03:00.0: BAR 0 [mem
>> 0xfe200000-0xfe3fffff 64bit]: assigned
>> [    2.705672] ath12k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [    2.705885] ath12k_pci 0000:03:00.0: MSI vectors: 16
>> [    2.705889] ath12k_pci 0000:03:00.0: Hardware name: qcn9274 hw2.0
>> [    3.405328] ath12k_pci 0000:03:00.0: memory type 10 not supported
>> [    3.410796] ath12k_pci 0000:03:00.0: chip_id 0x0 chip_family 0xb
>> board_id 0xc soc_id 0x401a2200
>> [    3.410804] ath12k_pci 0000:03:00.0: fw_version 0x1011001d
>> fw_build_timestamp 2022-12-02 01:16 fw_build_id
>> QC_IMAGE_VERSION_STRING=WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
>> [    3.431347] ath12k_pci 0000:03:00.0: failed to fetch board data
>> for bus=pci,qmi-chip-id=0,qmi-board-id=12 from
>> ath12k/QCN9274/hw2.0/board-2.bin
>> [    3.431375] ath12k_pci 0000:03:00.0: failed to fetch board.bin from QCN9274/hw2.0
>> [    3.431386] ath12k_pci 0000:03:00.0: qmi failed to load bdf:
>> [    3.431387] ath12k_pci 0000:03:00.0: qmi failed to load board data file:-2
>> 
>> I'll try on my other test bed systems, but is it expected that this
>> will get further than this ?
>
> I believe the memory type 10 message can be ignored (I've received
> conflicting information on that)

BTW I noticed the same warning and I reported this to the QCN9274 team a
long time ago but they didn't do anything, sigh. This needs to be fixed
ASAP. A driver should not print errors.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


      parent reply	other threads:[~2024-04-11  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <LO0P123MB4057B28CB310E5A1CEEF92F0D6002@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM>
2024-04-10 14:52 ` QCN9274 - x64 - AMD or Intel david Atkins
2024-04-10 16:57   ` Jeff Johnson
2024-04-10 19:02     ` Jeff Johnson
2024-04-28 12:50       ` david Atkins
2024-05-03  7:07         ` david Atkins
2024-04-11  8:35     ` 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=87jzl4z48k.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=david@3adesign.co.uk \
    --cc=quic_jjohnson@quicinc.com \
    /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