Hi at 26.10.2010 12:56, Andrew wrote: > 26.10.2010 11:07, Erich Titl пишет: >> I _believe_ specialized arch branches should _not_ be the default. The >> default should be as generic as possible, so this probably means a i386 >> architecture, as we har right now. >> >> We cannot and should not force people out of their hardware. >> >> cheers >> >> Erich > i386 in any case is meanless
Sorry, I meant 486 - Bering-uClibc requires at least 16MB of > RAM just to out of box; and requires 64M+ for all features (for ex., > hardware detection script requires that modules will be extracted on > ramdisk - and it's size is more than 20 MB). Wooooo... that is asking for trouble, And 'generic' not always > means 'good for all'. i386 build will be much slower than i686 - as says > tests here (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41989 ), Yes, as I said, is it meant to be with small, possibly embedded devices or is it meant to be a full fledged distro. HWdetection is fun, but meaningless for an embedded device. > compiling test for i686 will add approx 35% more points comparable to > i386 (using Geode LX); on my Athlon II difference in this test was near > 25% for i386 and i686 - IMHO good reason to maintain some branches. Yes, but not complete branches, just the hardware dependent parts. Also I think the main branch should not depend on all the funny things. For example, what sense does it make to detect that a certain board has ISDN hardware if noone ever needs it, all it takes is that there are the drivers available somewhere. Can we make the hardware detection optional? And > even more, difference between i686 and 'higher' CPUs wasn't amazing > (-march=k8 and -march=athlon-xp show worse results, and -march=core2 > shows higher for some % result) - so it isn't actual to support > something more specific than i686. As I said, just the hardware dependent parts. > > Possible, in near future it'll be good to add x86_64 branch (for higher > performance on new hardware - because this distro suitable not only for > home routers) - but it'll require some work and isn't trivial.Especially > if it'll be 'true' cross-compilation, on i386 (or other incompatible) > platform. Right, automatisms are difficult to realize with a multi platform environment. > > Also I think that for i686 branch it'll be good to enable PAE - at least > for NX bit support, which will make LEAF systems less exposed to buffer > overflow-based remote attacks that oriented on taking shell. Again, just on hardware that supports it. I _believe_ for example, that one of our targets is the ALIX board which, at the moment, comes at 256 MB > > In any case, anybody who needs support for specific rare hardware, i486 is _not_ rare, probably more the default on our user base. cheers Erich ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
