archive mirror
 help / color / mirror / Atom feed
From: Francesco Magliocca <>
Subject: Bug in Memory Layout of rx_desc for QCA6174
Date: Fri, 29 Oct 2021 16:43:53 +0200	[thread overview]
Message-ID: <> (raw)

Hi, sorry for the late reply, have had rough times.
Yes I can work on a patch, I'll try to get something working by the
end of the week.

> Heh, I was also about to ask about that as well :) The firmware is
> supposed to handle length differences but clearly it's not.

In fact, I see that the driver notifies the firmware about the offset
of the various fields of the data structure,
so this made me think about the firmware. I still can't figure out
what wifi packet is causing this problem...

Anyways I'll work on a patch abstracting the various representations out.
I just ask that you be a little bit patient with me, because this is
the first time I contribute to the kernel,
so I may be making mistakes

ath10k mailing list

             reply	other threads:[~2021-10-29 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 14:43 Francesco Magliocca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-18  7:28 Bug in Memory Layout of rx_desc for QCA6174 Francesco Magliocca
2021-09-21  9:21 ` Kalle Valo
2021-10-29  9:07   ` Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).