[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260206012917.GC943673@ziepe.ca>
Date: Thu, 5 Feb 2026 21:29:17 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Pavan Chebbi <pavan.chebbi@...adcom.com>
Cc: Andy Gospodarek <andrew.gospodarek@...adcom.com>,
Saeed Mahameed <saeedm@...dia.com>, michael.chan@...adcom.com,
linux-kernel@...r.kernel.org, dave.jiang@...el.com,
Jonathan.Cameron@...wei.com, gospo@...adcom.com,
selvin.xavier@...adcom.com, leon@...nel.org,
kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH v3 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device
On Fri, Feb 06, 2026 at 06:54:37AM +0530, Pavan Chebbi wrote:
> Does that make the mechanism clear...
Nothing you have explained is different than how I understand it.
You clearly haven't understood what I'm explaining, please read both
my messages over several times until you get it.
I will help you one last time.
User uses this command:
struct hwrm_port_qstats_input {
__le16 req_type;
__le16 cmpl_ring;
__le16 seq_id;
__le16 target_id;
__le64 resp_addr;
__le16 port_id;
u8 flags;
u8 unused_0[5];
__le64 tx_stat_host_addr;
__le64 rx_stat_host_addr;
};
It sends the command buffer with tx_stat_host_addr set to 0xBAD
It sets num_dma = 0.
Explain what happens.
Jason
Powered by blists - more mailing lists