All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: "David H. Lynch Jr." <dhlii@dlasys.net>,
	linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
Date: Fri, 30 Dec 2005 20:58:04 -0700	[thread overview]
Message-ID: <43B601CC.1000102@secretlab.ca> (raw)
In-Reply-To: <43B5E37A.4020008@dlasys.net>

David H. Lynch Jr. wrote:
> 	I am working on a port of 2.6.14.5 to the Pico E-12 which is a Xilinx
> Virtex-IV system in a CF card. It is very similar to the ML403 but with
> alot less hardware. I would love to be able to pull a whole tree of the
> stuff you are working on - is there a git, svn, or cvs tree that the
> linuxppc-embedded patches are getting merged into ? and How can it be
> accessed ?
I don't have a public git tree at the moment for the xilinx virtex
stuff.  I can certainly create and maintain one if there is demand.  I
guess it depends on how many people want to colaborate on V2Pro/V4
support.  Anyone else interested?

> 	Right now I am trying to get /init to run - actually it runs but I am
> not getting IO on the console. Anyway, I hope to put out a collection of
> patches when I have it really working. Aside from the Pico  e-12 itself,
> I have Uartlite drivers that are consistent with the way the rest of the
> 2.6 serial drivers are layed out as well as a custom serial driver
> specific to the E-12. The E-12 stuff might not make it into the
> distribution kernel, but I would think there might be some interest in
> the UartLite driver.
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.

> 
> 	Anyway it would be nice to work against whatever all the
> linuxppc-embedded patches are going into.
I'm working off the mainline linux-2.6 tree from kernel.org.  PPC
patches are getting merged into mainline frequently.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

  parent reply	other threads:[~2005-12-31  4:05 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 1/8] Move xparameters.h into xilinx specific directory 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 2/8] Add xparameters file for Xilinx ML403 reference design 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 6/8] Migrate Xilinx Vertex support from the OCP bus to the platfom 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 [this message]
2005-12-31 16:34       ` David H. Lynch Jr.
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.
2005-12-30 10:29 ` [PATCH 7/8] Migrate ML300 reference design to the platform bus Grant Likely
2005-12-30 10:29 ` [PATCH 5/8] defconfigs for Xilinx ML300 and ML403 reference designs Grant Likely
     [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=43B601CC.1000102@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=dhlii@dlasys.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.