> While you may release an eCos + YAFFS combo under GPL this would require that
> you also need to release the entire code base, including the "application
> code" under GPL. If you want to keep the "application code" under wraps then
> you will likely need to arrange suitable licensing with Aleph One.
>
> If I have misunderstood something, then please help to clarify.
This is why we do not use YAFFS2 in our closed-source, eCos-based, products:
YAFFS2 lib is never included - unfortunately ;-(
However, it does not prevent from evaluating it - hence the port to YAFFS2 ;-)
Emmanuel.
(text/plain)