From: Richard Weinberger <richard@nod.at>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Dirk Behme <dirk.behme@de.bosch.com>,
linux-mtd@lists.infradead.org,
boris.brezillon@free-electrons.com,
david.oberhollenzer@sigma-star.at
Subject: Re: [PATCH 0/5] Add flight recorder to MTDRAM
Date: Wed, 06 Dec 2017 21:57:41 +0100 [thread overview]
Message-ID: <1586330.7x2FQLeB9A@blindfold> (raw)
In-Reply-To: <1944158.Wp3g4lm68D@blindfold>
Manfred,
Am Mittwoch, 6. Dezember 2017, 20:59:43 CET schrieb Richard Weinberger:
> > I have uploaded the initial image, the final image and the flight
> > recording.
> >
> > https://sourceforge.net/projects/calculix-rpm/files/ubifs/xattr/
>
> Cool! I'll give it a try.
Hmm, I did:
./replay -e 131072 -w 2048 dump-before.bin record.bin 168167
This applies 168167 to dump-before.bin, right?
So I expect dump-before.bin to match the sha1sum of image-168167.bin.
But it doesn't.
Thanks,
//richard
next prev parent reply other threads:[~2017-12-06 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 8:50 [PATCH 0/5] Add flight recorder to MTDRAM Dirk Behme
2017-12-06 8:50 ` [PATCH 1/5] mtdram: expose write size and writebuf size as module parameters Dirk Behme
2017-12-06 8:50 ` [PATCH 2/5] mtdram: Add flight recorder Dirk Behme
2017-12-06 8:50 ` [PATCH 3/5] mtdram: Allow to enable/disable flight recorder mode at runtime Dirk Behme
2017-12-06 8:50 ` [PATCH 4/5] mtdram: Convert the flight recorder to a ring buffer Dirk Behme
2017-12-06 8:50 ` [PATCH 5/5] mtdram flight recorder: Add checksums Dirk Behme
2017-12-06 10:41 ` [PATCH 0/5] Add flight recorder to MTDRAM Richard Weinberger
2017-12-06 19:44 ` Manfred Spraul
2017-12-06 19:59 ` Richard Weinberger
2017-12-06 20:57 ` Richard Weinberger [this message]
2017-12-07 16:06 ` Manfred Spraul
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=1586330.7x2FQLeB9A@blindfold \
--to=richard@nod.at \
--cc=boris.brezillon@free-electrons.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dirk.behme@de.bosch.com \
--cc=linux-mtd@lists.infradead.org \
--cc=manfred@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.