From: Sascha Hauer <s.hauer@pengutronix.de>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/4] fastboot: Add a ARM Barebox filetype handler
Date: Wed, 17 Feb 2016 08:37:49 +0100 [thread overview]
Message-ID: <20160217073749.GN19372@pengutronix.de> (raw)
In-Reply-To: <1455648888-20678-4-git-send-email-mpa@pengutronix.de>
On Tue, Feb 16, 2016 at 07:54:48PM +0100, Markus Pargmann wrote:
> This will automatically call barebox_update for the transfered file if
> it is an ARM Barebox image and the destination file is defined by some
> update handler.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
> drivers/usb/gadget/f_fastboot.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/usb/gadget/f_fastboot.c b/drivers/usb/gadget/f_fastboot.c
> index 192c0d6eb7f4..ae18d068e93f 100644
> --- a/drivers/usb/gadget/f_fastboot.c
> +++ b/drivers/usb/gadget/f_fastboot.c
> @@ -23,6 +23,7 @@
> #include <clock.h>
> #include <ioctl.h>
> #include <libbb.h>
> +#include <bbu.h>
> #include <boot.h>
> #include <dma.h>
> #include <fs.h>
> @@ -716,6 +717,34 @@ static void cb_flash(struct usb_ep *ep, struct usb_request *req, const char *cmd
> goto out;
> }
>
> + if (filetype == filetype_arm_barebox) {
There are some other barebox image types, like filetype_mips_barebox and
filetype_ch_image, so maybe we should check for them aswell? But then
again, ...
> + struct bbu_data data = {
> + .devicefile = filename,
> + .imagefile = FASTBOOT_TMPFILE,
> + .flags = BBU_FLAG_YES,
> + };
> +
> + if (!barebox_update_handler_exists(&data))
> + goto copy;
... Do we need the filetype check at all? Isn't this check enough? With
existing update handler for a device using barebox_update is the right
way to go, no matter what the filetype check says.
> +
> + fastboot_tx_print(f_fb, "INFOThis is an ARM Barebox image...");
> +
> + data.image = read_file(data.imagefile, &data.len);
> + if (!data.image) {
> + fastboot_tx_print(f_fb, "FAILreading bareboxs");
s/bareboxs/barebox/
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-17 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 18:54 [PATCH 1/4] bbu: Add barebox_update search by device Markus Pargmann
2016-02-16 18:54 ` [PATCH 2/4] bbu: Add function to check if an update handler exists Markus Pargmann
2016-02-16 18:54 ` [PATCH 3/4] fastboot: Fix usage of ubiformat for UBI image transfers Markus Pargmann
2016-02-17 7:29 ` Sascha Hauer
2016-02-17 9:33 ` Markus Pargmann
2016-02-16 18:54 ` [PATCH 4/4] fastboot: Add a ARM Barebox filetype handler Markus Pargmann
2016-02-17 7:37 ` Sascha Hauer [this message]
2016-02-17 10:02 ` Markus Pargmann
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=20160217073749.GN19372@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mpa@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