Thanks Shane, I am also looping in other people associated with CE on Linux, and, whom i met during OLS 2008. Please loop in more people whom you think would be interested in testing Linux with LTP.
Dear Haitao,Tim, Noboru, Michael, Thomas, We are discussing ways to make LTP work on embedded systems in particular. Since, the test suite itself is huge and contains tests related to almost every aspect of the Linux kernel - which is a limitation for embedded systems with limited capacity. Moreover the Memory and FS tests in LTP require huge spaces both in terms of Promary and Secondary Memory. We are discussing ways to address that, so that embedded systems can benefit from usage of LTP. On Mon, 2008-10-20 at 13:30 -0400, Shane Volpe wrote: > Subrata, > I think your idea is a good one, It will keep good track of what has > been changed for each special build making it easier for re-use in > other special builds. I think this approach would address all the > issues. > > Klas, > I understand your concerns but the problem with the version control > (branches) approach is who will maintain and keep up to date all of > the branches? IMHO it is better to keep everything mainstream that > way all stays up to date and is visible to everyone with out checking > out multiple branches. > > All, > Keeping everything mainstream will only work well if there is a good > regression plan established for making sure all patches are exercised > before each release. I think with what we are doing as long as the > patch applies LTP will probably compile and work ok. There needs to be > some regression script that can be run to go through and set all the > special #ifdef's and make sure everything applies ok. > > I have some patches I could submit to get this going, I'm just not > sure on the correct directory naming scheme. > Most of my patches are not because of the arch but because of the > memory limitations. Should there be a directory: > /ltp/patches/mem-limitations/duringruntime-64mb.patch Yes, it can be of that way as well. What i would recommend is to keep keep some arch specific directories like: ltp/patches/arch-specific/arm/*.patch ltp/patches/arch-specific/sh/*.patch and also: ltp/patches/memory-specific/*.patch ltp/patches/storage-specific/*.patch One thing i was talking about is for the Makefile(s) to detect the archs and then automatically apply them. I would counter that. Instead i would prefer users apply the Patches manually from ltp/patches directly, and, then go ahead with build/install/run. 1) Initially ltp/patches/arch-specific/*/*.patch can be applied, which may disable even compilation/installation of certain tests, 2) Then ltp/patches/memory-specific/*.patch & ltp/patches/storage-specific/*.patch can be applied to further prune down things. Shane, if you have some workable apcth, can you please share with us ? Regards-- Subrata > 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
