From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Robertson, Joseph M." <joseph.robertson@sanmina-sci.com>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Xilinx SystemACE device driver
Date: Fri, 13 Jul 2007 11:36:08 -0600 [thread overview]
Message-ID: <fa686aa40707131036k1bc5f2c4t701a44e0ef25acc8@mail.gmail.com> (raw)
In-Reply-To: <939D37AEB47F1F49B88FAB6599B6023501A17210@hsv1dafpew02.das.gov.sanm.corp>
On 7/13/07, Robertson, Joseph M. <joseph.robertson@sanmina-sci.com> wrote:
>
> Hi,
>
> Ok, so outlook is a problem. The horror is that, where I work thats all I
> can use. They block all the outside systems like gmail, yahoo, etc. So
> under linux, I have to use the web access for outlook. ugh.
> Why I work here I don't know, they think all software HAS to be bought.
>
> Um, so your patch creates another xsysace.c file, all by itself, which is a
> NEW driver?
> This replaces the 8 files of the previous driver? What happens to all the
> low level funcs?
>
> Where can I get your 2.6.22 tree to see how this is all supposed to go
> together? Is there a tar.bz2 package?
Start with installing 'git'. http://git.or.cz/
Then clone Linus' tree:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
if you're company blocks the git port, then you can use HTTP instead:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
There are a number of different git repos out there with virtex
support integrated, but I'm going to use the example of my tree... (I
rebased my tree onto 2.6.22, so it's very up to date)
$ git fetch git://git.secretlab.ca/git/linux-2.6.git virtex-dev:virtex-dev
(Again, you can use http:// if the git port is blocked)
Now you'll have a branch in your git tree called 'virtex-dev' that
includes my patchset.
You can checkout that branch with:
$ git branch mybranch virtex-dev
$ git checkout mybranch
You can view the patchset with:
$ gitk virtex-dev
You can look at in individual patch with:
$ git show <SHA1 id>
(All git commits are identified with a SHA1 hash; you'll see them in
gitk, or when you do a 'git log)
Also, you can view the tree online at:
http://git.secretlab.ca/cgi-bin/gitweb.cgi?p=linux-2.6.git;a=summary
If you click on the 'commitdiff' link for a patch, followed by
'plain', you should get a downloadable version of the patch.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-07-13 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070712225138.13213.38257.stgit@trillian>
[not found] ` <939D37AEB47F1F49B88FAB6599B6023501A1720B@hsv1dafpew02.das.gov.sanm.corp>
2007-07-13 15:41 ` [PATCH] Xilinx SystemACE device driver Grant Likely
2007-07-13 16:04 ` Robertson, Joseph M.
2007-07-13 17:36 ` Grant Likely [this message]
2007-07-14 5:05 ` OT " David H. Lynch Jr.
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=fa686aa40707131036k1bc5f2c4t701a44e0ef25acc8@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=joseph.robertson@sanmina-sci.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).