NAND review

[Rutger Hofman]

Simon Kallweit wrote:
> Rutger Hofman wrote:
>>> Jonathan Larmour wrote:
>>>> that). But I'm also concerned about possibly having too much 
>>>> layering in Rutger's version for small simple implementations.
>>
>> Well, there is one obvious candidate for being thinned out in my NAND 
>> implementation: the ANC layer that hides the presence of multiple 
>> controllers and/or chips. Making this optional for the (common) case 
>> of one controller and one (or multiple identical) chips will be easy.
> 
> I don't really like that idea, as it cuts flexibility a lot. I think we 
> will see the need to control 2 or more NAND controllers and/or chips at 
> the same time. With Ross's solution this is currently possible and this 
> rare case is where his implementation shines IMHO, because you just 
> simply implement it in the platform instead of trying to implement it 
> generically.

Uhmmm... I am not sure I understand? In my current NAND implementation, 
the platform is free to hide the fact that there are multiple devices by 
having one ANC that handles the multiplicity issues transparently, or 
the platform can configure things so that the multiplicity is made 
public by using multiple ANC structs, or everything in between.

#undef-ing the multiplicity support /within/ the ANC code would be a 
hack to get leaner compiled code when ANCs have only one (type of) 
controller/chip. This leaves in multiplicity by using multiple ANCs anyway.

Rutger