From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
Date: Sat, 31 Dec 2005 11:34:50 -0500 [thread overview]
Message-ID: <43B6B32A.5060606@dlasys.net> (raw)
In-Reply-To: <43B601CC.1000102@secretlab.ca>
Grant Likely wrote:
> David H. Lynch Jr. wrote:
>
> Since the E-12 is a commercially available board, it would be useful to
> have the patches on the ML, even if they don't get applied to mainline.
So at what state should things be at before posting them ?
Right now:
The basic E-12 stuff is complete - though it couls use some polish. It
was based on the ML300 code, and almost certainly overlaps and conflicts
with your ML403 work. I would be happy to reconcile them, but I would
need to know what to work against.
I am not a git expert at this point. I am working against the 2.6.14.5
source3 on kernel.org. There are numerous git trees what is the right one ?
The serial/console drivers for the "Keyhole" - a bidirectional link
between a Linux/Windows development host and the E-12, and the Xilinx
UartLite are in (hopefully) late debugging, Output is probably complete,
UartLite input needs testing, Keyhole input needs alot of work - among
other things the host side is still only a display, so it is somewhat
difficult to do the Linux input side.
next prev parent reply other threads:[~2006-01-02 10:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 10:29 [PATCH 0/8] Migration to platform bus for Virtex devices Grant Likely
2005-12-30 10:29 ` [PATCH 4/8] Add Virtex-4 FX to cpu table Grant Likely
2005-12-30 10:29 ` [PATCH 1/8] Move xparameters.h into xilinx specific directory Grant Likely
2005-12-30 10:29 ` [PATCH 2/8] Add xparameters file for Xilinx ML403 reference design Grant Likely
2005-12-30 10:29 ` [PATCH 3/8] Generalize Xilinx Virtex-II/IV support files Grant Likely
2005-12-30 10:29 ` [PATCH 6/8] Migrate Xilinx Vertex support from the OCP bus to the platfom bus Grant Likely
2005-12-30 10:29 ` [PATCH 5/8] defconfigs for Xilinx ML300 and ML403 reference designs Grant Likely
2005-12-30 10:29 ` [PATCH 7/8] Migrate ML300 reference design to the platform bus Grant Likely
2005-12-30 10:29 ` [PATCH 8/8] Add support for Xilinx ML403 reference design Grant Likely
[not found] ` <43B5E37A.4020008@dlasys.net>
2005-12-31 3:58 ` Grant Likely
2005-12-31 16:34 ` David H. Lynch Jr. [this message]
2006-01-02 16:26 ` Grant Likely
2006-01-04 6:00 ` [RFC] Pico E12 (Xilinx V4) patches to 2.6.15 David H. Lynch Jr.
2006-01-04 23:18 ` RESEND:[RFC] " David H. Lynch Jr.
[not found] ` <43BF0736.4050703@secretlab.ca>
2006-01-07 6:55 ` David H. Lynch Jr.
2006-01-08 21:40 ` [RFC] Patches for Xilinx UartLite " David H. Lynch Jr.
[not found] <20060101010006.EACCA6897A@ozlabs.org>
[not found] ` <43B8DAB3.2010001@ozlabs.org>
2006-01-02 8:00 ` [PATCH 8/8] Add support for Xilinx ML403 reference design Grant Likely
[not found] <20060103010004.85C2268979@ozlabs.org>
[not found] ` <43BA2944.5030903@ozlabs.org>
2006-01-03 8:08 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 8:12 Paula Saameño
2006-01-03 8:24 ` Grant Likely
2006-01-03 8:29 ` Paula Saameño
2006-01-03 8:30 ` Grant Likely
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=43B6B32A.5060606@dlasys.net \
--to=dhlii@dlasys.net \
--cc=grant.likely@secretlab.ca \
--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).