From: Wolfgang Denk <wd@denx.de>
To: saiful.khan@sify.com
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: porting ELDK linux for MBX board
Date: Mon, 18 Dec 2006 22:15:16 +0100 [thread overview]
Message-ID: <20061218211516.6332F353C25@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 18 Dec 2006 18:22:44 +0600." <1166446364.45868f1cabae9@mail.sify.com>
In message <1166446364.45868f1cabae9@mail.sify.com> you wrote:
>
> Hi please suggest me how can i port linuxppc_2_4_devel into mbx board, i m new to this. so plese help me.
This has been done many years ago already. Just use the existing code.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
An Elephant is a mouse with an Operating System. - Knuth
next prev parent reply other threads:[~2006-12-18 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 12:22 porting ELDK linux for MBX board saiful.khan
2006-12-18 21:15 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-19 4:37 Saiful Khan
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=20061218211516.6332F353C25@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=saiful.khan@sify.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;
as well as URLs for NNTP newsgroup(s).