From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Chris Healy <cphealy@gmail.com>, Kyle McMartin <kyle@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Marek <mmarek@suse.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Fate of ihex2fw tool
Date: Wed, 17 Oct 2018 09:43:28 +0200 [thread overview]
Message-ID: <20181017074328.GB25537@kroah.com> (raw)
In-Reply-To: <CAHQ1cqGzq5k5xVzngJo03eKn03hg43AMQ6r2p129dic9wbm=jw@mail.gmail.com>
On Tue, Oct 16, 2018 at 10:36:15PM -0700, Andrey Smirnov wrote:
> Everyone:
>
> Since commit 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware:
> delete in-kernel firmware"):
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.19-rc7&id=5620a0d1aacd554ebebcff373e31107bb1ef7769
>
> firmware/ihex2fw.c is gone from the source tree and with it ihex2fw
> tool used to generate sruct ihxed_binrec {} filled images (.ihex ->
> .fw) consumed by request_ihex_frimware().
>
> I tried looking for that too in
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> but couldn't find it there.
>
> Is there a new/different source tree it can be found nowadays?
> Or is there another established tool that can do .ihex -> .fw
> conversion that is expected to be used instead of ihex2bin?
We've all had to write this utility over and over again over the years,
so why not just submit a patch to add this tool back under tools/ ?
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-17 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 5:36 Andrey Smirnov
2018-10-17 7:43 ` Greg Kroah-Hartman [this message]
2018-10-17 16:34 ` Andrey Smirnov
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=20181017074328.GB25537@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kyle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®