Am 08.05.2015 um 23:39 schrieb Brian Norris:
> On Fri, May 08, 2015 at 04:26:32PM -0500, Ben Shelton wrote:
>> On 04/27, Brian Norris wrote:
>>> On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
wrote:
> On Tue,
On Fri, May 08, 2015 at 04:26:32PM -0500, Ben Shelton wrote:
> On 04/27, Brian Norris wrote:
> > On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
> > > On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
> > > wrote:
> > > > On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard
On 04/27, Brian Norris wrote:
> On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
> > On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
> > wrote:
> > > On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
> > >> Oh, I thought every driver has to implement that
On 04/27, Brian Norris wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
Oh, I thought every driver has to
On Fri, May 08, 2015 at 04:26:32PM -0500, Ben Shelton wrote:
On 04/27, Brian Norris wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM
Am 08.05.2015 um 23:39 schrieb Brian Norris:
On Fri, May 08, 2015 at 04:26:32PM -0500, Ben Shelton wrote:
On 04/27, Brian Norris wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 7:33 PM, Josh Cartwright wrote:
> On Tue, Apr 28, 2015 at 09:14:26AM +0530, punnaiah choudary kalluri wrote:
>> On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris
>> wrote:
>> > On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
>> >> On Tue, Apr 28,
On Tue, Apr 28, 2015 at 09:14:26AM +0530, punnaiah choudary kalluri wrote:
> On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris
> wrote:
> > On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
> >> On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
> >> wrote:
[..]
> >> Agree that
On Tue, Apr 28, 2015 at 09:14:26AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris computersforpe...@gmail.com
wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
On Tue, Apr 28, 2015 at 7:33 PM, Josh Cartwright jo...@ni.com wrote:
On Tue, Apr 28, 2015 at 09:14:26AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris computersforpe...@gmail.com
wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri
On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris
wrote:
> On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
>> On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
>> wrote:
>> > On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
>> >> Oh, I thought every driver
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
> On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
> wrote:
> > On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
> >> Oh, I thought every driver has to implement that function. ;-\
> >
> > Nope.
> >
> >>
On Wed, Mar 25, 2015 at 7:32 PM, Richard Weinberger wrote:
> Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
> feature. It is useful when the host-platform does not offer
> multi-bit ECC and software ECC is not feasible.
>
> Based on original work by David Mosberger
>
>
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
wrote:
> On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
>> Am 27.04.2015 um 23:35 schrieb Ben Shelton:
>> > I tested this against the latest version of the PL353 NAND driver that
>> > Punnaiah
>> > has been working to upstream
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
> Am 27.04.2015 um 23:35 schrieb Ben Shelton:
> > I tested this against the latest version of the PL353 NAND driver that
> > Punnaiah
> > has been working to upstream (copying her on this message). With a few
> > changes
> > to
On Mon, Apr 27, 2015 at 4:15 PM, Richard Weinberger wrote:
> Am 28.04.2015 um 01:10 schrieb Brian Norris:
>> On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger wrote:
>>> Am 28.04.2015 um 00:53 schrieb Brian Norris:
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
>
Am 28.04.2015 um 01:10 schrieb Brian Norris:
> On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger wrote:
>> Am 28.04.2015 um 00:53 schrieb Brian Norris:
>>> On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
>>> When I build
On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger wrote:
> Am 28.04.2015 um 00:53 schrieb Brian Norris:
>> On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
>>> Am 28.04.2015 um 00:36 schrieb Ben Shelton:
>> When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I
Am 28.04.2015 um 00:53 schrieb Brian Norris:
> On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
>> Am 28.04.2015 um 00:36 schrieb Ben Shelton:
> When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I get the
> following warning here:
>
> In file included
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
> Am 28.04.2015 um 00:36 schrieb Ben Shelton:
> >>> When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I get the
> >>> following warning here:
> >>>
> >>> In file included from drivers/mtd/nand/nand_base.c:46:0:
> >>>
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
> On 04/28, Richard Weinberger wrote:
>> Am 27.04.2015 um 23:35 schrieb Ben Shelton:
>>> I tested this against the latest version of the PL353 NAND driver that
>>> Punnaiah
>>> has been working to upstream (copying her on this message). With a few
On 04/28, Richard Weinberger wrote:
> Am 27.04.2015 um 23:35 schrieb Ben Shelton:
> > I tested this against the latest version of the PL353 NAND driver that
> > Punnaiah
> > has been working to upstream (copying her on this message). With a few
> > changes
> > to that driver, I got it most of
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
> I tested this against the latest version of the PL353 NAND driver that
> Punnaiah
> has been working to upstream (copying her on this message). With a few
> changes
> to that driver, I got it most of the way through initialization with on-die
> ECC
Hi Richard,
On 03/25, Richard Weinberger wrote:
> Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
> feature. It is useful when the host-platform does not offer
> multi-bit ECC and software ECC is not feasible.
>
> Based on original work by David Mosberger
>
> Signed-off-by:
Hi Richard,
On 03/25, Richard Weinberger wrote:
Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
feature. It is useful when the host-platform does not offer
multi-bit ECC and software ECC is not feasible.
Based on original work by David Mosberger dav...@egauge.net
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working to upstream (copying her on this message). With a few
changes
to that driver, I got it most of the way through initialization with on-die
ECC
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
On 04/28, Richard Weinberger wrote:
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working to upstream (copying her on this message). With a few
changes
to
On Mon, Apr 27, 2015 at 4:15 PM, Richard Weinberger rich...@nod.at wrote:
Am 28.04.2015 um 01:10 schrieb Brian Norris:
On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger rich...@nod.at wrote:
Am 28.04.2015 um 00:53 schrieb Brian Norris:
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard
On 04/28, Richard Weinberger wrote:
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working to upstream (copying her on this message). With a few
changes
to that driver, I got it most of the way
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I get the
following warning here:
In file included from drivers/mtd/nand/nand_base.c:46:0:
Am 28.04.2015 um 01:10 schrieb Brian Norris:
On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger rich...@nod.at wrote:
Am 28.04.2015 um 00:53 schrieb Brian Norris:
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
When I build this
On Mon, Apr 27, 2015 at 3:57 PM, Richard Weinberger rich...@nod.at wrote:
Am 28.04.2015 um 00:53 schrieb Brian Norris:
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working to upstream (copying her on this message). With a few
changes
to that
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working
On Wed, Mar 25, 2015 at 7:32 PM, Richard Weinberger rich...@nod.at wrote:
Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
feature. It is useful when the host-platform does not offer
multi-bit ECC and software ECC is not feasible.
Based on original work by David Mosberger
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
Oh, I thought every driver has to implement that function. ;-\
On Tue, Apr 28, 2015 at 8:52 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard
Am 28.04.2015 um 00:53 schrieb Brian Norris:
On Tue, Apr 28, 2015 at 12:42:18AM +0200, Richard Weinberger wrote:
Am 28.04.2015 um 00:36 schrieb Ben Shelton:
When I build this without CONFIG_MTD_NAND_ECC_ON_DIE enabled, I get the
following warning here:
In file included from
Probably not really the feedback you're hoping for at this moment, this
being an RFC, but I spotted two nits anyway.
On Wed, 2015-03-25 at 15:02 +0100, Richard Weinberger wrote:
> --- /dev/null
> +++ b/drivers/mtd/nand/nand_ondie.c
This file makes git am whine: "new blank line at EOF".
>
Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
feature. It is useful when the host-platform does not offer
multi-bit ECC and software ECC is not feasible.
Based on original work by David Mosberger
Signed-off-by: Richard Weinberger
---
drivers/mtd/nand/nand_base.c | 66
Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
feature. It is useful when the host-platform does not offer
multi-bit ECC and software ECC is not feasible.
Based on original work by David Mosberger dav...@egauge.net
Signed-off-by: Richard Weinberger rich...@nod.at
---
Probably not really the feedback you're hoping for at this moment, this
being an RFC, but I spotted two nits anyway.
On Wed, 2015-03-25 at 15:02 +0100, Richard Weinberger wrote:
--- /dev/null
+++ b/drivers/mtd/nand/nand_ondie.c
This file makes git am whine: new blank line at EOF.
+#include
42 matches
Mail list logo