Sorry for late response, 1.1 release and all 2010/10/20 Wichmann, Mats D <[email protected]>: >> Line 72, we really need to spell out that it is ARMv7, EABI, softfp >> (for 1.1) as there is emerging tendancies in industry to use hardfp too. > I'll take any info I can get here, nobody's given me any details > for this area. Do you have proposed wording?
ARMv7 (ARM EABI, VFP support, softfp float ABI) > >> Lines 127-129, given that GCC 4.5 in MeeGo 1.1 isn't exactly the best >> when it comes to compiler bugs on ARM and some other areas, is there >> an exception to compiler bug fixes as these might be needed to actually >> productize? > > suggestions for a way to say this? I'll poke around and see if there > are objections. 'A MeeGo compliant distribution MUST use the same tool chain and the same compiler options as the reference implementation. The tool chain MAY be patched to solve compiler bugfixes accepted in upstream GCC as long as they do not break ABI or API' maybe? >> Line 187, don't we need more than 'uses 2.6.35 kernel or later'? There >> should be a requirement on the minimum of options to provide on a >> MeeGo install for a userland to run. > > I think so, but so far despite a few references about as detailed > as yours (should have a list of config options), the details haven't > been forthcoming. I think you should include 'config-generic' from MeeGo 1.1 kernel as an appendix with a note saying "Options that are not applicable on your architecture, when your architecture flag (CONFIG_X86 or CONFIG_ARM) is enabled, are not required". This is due to the situation that there's no config-generic, config-generic-x86 (doesn't exist), config-generic-arm (does exist), so config-generic contains CONFIG_X86 :) Arjan should be able to contribute more in this area.. >> Lines 262: there's also a patchlevel (.35) in current MeeGo 1.1 > > Is it important to add this (ref: bash version, which is only listed as 4.0)? Shouldn't change behaviour, but I didn't read too close into what the 40 patches actually are. BR Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
