On 2010-08-16, Scott Wood wrote:
> On Fri, Aug 13, 2010 at 09:22:21PM +, Grant Edwards wrote:
> At one point in the legacy NAND code, a distinction was made when
> reading between completely skipping bad blocks, and filling the
> buffer with zeroes in place of the bad blocks. It looks like
>
On Fri, Aug 13, 2010 at 09:22:21PM +, Grant Edwards wrote:
> I'm using 1.3.4 (that's what's supported by Atmel). While that's the
> current "released" version, it appears to be over two years old?
>
> I've been reading nand flash docs and source code for a while now, and
> I must admit the mo
On 2010-08-13, Grant Edwards wrote:
> On 2010-07-09, Scott Wood wrote:
>> On Fri, Jul 09, 2010 at 08:56:40AM -0400, Ben Gardiner wrote:
>>
>>> If you are putting an MTD filesystem in that partition then the
>>> filesystem itself will take care of bad blocks that might occur in
>>> the partition d
On 2010-07-09, Scott Wood wrote:
> On Fri, Jul 09, 2010 at 08:56:40AM -0400, Ben Gardiner wrote:
>
>> If you are putting an MTD filesystem in that partition then the
>> filesystem itself will take care of bad blocks that might occur in
>> the partition during runtime. During the flash programming
On Fri, Jul 09, 2010 at 08:56:40AM -0400, Ben Gardiner wrote:
> If you are putting an MTD filesystem in that partition then the
> filesystem itself will take care of bad blocks that might occur in the
> partition during runtime. During the flash programming of this
> filesystem using nand write.jff
On Fri, Jul 9, 2010 at 5:12 AM, Arno Steffen
wrote:
> Sorry another question to that.
>
> As for instance I want to have 10MB for root partion and keep 2 blocks
> extra as reserve for some bad blocks.
> I will erase the hole 10MB+2block, write 10MB. That's what I do in uboot.
>
> But in Kernel I h
Sorry another question to that.
As for instance I want to have 10MB for root partion and keep 2 blocks
extra as reserve for some bad blocks.
I will erase the hole 10MB+2block, write 10MB. That's what I do in uboot.
But in Kernel I have some partition table like this:
{
.name
2010/6/25 Scott Wood :
> On 06/25/2010 05:18 AM, Arno Steffen wrote:
>>
>> 2010/6/24 Scott Wood:
>>>
>>> On 06/24/2010 01:28 AM, Arno Steffen wrote:
does it mean in other words - I don't have to care for the bad block,
can write on the bad block address as it would be ok?
>>>
>>> You
On 06/25/2010 05:18 AM, Arno Steffen wrote:
> 2010/6/24 Scott Wood:
>> On 06/24/2010 01:28 AM, Arno Steffen wrote:
>>>
>>> does it mean in other words - I don't have to care for the bad block,
>>> can write on the bad block address as it would be ok?
>>
>> You can't write directly to that block, bu
2010/6/24 Scott Wood :
> On 06/24/2010 01:28 AM, Arno Steffen wrote:
>>
>> does it mean in other words - I don't have to care for the bad block,
>> can write on the bad block address as it would be ok?
>
> You can't write directly to that block, but it can be included in a range of
> blocks as long
On 06/24/2010 01:28 AM, Arno Steffen wrote:
> does it mean in other words - I don't have to care for the bad block,
> can write on the bad block address as it would be ok?
You can't write directly to that block, but it can be included in a
range of blocks as long as the range is large enough to h
Dear Arno Steffen,
In message you
wrote:
>
> The only thing I have to care is, that I have leave enough space
> between the partitions. As for instance : I need 10 blocks for a
> certain filesystem, give it 12 ? So it could correct 2 bad blocks in
> this range.
If you are dealing with NAND, and
2010/6/23 Scott Wood :
> On Wed, Jun 23, 2010 at 02:40:51PM +0200, Arno Steffen wrote:
>> A short question to handling of bad blocks:
>> My nand shows a few bad blocks (example 10)
>>
>> What is happen when I write / read from that block via nand write / read.
>> Is content than ok (by mapping
On Wed, Jun 23, 2010 at 02:40:51PM +0200, Arno Steffen wrote:
> A short question to handling of bad blocks:
> My nand shows a few bad blocks (example 10)
>
> What is happen when I write / read from that block via nand write / read.
> Is content than ok (by mapping good blocks do that address)?
A short question to handling of bad blocks:
My nand shows a few bad blocks (example 10)
What is happen when I write / read from that block via nand write / read.
Is content than ok (by mapping good blocks do that address)?
Other way around - if I have commands like
"get_kn=nand read.i 0x8000
15 matches
Mail list logo
