All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller
Date: Wed, 20 Apr 2011 08:12:25 +0000	[thread overview]
Message-ID: <4DAE9569.1050905@gaisler.com> (raw)
In-Reply-To: <1303229239-21551-6-git-send-email-daniel@gaisler.com>

crn@post.netunix.com wrote:

>
>
> On Wed, 20 Apr 2011, Daniel Hellstrom wrote:
>
>>>
>> I agree that it would be nicer, however I think the SUNs will never 
>> be booted on CPU1 anyway? Anyways, I think this should go into 
>> another patch series.
>
>
> You cannot assume this, sun4d and AFAIK all 64bit systems will boot on
> the first non-blacklisted CPU found.
> For example, it is perfectly OK to have no CPU present on board0 slot0
> in which case the SS1000 will boot using CPU1.

Sorry I meant the UP 32-bit SUNs, some if not all SMP 32-bit SUNs 
apparently use the boot_cpu_id Sam is talking about. Have you tried 
booting on CPU1 with a UP Linux kernel on the SS1000 machine?

I still believe that the changes should go into a separate patch series 
though.

Thanks,
Daniel

  parent reply	other threads:[~2011-04-20  8:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 16:07 [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller registers Daniel Hellstrom
2011-04-19 18:47 ` [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller Sam Ravnborg
2011-04-20  7:02 ` Daniel Hellstrom
2011-04-20  7:39 ` crn
2011-04-20  8:12 ` Daniel Hellstrom [this message]
2011-04-20  8:15 ` David Miller
2011-04-20  8:35 ` Daniel Hellstrom
2011-04-20  8:39 ` David Miller
2011-04-20  8:44 ` Daniel Hellstrom
2011-04-20  8:45 ` David Miller
2011-04-20  8:46 ` crn
2011-04-20  9:06 ` Sam Ravnborg
2011-04-20  9:38 ` Josip Rodin
2011-04-20 10:44 ` Sam Ravnborg
2011-04-20 10:47 ` Daniel Hellstrom
2011-04-20 11:25 ` Daniel Hellstrom

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=4DAE9569.1050905@gaisler.com \
    --to=daniel@gaisler.com \
    --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.