From: <Thomas.Kopp@microchip.com>
To: <mkl@pengutronix.de>
Cc: <Stefan.Althoefer@janztec.com>, <linux-can@vger.kernel.org>
Subject: RE: RE: AW: AW: mcp251xfd: Bad message receiption (1/2)
Date: Tue, 10 Jan 2023 21:40:16 +0000 [thread overview]
Message-ID: <BL3PR11MB6484FC468720BAB0660766A8FBFF9@BL3PR11MB6484.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230110183952.pvtuw5gudefnnyv5@pengutronix.de>
About Head not tail: Whoops, yes correct.
> The correct message counter is 0x100, the wrong one 0x120. That's 2x
> FIFO size. I'd like to know when the FIFO head is wrong for the first
> time, one that results in a data transfer where "old" FIFO contents is
> read. I haven't dumped any data yet.
Not sure what you mean. Do you want the message counter at that point in time?
Thomas
next prev parent reply other threads:[~2023-01-10 21:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 7:44 mcp251xfd: Bad message receiption Stefan Althöfer
2022-12-22 9:07 ` Thomas.Kopp
2022-12-22 10:30 ` AW: " Stefan Althöfer
2022-12-22 13:02 ` Marc Kleine-Budde
2022-12-23 8:18 ` AW: " Stefan Althöfer
2022-12-23 19:25 ` Marc Kleine-Budde
2022-12-24 15:57 ` Marc Kleine-Budde
2022-12-30 22:51 ` AW: " Stefan Althöfer
2023-01-01 10:43 ` Stefan Althöfer
2023-01-04 15:55 ` Stefan Althöfer
2023-01-09 7:10 ` AW: AW: AW: mcp251xfd: Bad message receiption (1/2) Stefan Althöfer
2023-01-10 12:50 ` Thomas.Kopp
2023-01-10 14:53 ` Marc Kleine-Budde
2023-01-10 17:08 ` Marc Kleine-Budde
2023-01-10 18:39 ` Marc Kleine-Budde
2023-01-10 21:40 ` Thomas.Kopp [this message]
2023-01-10 21:50 ` Marc Kleine-Budde
2023-01-10 22:37 ` Marc Kleine-Budde
2023-01-10 22:43 ` Marc Kleine-Budde
2023-01-11 8:17 ` Marc Kleine-Budde
2023-01-11 11:54 ` Marc Kleine-Budde
2023-01-09 7:10 ` AW: AW: AW: mcp251xfd: Bad message receiption (2/2) Stefan Althöfer
2022-12-22 14:51 ` mcp251xfd: Bad message receiption Marc Kleine-Budde
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=BL3PR11MB6484FC468720BAB0660766A8FBFF9@BL3PR11MB6484.namprd11.prod.outlook.com \
--to=thomas.kopp@microchip.com \
--cc=Stefan.Althoefer@janztec.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).