On Mon, 20 Aug 2018 18:08:14 +0200
Miquel Raynal wrote:
> Hi Boris,
>
> Boris Brezillon wrote on Thu, 16 Aug 2018
> 18:22:03 +0200:
>
> > On Thu, 16 Aug 2018 17:30:27 +0200
> > Miquel Raynal wrote:
> >
> > > There should not be a 'nand' command, a 'sf' command and certainly not
> > > a
Hi Boris,
Boris Brezillon wrote on Thu, 16 Aug 2018
18:22:03 +0200:
> On Thu, 16 Aug 2018 17:30:27 +0200
> Miquel Raynal wrote:
>
> > There should not be a 'nand' command, a 'sf' command and certainly not
> > a new 'spi-nand' command. Write a 'mtd' command instead to manage all
> > MTD
On Thu, 16 Aug 2018 17:30:27 +0200
Miquel Raynal wrote:
> +/*
> + * Ensure the MTD device partition list has been initialized already (needed
> for
> + * non DM-compliant devices).
I don't see what this has to do with DM vs non-DM drivers. All MTD
devices are registered to the MTD framework,
On Thu, 16 Aug 2018 17:30:27 +0200
Miquel Raynal wrote:
> There should not be a 'nand' command, a 'sf' command and certainly not
> a new 'spi-nand' command. Write a 'mtd' command instead to manage all
> MTD devices/partitions at once. This should be the preferred way to
> access any MTD device.
On Thu, 16 Aug 2018 17:30:27 +0200
Miquel Raynal wrote:
> There should not be a 'nand' command, a 'sf' command and certainly not
> a new 'spi-nand' command. Write a 'mtd' command instead to manage all
> MTD devices/partitions at once. This should be the preferred way to
> access any MTD device.
5 matches
Mail list logo