All, Sorry if this is a re-post but my last post got a send error message so I'm resending it.
>Shane, > >What do you say ? Subrata, Sorry for the delay, below are my comments: >> arm7tdmi with 50 MHz and little RAM, vs a arm1126 with almost PC style >> hardware. When I looked at your directory structure I was also thinking there would be "ltp/mach/" were patches for specific machines would go so that would address this issue. >>Embedded systems are usually tested remotely, so there may not even be a >>'patch' command be available on the box. Patch only takes up about 50KB where as python (heart of LTP) takes up about 1.9M (python-core plus all required modules). so if someone goes through the hassle of getting python installed I do not think installing patch will be much more effort. However I also understand the concern about reinventing the wheel and then needing to support the new type of wheel :-) when we could just use some method (kconfig + kbuild) that already exists. Maybe this is a good time to discuss in more detail what we see as the major issues that need addressed for LTP to better run on embedded systems. Once we have a list of the major issues we can discuss methods (or utilities) being used by other popular projects in which we may reuse. How do we accomplish identifying the issues: What I would really like to see done is ask for anyone who has used LTP in an embedded system (post to the list) to submit a brief informal write-up of what it took to get LTP working. As part of the write-up they should include a snap-shot of their test results, arch, memory and machine name if not custom. It is important to see the results as LTP, for the most part, worked right out of the box for me but with quite a few failures. It was not until after I tweaked a handful of tests to reflect the resources available on my board did I get almost all test cases to pass. This will end up being quite a bit of data because of the Results file so if the list is not the right place then I would be willing to volunteer my email address as a place for people to email their write-ups and results. This brings up another reason why I wanted to start this embedded imitative, I HAVE tweaked some of the test cases so they would work on my board, how do I know I have not invalidated test by tweaking it too much as I'm certainly not an expert on all the tests. If we make these tweaks part of LTP somehow then they will get visibility and hopefully if something is tweaked wrong then some LTP developer will fix it or let everyone know about the error :-) Regards, Shane ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
