From: Grant Likely <glikely@gmail•com>
To: linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: [PATCH 0/2] RFC: Port Virtex-II Pro code to use the platform bus
Date: Sun, 11 Sep 2005 00:57:05 -0600 [thread overview]
Message-ID: <528646bc05091023575d640a6e@mail.gmail.com> (raw)
In-Reply-To: <528646bc0509100033167dae7f@mail.gmail.com>
BTW, I'll be out of town and computer-free until Sept. 19, so I won't
answer any comments until then.
Cheers,
g.
On 9/10/05, Grant Likely <glikely@gmail•com> wrote:
> Here is my work to date to bring the V2Pro port over to the platform
> bus. I don't expect these to be accepted as-is, but I'm looking for
> comments before I get it polished.
>=20
> Should apply cleanly against 2.6.13 (but may require the TLB patch first)
> http://patchwork.ozlabs.org/linuxppc/patch?id=3D2058
>=20
> Patch 1: changes from the ML300 perspective. I temporarly don't have
> access to an ML300 so this is untested (but it compiles). Could
> somebody please test this for me?
>=20
> Patch 2: example patch for another V2PRO based board. This isn't
> really acceptable for mainline because it's not based on a reference
> or published FPGA design, but it shows the work required to bring up
> another board. It also shines some light on what code should be
> common between all V2Pro ports (which I'm working on). This one runs
> on a 2VP4-FG456 eval board (pls ignore all the references to 2VP30).
>
prev parent reply other threads:[~2005-09-11 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 7:33 [PATCH 0/2] RFC: Port Virtex-II Pro code to use the platform bus Grant Likely
2005-09-11 6:57 ` Grant Likely [this message]
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=528646bc05091023575d640a6e@mail.gmail.com \
--to=glikely@gmail$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/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