From: "narendra sisodiya" <narendra.sisodiya@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Linux on ML310
Date: Sat, 24 Nov 2007 04:22:18 +0530 [thread overview]
Message-ID: <e3fb97f30711231452t473f7949x901e4921c20ec699@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi, I am working ML310 XUP virtex2Pro board. My task is to port a Linux
2.4.26 on PowerPC405. I am on the mid way
I have following question.
1. Why in every document Linux kernel 2.4.26 is used, can i use
2.6.xxversion. If yes what will be the modifications,
2. In document some are using busybox for making root file system and
in some Yellow Dog Linux. so what are the such possible options?
3. If any body has done some project then Please share your experience
with me.
--
Narendra Sisodiya
MTech (Computer Technology), IIT Delhi
+91-9999232792
http://www.techfandu.org/index.html
[-- Attachment #2: Type: text/html, Size: 713 bytes --]
next reply other threads:[~2007-11-23 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 22:52 narendra sisodiya [this message]
2007-11-23 23:17 ` Linux on ML310 Grant Likely
2007-11-24 0:09 ` narendra sisodiya
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=e3fb97f30711231452t473f7949x901e4921c20ec699@mail.gmail.com \
--to=narendra.sisodiya@gmail.com \
--cc=linuxppc-embedded@ozlabs.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 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).