[OpenWrt-Devel] [PATCH] malta: disable mips16

[John Crispin]

On 27/08/2015 10:50, Dirk Neukirchen wrote:
> On 27.08.2015 09:27, Yousong Zhou wrote:
>> On 27 August 2015 at 12:02, Dirk Neukirchen <dirkneukirchen at web.de> wrote:
>>> - it causes issues with qemu versions < 2.2
>>> should fix issues with Ubuntu 14.03 LTS (qemu 2.0)
>>> errors are:
>>> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
>>>
>>
>> But it's a bug within qemu.  I have a simple script [1] for building
>> qemu at least v2.3.0 from source code.
>>
>>  [1] https://github.com/yousong/build-scripts/blob/master/build-qemu.sh
>>
>>                 yousong
>>
> 
> MIPS16 is still deactivated on 44 packages so it still can be considered "unstable" 
> /imho

rather then make it 45 and add the kernel i think we should fix stuff.

personally i dont see it feasible to force everyone to use no mips16
because your distro is outdated

that is like saying "lets force 11b always as some users still have
ancient wifi dongles"



> 
> Other reasons to fix:
> - potential code size reduction by using MIPS16 is not important qemu targets

hjaving ne eminent need for size reduction does not mean bloat is acceptable


> - compiling qemu might break and that requires more user action

works fine for me and i had no reports of it being broken so far

> - some ppl dont like to compile software thats available in distro packages

some people just use distros that ship up to date packages

> - Ubuntu LTS will keep 2.0

ermm ... well .. that is ubuntu

> - Debian 8/jessie has 2.1

backports ?

> - its unlikely that qemu will backport fixes to 2.0 version

sure that is why we dont use ancient software

> - its unclear if/when Ubuntu will backport that fix

ermm ... well .. that is ubuntu



> 
> Reasons not to fix:
> - Malta targets developers that want to test features / build test environments ....
> it is expected mostly developers use this target and they know how to either
> handle or circumvent this known issue.

exactly and i think it is fair to expect a developer to be able to setup
a development env

> 
> Most people do not seem to read wiki or search bugtracker for open/known
issues.

some people dont respect the read light and some people dont read
forums, that is not our problem


> Is putting a README into the bin/ dir on "half broken" platforms a better solution ?

as i said before if something is broken fix it rather than hiding the
details

> Some prefix/suffix indicating which qemu version is working with that file ?

HEAD tends to work ;)



> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel