From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: 2.6.17-rc5 does not build for sparc
Date: Sat, 27 May 2006 22:43:27 +0000 [thread overview]
Message-ID: <4478D60F.9070603@mc.net> (raw)
In-Reply-To: <4478bffd45960@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Krzysztof Helt wrote:
> Hello,
>
> I tried to build the 2.6.17-rc5 for sparc with SMP enabled. The
> kernel was not build due to a missing macro. Here is a patch
> which fixes this (I copied the macro from a sparc64 header).
>
That's not all that is broken. I think I have what could be 4 separate
patches for smp here: (combined in the attached patch)
1. add topology_init - fixes a boot time crash
2. setup cpu_possible_map - actually boot the additional cpu's
3. fix smp related section mismatch warnings
4. add the missing *_can_lock macros
If you are running a local framebuffer, you may encounter a problem with
vmalloc. Adding "migration_cost=10000" to the kernel command line
should cover up the problem.
I haven't had the time to give it a thorough testing and see if it
self-recompiles recently, but I was previously able to successfully
rebuild the kernel with "make -j6" on a dual SuperSPARC II.
Bob
[-- Attachment #2: sparc32-smp-2.6.17-rc4.patch --]
[-- Type: application/patch, Size: 6594 bytes --]
next prev parent reply other threads:[~2006-05-27 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 21:09 2.6.17-rc5 does not build for sparc Krzysztof Helt
2006-05-27 22:43 ` Bob Breuer [this message]
2006-05-28 9:30 ` BERTRAND Joël
2006-05-28 10:27 ` Christian Joensson
2006-05-29 6:03 ` Krzysztof Helt
2006-06-06 4:15 ` David Miller
2006-06-06 4:59 ` Bob Breuer
2006-06-06 5:08 ` David Miller
2006-06-06 7:09 ` Bob Breuer
2006-06-08 11:33 ` Krzysztof Helt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4478D60F.9070603@mc.net \
--to=breuerr@mc.net \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.