linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Paula Saameño" <gnathita@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
Date: Tue, 3 Jan 2006 09:29:38 +0100	[thread overview]
Message-ID: <259581790601030029j6fa915f9nfb3869ad41915aa4@mail.gmail.com> (raw)
In-Reply-To: <43BA34C5.9050609@secretlab.ca>

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

Hi Grant,

I´ll try the patches today and I let you know how is going.

See you!

On 1/3/06, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> Paula Saameño wrote:
> > I am working with ML403 as well. Right now, I am using a 2.4.26 kernel,
> > but I would be interested in a 2.6 one, it would be great!!
> >
> > Happy 2006!!
> > Paula Saameno
>
> Thanks Paula.
>
> Can you try the posted patches on your ML403?  It should compile and
> boot with no problems with the reference design.  (However, I got the
> memory size initialization wrong; add mem=64M to the kernel command line)
>
> I'll send a patch to fix the mem size tomorrow.
>
> Thanks,
> g.
>
> >
> > Florian wrote:
> >>> 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?
> >>
> >>
> >> Yes. I am also working on a Virtex-4 system with Linux.
> >> Do you support also a Linux 2.4 tree?
> > Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
> > tracking the virtex support in 2.4.
> >
> > Are you strictly working on 2.4?  Or are you interested in 2.6 as well?
> >
> > Cheers,
> > g.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> (403) 663-0761
>

[-- Attachment #2: Type: text/html, Size: 2318 bytes --]

  reply	other threads:[~2006-01-03  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03  8:12 [PATCH 8/8] Add support for Xilinx ML403 reference design Paula Saameño
2006-01-03  8:24 ` Grant Likely
2006-01-03  8:29   ` Paula Saameño [this message]
2006-01-03  8:30     ` Grant Likely
     [not found] <20060103010004.85C2268979@ozlabs.org>
     [not found] ` <43BA2944.5030903@ozlabs.org>
2006-01-03  8:08   ` Grant Likely
     [not found] <20060101010006.EACCA6897A@ozlabs.org>
     [not found] ` <43B8DAB3.2010001@ozlabs.org>
2006-01-02  8:00   ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 10:29 [PATCH 0/8] Migration to platform bus for Virtex devices 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.
2006-01-02 16:26         ` 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=259581790601030029j6fa915f9nfb3869ad41915aa4@mail.gmail.com \
    --to=gnathita@gmail.com \
    --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).