All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: sparclinux@vger.kernel.org
Subject: Re: 2.6.17-rc5 does not build for sparc
Date: Mon, 29 May 2006 06:03:34 +0000	[thread overview]
Message-ID: <447a8eb6efe1f@wp.pl> (raw)
In-Reply-To: <4478bffd45960@wp.pl>

Dnia 28-05-2006 o godz. 0:43 Bob Breuer napisa³:
 
> 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\x10000" to the kernel command line
> should cover up the problem.
> 

Thank you for the patch. It's a pity you haven't post it earlier
as I lost few hours fixing missing topology_init.

Anyway, it is a huge improvement other the current state of
official kernel. Is this patch on its way to the kernel?

> 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.
> 

I was not so lucky. I was able to boot and two cpus were detected
 (Supersparc II) but the machine opened PROM console after
mounting tmpfs filesystem (for the /tmp directory). The harddisk
filesystems were mounted correctly. I will try to look into this
problem.

Krzysztof




  parent reply	other threads:[~2006-05-29  6:03 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
2006-05-28  9:30 ` BERTRAND Joël
2006-05-28 10:27 ` Christian Joensson
2006-05-29  6:03 ` Krzysztof Helt [this message]
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=447a8eb6efe1f@wp.pl \
    --to=krzysztof.h1@wp.pl \
    --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.