Hi Kamil,
First of all, thanks for your great contribution.
On Jun 25, 2015 at 20:44 PM, Kamil Debski wrote:
>
> Hi Peter,
>
> Thank you for work on this. I have applied this patch to the latest
> kernel and it had some minor merge conflicts that needed to be resolved.
> But apart from this it
Hi Peter,
Thank you for work on this. I have applied this patch to the latest kernel and
it had some minor merge conflicts that needed to be resolved. But apart from
this it compiled and worked in my setup.
My testing procedure was following:
1) I applied your patch to the NAND core
2) I applie
Ping
>
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
> onenand has own bbt(onenand_bbt.c).
>
> Parameterize a few relevant device detail information into a new
> nand_bbt struct, and set some hooks fo
Currently nand_bbt.c is tied with struct nand_chip, and it makes other
NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
onenand has own bbt(onenand_bbt.c).
Parameterize a few relevant device detail information into a new
nand_bbt struct, and set some hooks for chip specified par
4 matches
Mail list logo
