All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jayachandran C." <jayachandranc@netlogicmicro.com>
To: wu zhangjin <wuzhangjin@gmail.com>
Cc: "wilbur.chan" <wilbur512@gmail.com>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Support for Netlogic XLR/XLS processors
Date: Fri, 18 Mar 2011 14:36:32 +0530	[thread overview]
Message-ID: <20110318090631.GA8628@jayachandranc.netlogicmicro.com> (raw)
In-Reply-To: <AANLkTi=5-zOAXUr95S-KS3kT4Nm2F8H=6Y9AKGg09iv=@mail.gmail.com>

On Fri, Mar 18, 2011 at 11:26:05AM +0800, wu zhangjin wrote:
> On Mon, Mar 14, 2011 at 10:29 PM, Jayachandran C.
> <jayachandranc@netlogicmicro.com> wrote:
> > On Mon, Mar 14, 2011 at 08:19:22PM +0800, wilbur.chan wrote:
> >> Will kexec be supported on XLS/XLR/XLP ?
> >
> > The patches I have does not support it. I haven't really looked at what
> > is needed in XLR platform code to support kexec, so I'm not sure what it
> > takes to support it for XLR either. Any pointers?
> 
> You can get some information here:
> 
> http://dev.lemote.com/code/linux-loongson-community/wiki/kexec-loongson
> 
> And here:
> 
> http://patchwork.linux-mips.org/project/linux-mips/list/?q=kexec

Will look at this.

> BTW: what about the cpu hotplug support for XL{R, S, P} ?

Not right now. My intial goal for Linux/MIPS is hardware support, i.e.
processor support and then drivers. I can start thinking of feature support
once we have reasonable hardware support in the kernel...
-- 
Jayachandran C.
jayachandranc@netlogicmicro.com                  (Netlogic Microsystems)
jchandra@freebsd.org                               (The FreeBSD Project)

      reply	other threads:[~2011-03-18  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 18:27 [PATCH] Support for Netlogic XLR/XLS processors Jayachandran C.
2011-03-14 12:19 ` wilbur.chan
2011-03-14 14:29   ` Jayachandran C.
2011-03-18  3:26     ` wu zhangjin
2011-03-18  9:06       ` Jayachandran C. [this message]

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=20110318090631.GA8628@jayachandranc.netlogicmicro.com \
    --to=jayachandranc@netlogicmicro.com \
    --cc=linux-mips@linux-mips.org \
    --cc=wilbur512@gmail.com \
    --cc=wuzhangjin@gmail.com \
    /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.