On Wed, 11 Sep 2019 at 14:45, Vincent Wiemann
wrote:
> On 11.09.19 13:00, Rafał Miłecki wrote:
> > On Wed, 11 Sep 2019 at 12:19, Vincent Wiemann
> > wrote:
> >> Hi Rafal,
> >>
> >> better error messages for sysupgrade is a good idea.
> >
> > Hi & let me ask shortly. Did you follow the recent
On 11.09.19 13:00, Rafał Miłecki wrote:
> On Wed, 11 Sep 2019 at 12:19, Vincent Wiemann
> wrote:
>> Hi Rafal,
>>
>> better error messages for sysupgrade is a good idea.
>
> Hi & let me ask shortly. Did you follow the recent development? Saw my
> improvements & pending patches?
>
Sorry, I
On Wed, 11 Sep 2019 at 12:19, Vincent Wiemann
wrote:
> Hi Rafal,
>
> better error messages for sysupgrade is a good idea.
Hi & let me ask shortly. Did you follow the recent development? Saw my
improvements & pending patches?
___
openwrt-devel mailing
Hi Rafal,
better error messages for sysupgrade is a good idea.
On 11.09.19 11:26, Rafał Miłecki wrote:
> On Wed, 19 Jun 2019 at 16:07, Rafał Miłecki wrote:
>> Currently targets can implement platform_check_image() that verifies
>> submitted firmware file. It may return a success or failure.
>>
On Wed, 19 Jun 2019 at 16:07, Rafał Miłecki wrote:
> Currently targets can implement platform_check_image() that verifies
> submitted firmware file. It may return a success or failure.
>
> I'm looking for more complex implementation/solution. I'd like
> firmware validation to provide more info
On 19.06.2019 16:07, Rafał Miłecki wrote:
My question is: what do you find the best way of implementing it?
Today IRC chat log for a reference:
[12:21] guys, would you check my "sysupgrade: extending firmware
validation" e-mail?
[12:21] jow: that possibly affects LuCI
[12:21] blogic: you
