Rutger Hofman wrote:
First, I noticed a few things I would like to clear up in front.
Currently, the NAND subsystem sits in io/flash_nand which I think is
fine. But the devices sit under devs/flash, which is the same location
as for NOR flash. I think we should rename this to devs/flash_nand. I
Rutger Hofman writes:
> Sergei Gavrikov wrote:
> [snip]
>> I see that you started from NAND flash driver for eCos to wire it with
>> UFFS core then. Fortunately or unfortunately I have no NAND flash parts
>> to play with it, and I looked in a side of a UFFS SIMRAM class which was
[snip]
>> file sys
Sergei Gavrikov wrote:
[snip]
I see that you started from NAND flash driver for eCos to wire it with
UFFS core then. Fortunately or unfortunately I have no NAND flash parts
to play with it, and I looked in a side of a UFFS SIMRAM class which was
implemented by UFFS's author to debug and play with
Simon Kallweit wrote:
Simon Kallweit wrote:
Now for the actual design of the synth driver. I think the best way
would be to implement a NAND simulator based on the ONFI
specification. Something similar has been done for the MTD framework,
but I guess other than for inspiration we're not allowe
Simon Kallweit wrote:
Hi there
I merged the NAND code from Rutger into my repo and tried to figure out
how to write synthetic target support, which in my opinion would be a
great addition so we can test future filesystems (UFFS) without a
target, do wear-leveling analysis and stuff like that.
Sergei Gavrikov wrote:
Thank you for your efforts! Can I ask you about UFFS itself? How did it
look for you, Is UFFS stable enough to use it? Thanks to your post about
UFFS I looked on its sources 2 days ago and just tried to know what its a
memory amount. I did stand up a small test sandbox here
On Tue, May 12, 2009 at 10:36:34AM +0200, Simon Kallweit wrote:
> Simon Kallweit wrote:
>> Now for the actual design of the synth driver. I think the best way
>> would be to implement a NAND simulator based on the ONFI
>> specification. Something similar has been done for the MTD
>> framework, but
Simon Kallweit wrote:
Now for the actual design of the synth driver. I think the best way
would be to implement a NAND simulator based on the ONFI specification.
Something similar has been done for the MTD framework, but I guess other
than for inspiration we're not allowed to use that code. So
Hi there
I merged the NAND code from Rutger into my repo and tried to figure out
how to write synthetic target support, which in my opinion would be a
great addition so we can test future filesystems (UFFS) without a
target, do wear-leveling analysis and stuff like that.
First, I noticed a f
