From: "Pali Rohár" <pali@kernel.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: "Stefan Roese" <sr@denx.de>,
"Elad Nachman" <enachman@marvell.com>,
"Vadym Kochan" <vadym.kochan@plvision.eu>,
"Marek Behún" <kabel@kernel.org>, u-boot <u-boot@lists.denx.de>
Subject: Re: [PATCH 7/7] tools: kwboot: Add knowledge of Marvell's TIM
Date: Mon, 19 Sep 2022 01:02:59 +0200 [thread overview]
Message-ID: <20220918230259.d4od2bc7572uzrys@pali> (raw)
In-Reply-To: <CAFOYHZAt7E5f717vwmx470yJUz+Ht=wKYaigSUOc910toCaHKQ@mail.gmail.com>
On Monday 19 September 2022 10:57:10 Chris Packham wrote:
> Having looked more into mox-imager (and WtpDownloader) I've realised
> that the AlleyCat5 uses something called "TIM" but it's different to
> the format used by Armada-3700. I suspect what I'm actually dealing
> with is a TIMv0 that pre-dates the version used by Armada-3700. All
> the more reason to do something new instead of trying to shoe-horn it
> into one of the existing places. I'll probably end up making a fork of
> your mvebu64boot and adapting it (mox-imager just does too much).
Hello! If that AC5 TIM format is different than A3720 TIM then it really
makes sense to create a new tool. Forking mvebu64boot into completely
new project seems like the easiest way how to achieve working tool
without being afraid to break existing support.
Anyway, is not there any Marvell tool for this AC5 TIM format? Like
A3720 TBB or WtpDownloader?
next prev parent reply other threads:[~2022-09-18 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:54 [PATCH 0/7] arm: mvebu: Support for 98DX25xx/98DX35xx (AlleyCat5) Chris Packham
2022-09-16 4:54 ` [PATCH 1/7] net: mvneta: Add support for AlleyCat5 Chris Packham
2022-09-16 4:54 ` [PATCH 2/7] usb: ehci: ehci-marvell: Support for marvell,ac5-ehci Chris Packham
2022-09-16 4:54 ` [PATCH 3/7] pinctrl: mvebu: Add AlleyCat5 support Chris Packham
2022-09-16 4:54 ` [PATCH 4/7] misc: mvebu: Add sample at reset driver Chris Packham
2022-09-16 4:54 ` [PATCH 5/7] arm: mvebu: Support for 98DX25xx/98DX35xx SoC Chris Packham
2022-09-16 4:54 ` [PATCH 6/7] arm: mvebu: Add RD-AC5X board Chris Packham
2022-09-16 10:58 ` Pali Rohár
2022-09-17 9:03 ` Chris Packham
2022-09-16 4:54 ` [PATCH 7/7] tools: kwboot: Add knowledge of Marvell's TIM Chris Packham
2022-09-16 8:11 ` Pali Rohár
2022-09-16 10:34 ` Chris Packham
2022-09-16 10:50 ` Pali Rohár
2022-09-16 12:36 ` Pali Rohár
2022-09-18 22:57 ` Chris Packham
2022-09-18 23:02 ` Pali Rohár [this message]
2022-09-19 8:24 ` Chris Packham
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=20220918230259.d4od2bc7572uzrys@pali \
--to=pali@kernel.org \
--cc=enachman@marvell.com \
--cc=judge.packham@gmail.com \
--cc=kabel@kernel.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=vadym.kochan@plvision.eu \
/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