All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Konovalov <akonovalov@ru.mvista.com>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx git tree at source.mvista.com
Date: Thu, 24 May 2007 17:08:36 +0400	[thread overview]
Message-ID: <46558E54.80909@ru.mvista.com> (raw)
In-Reply-To: <465561A4.9020403@dlasys.net>

Hi David,

David H. Lynch Jr. wrote:
> Andrei Konovalov wrote:
>> Hello,
>>
>> My Xilinx Virtex Development tree is now alive again.
>>
>> Please use the dev branch (master is just the ko copy):
>> http://source.mvista.com/git/gitweb.cgi?p=linux-xilinx-26.git;a=shortlog;h=dev
>> Currently it has a patch to enable the framebuffer
>> on ML403 and ML300 plus TEMAC driver that uses
>> the PHY lib (FIFO mode support only).
>> The TEMAC driver is work in progress.
>> In the queue are SGDMA TEMAC support, and SPI driver
>> (master only).
>>
>> My concern is that the TEMAC driver uses the "level 1 drivers" from EDK 9.1.
>> The comments / opinions on how to get this driver (not the current incomplete
>> version of course) accepted into the ko tree are very welcomed.
>>   
> I have an almost working FIFO TEMAC driver. It is similarly based.
> it started out based on the Trek webserver sample

Is this a reference design by Xilinx? Linux based or standalone?

> I spent probably 3-4 days de-EDKing it into something that fit into a
> single source and was closer to ko norms.
> It is based on approximately the EDK 8.1 stuff. You are welcome to it,
> if it could be helpful in anyway.
> I am all for getting an acceptable driver into the ko tree.

You could post your driver to the list when you think it is in good enough shape.
If your driver is based on the linux TEMAC driver from EDK, it shouldn't
be very different from my version (my added value is mostly replacing the
custom PHY code with the PHY lib stuff). Then we could merge our drivers (or
whatever would make sense).

I would be interested to have a look at your current code just to see
how much has it cost to "de-EDK" the FIFO part. You could email me
your (even not quite working) driver privately if you want.


Thanks,
Andrei

  reply	other threads:[~2007-05-24 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24  8:53 Xilinx git tree at source.mvista.com Andrei Konovalov
2007-05-24  9:57 ` David H. Lynch Jr.
2007-05-24 13:08   ` Andrei Konovalov [this message]
2007-05-24 15:42     ` Wolfgang Reissnegger
2007-05-25  1:49       ` David H. Lynch Jr.
2007-05-25  4:26         ` Wolfgang Reissnegger
2007-05-28 23:30           ` John Williams
2007-05-29  8:07             ` Andrei Konovalov
2007-05-25  0:47     ` David H. Lynch Jr.
2007-06-12 10:29 ` Esben Nielsen
2007-06-12 17:09   ` Dale Farnsworth

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=46558E54.80909@ru.mvista.com \
    --to=akonovalov@ru.mvista.com \
    --cc=dhlii@dlasys.net \
    --cc=linuxppc-dev@ozlabs.org \
    --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.