From: Jason Gunthorpe <jgg@ziepe.ca>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: Andy Gospodarek <andrew.gospodarek@broadcom.com>,
Saeed Mahameed <saeedm@nvidia.com>,
michael.chan@broadcom.com, linux-kernel@vger.kernel.org,
dave.jiang@intel.com, Jonathan.Cameron@huawei.com,
gospo@broadcom.com, selvin.xavier@broadcom.com, leon@kernel.org,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH v3 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device
Date: Thu, 5 Feb 2026 21:29:17 -0400 [thread overview]
Message-ID: <20260206012917.GC943673@ziepe.ca> (raw)
In-Reply-To: <CALs4sv0Pc0dhYvBU_PPawyN=c=fEvn+nq1uvpzjnKGn0BJjc4Q@mail.gmail.com>
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
next prev parent reply other threads:[~2026-02-06 1:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 15:54 [PATCH v3 fwctl 0/5] fwctl/bnxt_fwctl: fwctl for Broadcom Netxtreme devices Pavan Chebbi
2026-01-29 15:54 ` [PATCH v3 fwctl 1/5] fwctl/bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2026-01-29 15:54 ` [PATCH v3 fwctl 2/5] fwctl/bnxt_en: Refactor aux bus functions to be more generic Pavan Chebbi
2026-01-30 11:37 ` Jonathan Cameron
2026-01-30 12:26 ` Pavan Chebbi
2026-02-04 23:44 ` Saeed Mahameed
2026-02-05 4:00 ` Pavan Chebbi
2026-02-05 8:41 ` Pavan Chebbi
2026-01-29 15:54 ` [PATCH v3 fwctl 3/5] fwctl/bnxt_en: Create an aux device for fwctl Pavan Chebbi
2026-01-30 11:39 ` Jonathan Cameron
2026-02-04 23:47 ` Saeed Mahameed
2026-01-29 15:54 ` [PATCH v3 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2026-01-30 12:03 ` Jonathan Cameron
2026-01-30 15:19 ` Jason Gunthorpe
2026-02-05 0:19 ` Saeed Mahameed
2026-02-05 4:25 ` Pavan Chebbi
2026-02-05 15:09 ` Pavan Chebbi
2026-02-05 17:33 ` Jason Gunthorpe
2026-02-05 17:47 ` Andy Gospodarek
2026-02-05 18:42 ` Jason Gunthorpe
2026-02-06 0:19 ` Andy Gospodarek
2026-02-06 0:39 ` Jason Gunthorpe
2026-02-06 1:24 ` Pavan Chebbi
2026-02-06 1:29 ` Jason Gunthorpe [this message]
2026-02-06 4:45 ` Pavan Chebbi
2026-02-09 13:41 ` Andy Gospodarek
2026-02-17 14:43 ` Pavan Chebbi
2026-01-29 15:54 ` [PATCH v3 fwctl 5/5] fwctl/bnxt_fwctl: Add documentation entries Pavan Chebbi
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=20260206012917.GC943673@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Jonathan.Cameron@huawei.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=dave.jiang@intel.com \
--cc=gospo@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=pavan.chebbi@broadcom.com \
--cc=saeedm@nvidia.com \
--cc=selvin.xavier@broadcom.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