All of lore.kernel.org
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Alan Wu <alan.wu@mstarsemi.com>
Cc: linux-mips@linux-mips.org
Subject: Re: VPE loader support on 34K
Date: Thu, 26 Mar 2009 09:42:50 +0800	[thread overview]
Message-ID: <49CADD9A.5030508@windriver.com> (raw)
In-Reply-To: <B34CE01D80AD4D309E259934BA1361AA@mstarsemi.com.tw>

Alan Wu wrote:
> Hello,
> 
> I'm porting 2.6.26 Linux on the platform of MIPS 34K. Currently, the uni-processor 
> kernel model(1 VPE) and SMP model (2 VPE) are up and work perfectly.
> 
> Now, I need to port the AP/SP model on a normal Linux uniprocessor kernel model. 
> I'd like to load an application program (ELF ?) into kernel space where this 
> application will run on a Secondary VPE undisturbed by the Linux kernel.
> 
> After I enabled the MIPS_VPE_LOADER [=y] in .config , the kernel is up without
> any error/warning message.
> 
> Please help :
> 
> 1. How to load the application into VPE1 from VPE0 ? (cat XYZapp >/dev/vpe1 ?)

Exactly.

> 2. Is there any sample "Hello World" application for this ? 
> 3. Any specific tool chain needed ?

I recommend you refer to the file, MIPS® SDE Programmers' Guide (.pdf).
http://www.mips.com/products/product-materials/processor/software/

It's easy to build the sample with SDE. And ever I program a sample to output
some messages from UART to validate AP/AP. I think even you can implement the
same to display something from the LED.

Best Regards
Tiejun

> 
> Thanks.
> 
> 
> 
> 
> 
> 

      parent reply	other threads:[~2009-03-26  1:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 14:37 VPE loader support on 34K Alan Wu
2009-03-25 14:37 ` Alan Wu
2009-03-25 15:42 ` Ralf Baechle
2009-03-25 16:03 ` Kevin D. Kissell
2009-03-26  1:42 ` tiejun.chen [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=49CADD9A.5030508@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=alan.wu@mstarsemi.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.