Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code
From: Kjetil Oftedal <hidden>
Date: 2009-10-08 13:24:43
Also in:
linux-devicetree, sparclinux
Possibly related (same subject, not in this thread)
- 2009-10-16 · Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code · Grant Likely <hidden>
- 2009-10-15 · Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code · Stephen Rothwell <hidden>
- 2009-10-15 · Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code · Grant Likely <hidden>
- 2009-10-15 · Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code · Stephen Rothwell <hidden>
- 2009-10-08 · Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code · David Miller <hidden>
On Wed, 7 Oct 2009, David Miller wrote:
From: Chris Newport <redacted> Date: Thu, 8 Oct 2009 02:29:25 +0100 (BST)quoted
Sun4d has never had SMP support andWrong.quoted
this is apparantly problematic due to Cray interlectual property causing a lack of bus documentation.XBUS documentation is not available, but we fully know how to program the SBUS interrupt controller and whatnot. It's all there in the sun4d interrupt and SMP support and it did work just fine at one point. Amusingly the SBUS interrupt stuff on sun4d is a very close sibling to the IMAP/ICLR scheme used on sun4u.
The Sun4d SMP support exists, but is broken in 2.6. And the UP support is buggy. At least on my test-setup, the kernel is unable to load userland from scsi-drives. Dropping the sun4 32-bit SPARC is a bit counterproductive when considering the resent effort to unify sparc64 and sparc arch-branches ?