From: Julien Olivain <ju.o@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org,
Stefan Hager <stefan.hager@ginzinger.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v8 10/10] package/tensorflow-lite: new package
Date: Tue, 28 Jan 2025 23:40:12 +0100 [thread overview]
Message-ID: <42a394596365512b8bf4d523042534ae@free.fr> (raw)
In-Reply-To: <20250128170153.2298242-10-james.hilliard1@gmail.com>
Hi James, Stefan,
On 28/01/2025 18:01, James Hilliard wrote:
> From: Stefan Hager <stefan.hager@ginzinger.com>
>
> This package adds the tensorflow lite runtime to buildroot.
>
> Tested-by: Stefan Hager <stefan.hager@ginzinger.com>
> Signed-off-by: Stefan Hager <stefan.hager@ginzinger.com>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
[...]
> diff --git a/package/tensorflow-lite/tensorflow-lite.mk
> b/package/tensorflow-lite/tensorflow-lite.mk
> new file mode 100644
> index 0000000000..433eff3242
> --- /dev/null
> +++ b/package/tensorflow-lite/tensorflow-lite.mk
> @@ -0,0 +1,59 @@
> +################################################################################
> +#
> +# tensorflow-lite
> +#
> +################################################################################
> +
> +TENSORFLOW_LITE_VERSION = 2.11.0
So I finally merged this longstanding tensorflow-lite series.
Thanks again!
The version merged here is a bit outdated already. See:
https://github.com/tensorflow/tensorflow/releases/tag/v2.11.0
from November 2022.
For reference, the latest version, as of today is v2.18.0:
https://github.com/tensorflow/tensorflow/releases/tag/v2.18.0
from October 2024.
So it would be really nice to see updates towards this newer version.
This will probably bring new dependencies too.
Also, for information, tensorflow-lite is in a process to be
renamed to LiteRT. See:
https://developers.googleblog.com/en/tensorflow-lite-is-now-litert/
https://github.com/google-ai-edge/litert
It seems this process will take some time, so I merged this
package with its "old" name anyway.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-28 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 17:01 [Buildroot] [PATCH v8 01/10] package/cpuinfo: new package James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 02/10] package/ruy: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 03/10] package/gemmlowp: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 04/10] package/pthreadpool: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 05/10] package/psimd: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 06/10] package/fp16: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 07/10] package/xnnpack: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 08/10] package/fft2d: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 09/10] package/farmhash: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 10/10] package/tensorflow-lite: " James Hilliard
2025-01-28 22:40 ` Julien Olivain [this message]
2025-01-28 23:00 ` James Hilliard
2025-01-28 22:36 ` [Buildroot] [PATCH v8 01/10] package/cpuinfo: " Julien Olivain
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=42a394596365512b8bf4d523042534ae@free.fr \
--to=ju.o@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=stefan.hager@ginzinger.com \
--cc=thomas.petazzoni@bootlin.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