LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Blakeslee <BlakesleeS@embeddedplanet.com>
To: "'Nikhil Bhargava '" <nikhilbhargav_nsit@coolgoose.com>,
	"'dank@kegel.com '" <dank@kegel.com>,
	"'linuxppc-embedded@lists.linuxppc.org '"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: want help regarding toolchain for E8260 Planetcore
Date: Sat, 20 Dec 2003 14:46:30 -0500	[thread overview]
Message-ID: <D73A25AA6E54D511AD74009027B1110F5BAFBB@ORION> (raw)


 I use ELDK(www.denx.de) as the tool chain and the linuxppc_2_4_devel tree
to run on the ep8260

-----Original Message-----
From: Nikhil Bhargava
To: dank@kegel.com; linuxppc-embedded@lists.linuxppc.org
Sent: 12/17/03 11:21 PM
Subject: want help regarding toolchain for E8260 Planetcore


hello,

Thanks for all members of this grp for helping me out on almost all
ocassions when i have a doubt going beyond myself.

I have to port opensource Linux 2.4.X on to an E8260 mpc 8260 target
board from planet core. I will use this development board in testing
some protocol stacks. Can any one tell me what are the most stable
versions of Gcc, Glibc etc should i use. Further what components to
choose and what to discard from the standard os. Moreso, the board
already have a bootloader running so i just need to port the os on it.
In this scenarios how should i go about it. I will be using BDI 2000
emulator/debugger.

I am following Karim's embedded linux book and web resources for this.


Regards,

Nikhil Bhargava


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-12-20 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20 19:46 Steven Blakeslee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-18  4:21 want help regarding toolchain for E8260 Planetcore Nikhil Bhargava

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=D73A25AA6E54D511AD74009027B1110F5BAFBB@ORION \
    --to=blakeslees@embeddedplanet.com \
    --cc=dank@kegel.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nikhilbhargav_nsit@coolgoose.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox