From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Nick Dyer <nick@shmanahar.org>
Cc: Andrew Duggan <aduggan@synaptics.com>,
Chris Healy <cphealy@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9] Input: synaptics-rmi4 - add support for F34 V7 bootloader
Date: Mon, 12 Dec 2016 11:03:19 -0800 [thread overview]
Message-ID: <20161212190319.GB10591@dtor-ws> (raw)
In-Reply-To: <20161211201631.GA5882@lava.h.shmanahar.org>
On Sun, Dec 11, 2016 at 08:16:31PM +0000, Nick Dyer wrote:
> On Sun, Dec 11, 2016 at 12:03:49AM -0800, Dmitry Torokhov wrote:
> > On Sun, Dec 11, 2016 at 12:18:26AM +0000, Nick Dyer wrote:
> > > +static void rmi_f34v7_parse_img_header_10_bl_container(struct f34_data *f34,
> > > + const u8 *image)
> > > +{
> > > + int i;
> > > + int num_of_containers;
> > > + unsigned int addr;
> > > + unsigned int container_id;
> > > + unsigned int length;
> > > + const u8 *content;
> > > + struct container_descriptor *descriptor;
> > > +
> > > + BUG_ON(f34->v7.img.bootloader.size < 4);
> >
> > Killing the box because you got bad firmware is not very nice...
> >
> > > +
> > > + num_of_containers = (f34->v7.img.bootloader.size - 4) / 4;
> >
> > Wouldn't
> >
> > num_of_containes = f34->v7.img.bootloader.size / 4 - 1;
> >
> > give the same result but be less "suspicious". The variable is 'int' so
> > for size < 4 we'll get a negative and the loop won't execute.
>
> Neat!
>
> > > +
> > > + for (i = 1; i <= num_of_containers; i++) {
> > > + addr = get_unaligned_le32(f34->v7.img.bootloader.data + i*4);
> > > + descriptor = (struct container_descriptor *)(image + addr);
> >
> > This casts away constness, which is not nice. DOes it still work if you
> > apply the below on top?
>
> I've run it through a few flash cycles with no issues.
>
> Tested-by: Nick Dyer <nick@shmanahar.org>
Great, I'll fold and apply then. Thanks!
--
Dmitry
prev parent reply other threads:[~2016-12-12 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 0:18 [PATCH v9] Input: synaptics-rmi4 - add support for F34 V7 bootloader Nick Dyer
2016-12-11 8:03 ` Dmitry Torokhov
2016-12-11 20:16 ` Nick Dyer
2016-12-12 19:03 ` Dmitry Torokhov [this message]
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=20161212190319.GB10591@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=cphealy@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=rydberg@bitmath.org \
/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;
as well as URLs for NNTP newsgroup(s).