On Tue, Oct 20, 2015 at 03:32:27PM -0400, Tom Rini wrote:
> On Mon, Oct 19, 2015 at 10:17:46AM +0200, Maxime Ripard wrote:
> > On Sat, Oct 17, 2015 at 04:42:09PM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 17-10-15 15:59, Hans de Goede wrote:
> > > >Hi,
> > > >
> > > >On 15-10-15 14:34, M
On Mon, Oct 19, 2015 at 10:17:46AM +0200, Maxime Ripard wrote:
> On Sat, Oct 17, 2015 at 04:42:09PM +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 17-10-15 15:59, Hans de Goede wrote:
> > >Hi,
> > >
> > >On 15-10-15 14:34, Maxime Ripard wrote:
> > >>Hi everyone,
> > >>
> > >>Here is the second att
On Sat, Oct 17, 2015 at 04:42:09PM +0200, Hans de Goede wrote:
> Hi,
>
> On 17-10-15 15:59, Hans de Goede wrote:
> >Hi,
> >
> >On 15-10-15 14:34, Maxime Ripard wrote:
> >>Hi everyone,
> >>
> >>Here is the second attempt at getting fastboot flashing functions
> >>working on top of a NAND, for arbit
Hi,
On 17-10-15 15:59, Hans de Goede wrote:
Hi,
On 15-10-15 14:34, Maxime Ripard wrote:
Hi everyone,
Here is the second attempt at getting fastboot flashing functions
working on top of a NAND, for arbitraly large images.
While the NAND support itself was quite easy to do, the support for
the
Hi,
On 15-10-15 14:34, Maxime Ripard wrote:
Hi everyone,
Here is the second attempt at getting fastboot flashing functions
working on top of a NAND, for arbitraly large images.
While the NAND support itself was quite easy to do, the support for
the Android sparse images was quite difficult to
Hi everyone,
Here is the second attempt at getting fastboot flashing functions
working on top of a NAND, for arbitraly large images.
While the NAND support itself was quite easy to do, the support for
the Android sparse images was quite difficult to add, and ended up
being a quite huge refactorin
6 matches
Mail list logo