From: Ralf Baechle <ralf@linux-mips.org>
To: Jonathan Day <imipak@yahoo.com>
Cc: Kaz Kylheku <kaz@zeugmasystems.com>, linux-mips@linux-mips.org
Subject: Re: CFE problem: starting secondary CPU.
Date: Sat, 7 Oct 2006 11:53:38 +0100 [thread overview]
Message-ID: <20061007105338.GA571@linux-mips.org> (raw)
In-Reply-To: <20061007021523.38254.qmail@web31512.mail.mud.yahoo.com>
On Fri, Oct 06, 2006 at 07:15:23PM -0700, Jonathan Day wrote:
> I've seen the case where the second CPU did not start
> on a Broadcom 1250 running a 64-bit kernel, but I
> don't know if anyone has a good solution. I just
> rigged the values in the Linux kernel so that it knows
> about the second CPU. It's a godawful hack, but I
> needed something quick at the time.
>
> Personally, I am not a fan of CFE and would love to
> know if there's a better way to bootstrap.
Firmware is a stepchild and all implementations have in common that they're
hated by they're users. And my grief is there are way to many different
firmwares for MIPS systems.
Ralf
next prev parent reply other threads:[~2006-10-07 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 23:58 CFE problem: starting secondary CPU Kaz Kylheku
2006-10-06 23:58 ` Kaz Kylheku
2006-10-07 2:15 ` Jonathan Day
2006-10-07 10:53 ` Ralf Baechle [this message]
2006-10-07 22:10 ` girish
2006-10-08 21:35 ` Jonathan Day
2006-10-09 13:25 ` Ralf Baechle
2006-10-09 19:12 ` Jonathan Day
2006-10-09 19:42 ` Mark E Mason
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 2:10 Kaz Kylheku
2006-10-09 2:10 ` Kaz Kylheku
2006-10-10 17:20 Kaz Kylheku
2006-10-10 17:20 ` Kaz Kylheku
2006-10-10 17:53 ` Mark E Mason
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=20061007105338.GA571@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=imipak@yahoo.com \
--cc=kaz@zeugmasystems.com \
--cc=linux-mips@linux-mips.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.