> By supported i mean it is available in the public eCos tree and the > recommended toolchain works (apart from with JFFS2, which is a well > know issue).
This is a good example of what I was talking about with regards to tool chains. I can't imagine that there's a problem per se with JFFS2 and a given tool chain, but rather with the public eCos JFFS2 code in general. > The eCosCentric code is private. You need to license it and people > here on this list have no access to it so will not be able to give you > answer to questions. But then, if you have access to it, you have > payed your license fee and will have a support contract, so there is > no need to ask here... The code bases aren't all that different. Most of the stuff in the eCosPro tree is support for platforms that aren't in the public trees yet. > There is also people who have EABI working in there own private > trees. However this has not yet made it back into the eCos CVS tree. I will gladly make the changes available. I just thought we might test it a bit more. > To me, supported means it is in the official eCos tree and you can ask > questions here and you will likely get answers. Well, I can offer up a patch set, but can't guarantee it'll go in. It'll probably be included in the 3.0 release though, so I'm not too worried about it for the time being. I can guarantee that if anyone asks questions, I'll do my best to answer them. --Chris -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
