From: Ameet Patil <appatil@cs•york.ac.uk>
To: Neil Steiner <neil.steiner@vt•edu>
Cc: "Dr. Neil Audsley" <neil.audsley@cs•york.ac.uk>,
Ameet Patil <ameet.patil@cs•york.ac.uk>,
linuxppc-embedded@ozlabs•org
Subject: Re: Inquiring about your Linux 2.6.17.1 port to XUP
Date: Sat, 14 Oct 2006 18:35:33 +0100 [thread overview]
Message-ID: <45311FE5.3080400@cs.york.ac.uk> (raw)
In-Reply-To: <45300A50.2010000@vt.edu>
Hi Neil,
Please help yourself! Everything in
http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/ is for public
access! And yes! You are right...
http://www.cs.york.ac.uk/rtslab/demos/amos/ is not for public.
Do post your comments or bugs (if any) on the linux embedded ppc mailing
list (linuxppc-embedded@ozlabs•org).
cheers,
-Ameet
Neil Steiner wrote:
> Dear Sirs:
>
> I came across a link to
> http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/ on comp.arch.fpga,
> but noticed that http://www.cs.york.ac.uk/rtslab/demos/amos/ requires
> login access, and so I wasn't sure whether or not your Linux 2.6.17.1
> files where intended for public consumption.
>
> I don't have a pressing need for a 2.6 kernel, and have instead been
> following directions from the University of Washington
> (http://www.cs.washington.edu/research/lis/empart/xup_ppc_linux.shtml)
> and Brigham Young University
> (http://splish.ee.byu.edu/projects/LinuxFPGA/configuring.htm) for a 2.4
> kernel, but seeing the link to your site did pique my curiosity.
>
> My question then is simply whether I may refer to your files if they
> prove to be useful, or if they were supposed to be restricted.
>
> Neil
next parent reply other threads:[~2006-10-14 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45300A50.2010000@vt.edu>
2006-10-14 17:35 ` Ameet Patil [this message]
2006-10-14 19:37 ` Gofast float point and 405ep Stelios Koroneos
2006-10-26 0:31 ` System ACE driver - for 2.6 kernel - need help to understand xsa_thread agnel juni
2006-10-26 8:00 ` Ameet Patil
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=45311FE5.3080400@cs.york.ac.uk \
--to=appatil@cs$(echo .)york.ac.uk \
--cc=ameet.patil@cs$(echo .)york.ac.uk \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=neil.audsley@cs$(echo .)york.ac.uk \
--cc=neil.steiner@vt$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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