Because unfs boot mode is unstable for qemuppc, disable it temporarily. Signed-off-by: Liming Wang <liming.wang@...> --- scripts/runqemu | 6 ++++++ 1 files changed, 6 insertions(+), 0

It's a workaround to fix yocto bug: [Bug 414][PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS Liming Wang (1): scripts/runqemu: disable unfs boot mode for qemuppc

Sorry, I'm wrong, irq2 is not the timer interrupt handler, it's described as: "IRQ2 is cascade interrupt to second interrupt controller". I will re-send the the mail. Liming Wang

preempt_rt kernel forces all irq interrupts to be threaded except some special interrupts. This cascade interrupt belongs to the exceptions. Because irq2 is initialized more early than "kthreadd"

This patch fixes yocto bug: [Bug 1392] qemumips: linux-yocto-rt_3.0 panics at boot Liming Wang (1): mips/rt: convert cascade interrupt to no threaded arch/mips/kernel/i8259.c | 1 + 1

It's a known issue that preempt_rt kernel must convert the main timer interrupt handler to no threaded, otherwise kernel can't work well. Signed-off-by: Liming Wang <liming.wang@...> ---

This patch fixes yocto bug: [Bug 1392] qemumips: linux-yocto-rt_3.0 panics at boot Liming Wang (1): mips/rt: convert timer interrupt handler to no threaded arch/mips/kernel/i8259.c | 1 +

I think that the thing being disputed isn't that ARM is different from PCs, but rather the issue that different ARM SOs do the same thing in different ways. in the early days of the PC we had the

Hi Paul, It seems as if it's this that's causing the problem. I had a 'real' patch file in place and it wasn't being processed during do_unpack. Removing the 'patch=1' fixed this and it was

We need to cc Richard/Saul on this, so they can re-consider and merge this as appropriate. But for me, I'm acking this change. Bruce

Luke: Step back from the keyboard just a bit. :) It's true that the glass isn't completely full--- but it's pretty darned full! And we wouldn't be discussing the various GPL and other violations

It's still in the latest lttng

ok. allow me to give some perspective and background as to why i believe that a bigger discussion is important, and to whom that discussion is important. a few years ago i read what seems like a

At a glance, this seems reasonable to me .. and then I looked a bit more. This is in fact introduced by lttng and the ENIVAL does look wrong. It's worth checking out the latest lttng to make sure that

Hi Chris, FYI patch=1 is no longer necessary as of quite some time ago - the .patch (or .diff) extension is enough to indicate that it's a patch. Are you sure there is no patch of this name

I quite like the wording, actually. :) Gordan

[ok i'm going to do another cross-post in a bit which will give some background and also perhaps some other topics for discussion, but i wanted to cover this first. apologies for people for whom this

Because qemuppc has no graphic emulation, remove console=tty0 and make it run into 3 run level. This can reduce boot time for qemuppc booting. Signed-off-by: Liming Wang

This patch is just a workaround to speed up boot time of qemuppc, because qemuppc has no framebuffer support, no need to start X server for qemuppc. Richard suggested to fix the X scripts so that if

Sorry, I wasn't clear in my original message, but for this to work we will need to declare the specific versions of distros we will consider tested. Cheers, Paul -- Paul Eggleton Intel Open