From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Vincent Winstead" <vwinstead@yahoo.com>
Cc: trini@kernel.crashing.org,
linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Xilinx Virtex-2 PRO FPGA ppc 405 on ML310 board
Date: Wed, 12 Apr 2006 13:52:29 -0600 [thread overview]
Message-ID: <528646bc0604121252r48d93ac0ubf7d60116815c1b5@mail.gmail.com> (raw)
In-Reply-To: <20060412193338.75924.qmail@web52010.mail.yahoo.com>
Please remember to CC the mailing list when replying
On 4/12/06, Vincent Winstead <vwinstead@yahoo.com> wrote:
>
> Now, what does that mean, to get the tree. Does it mean I'll get a li=
st
> of possible kernels that I can download, and then i'll have to choose one=
of
> them to download?
It means you get a clone of the source tree + revision history which
you can easily keep up to date with mainline. For things like Paul's
powerpc and powerpc-merge trees, you need to use it because I don't
think anybody is making .tar.gz snapshots from it.
> Also, how come I have to go through all this 'git' mumbo-jumbo? Why
> can't I just go to kernel.org and grab one of the 2.6 kernels off of ther=
e,
> then untar it? What's so special about the source.mvista.com kernels
> through git and rsync?
If you want to use 2.6: Git is a pretty easy way to keep up to date
with changes other are making on the tree. But no, you don't have to
use it. Some of the maintainers have snapshots generated from their
trees which you can download.
If you use 2.4: You need to use rsync to get the linuxppc-2.4 tree
because I don't think anyone is maintaining .tar.gz of the rsync
snapshot. Email Tom Rini and ask him. The linuxppc-2.4 tree is
special because it's one of the trees that actually has the ML300
patches integrated. Mainline does not.
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> (403) 399-0195
>
>
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 399-0195
next prev parent reply other threads:[~2006-04-12 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 12:55 Xilinx Virtex-2 PRO FPGA ppc 405 on ML310 board Vincent Winstead
2006-04-11 19:46 ` Grant Likely
[not found] ` <20060412172641.32987.qmail@web52014.mail.yahoo.com>
2006-04-12 18:42 ` Grant Likely
[not found] ` <20060412193338.75924.qmail@web52010.mail.yahoo.com>
2006-04-12 19:52 ` Grant Likely [this message]
[not found] ` <20060412214613.10018.qmail@web52004.mail.yahoo.com>
2006-04-12 21:50 ` Grant Likely
2006-04-12 21:55 ` Grant Likely
2006-04-12 22:11 ` Aidan Williams
2006-04-17 21:00 ` Vincent Winstead
2006-04-18 2:45 ` Aidan Williams
[not found] <20060424203047.86885.qmail@web52005.mail.yahoo.com>
2006-04-24 23:02 ` Aidan Williams
2006-04-25 22:21 ` Vincent Winstead
2006-04-27 11:15 ` Aidan Williams
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=528646bc0604121252r48d93ac0ubf7d60116815c1b5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.org \
--cc=vwinstead@yahoo.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).