Skip to contentSkip to conversation

[2.6.37] Add jasperforest BSP machine branch

PATCH In review Tom Zanussi 2 participants 2 messages Feb 14, 2011

lore
Share & tools
lore
#0 lore raw

cover [2.6.37] Add jasperforest BSP machine branch

From: Tom Zanussi <[email protected]>

'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which combined with the Intel 3420 PCH chipset (Ibex Peak) make up the 'Picket Post' CRB this BSP was developed on.

This adds the machine branch for the jasperforest BSP.

While developing it, I ran into problems with the board hanging during boot, which was caused by the lttng commit reverted by this patchset. Thanks to Bruce Ashfield for pointing out the possibly faulty commit.

The bad commit also caused the same hang in the sugarbay BSP if I advanced the SRCREV past the lttng commits, so it should also be reverted from the sugarbay branch. I can submit a patch for that too, or it can just be cherry-picked into the sugarbay branch if that's easier (it doesn't affect qemux86-64, which is why I didn't just revert it in common-pc-64 or standard).

Please pull.

Thanks,

Tom

Pull URL: git://git.pokylinux.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/yocto/standard/common-pc-64/jasperforest Browse:
http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/yocto/standard/common-pc-64/jasperforest

Tom Zanussi (1):
Revert "nmi-safe-kernel/x86_64-page-fault-nmi-safe"

 arch/x86/mm/fault.c |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)
#1 lore raw
Quoted 7 lines · Tom Zanussi

From: Tom Zanussi <[email protected]>

'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which combined with the Intel 3420 PCH chipset (Ibex Peak) make up the 'Picket Post' CRB this BSP was developed on.

This adds the machine branch for the jasperforest BSP.

Aha. This answers my question in my last email (ignore that question), this is fine.

Quoted 4 lines

While developing it, I ran into problems with the board hanging during boot, which was caused by the lttng commit reverted by this patchset. Thanks to Bruce Ashfield for pointing out the possibly faulty commit.

Good (that we found it), bad that it caused you some pain.

Quoted 7 lines

The bad commit also caused the same hang in the sugarbay BSP if I advanced the SRCREV past the lttng commits, so it should also be reverted from the sugarbay branch.  I can submit a patch for that too, or it can just be cherry-picked into the sugarbay branch if that's easier (it doesn't affect qemux86-64, which is why I didn't just revert it in common-pc-64 or standard).

I'll revert it everywhere from your confirmation that it was the problem. I staged a full revert here, and was waiting to hear if it helped you or not .. which I now know it does, consider it gone.

Will merge and push this out today.

Cheers,

Bruce

Quoted 23 lines

Please pull.

Thanks,

Tom

Pull URL: git://git.pokylinux.org/linux-yocto-2.6.37-contrib
 Branch: tzanussi/yocto/standard/common-pc-64/jasperforest Browse:
http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/yocto/standard/common-pc-64/jasperforest

Tom Zanussi (1):
 Revert "nmi-safe-kernel/x86_64-page-fault-nmi-safe"

 arch/x86/mm/fault.c |    4 +---

 1 files changed, 1 insertions(+), 3 deletions(-)

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"