linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Peter Mendham" <petermendham@computing.dundee.ac.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Patchset to establish sanity in Xilinx Virtex support
Date: Mon, 16 Apr 2007 08:48:52 -0600	[thread overview]
Message-ID: <528646bc0704160748o5c8ae604ma9ae70afcc649058@mail.gmail.com> (raw)
In-Reply-To: <462337AB.5000507@computing.dundee.ac.uk>

On 4/16/07, Peter Mendham <petermendham@computing.dundee.ac.uk> wrote:
> I have applied your patches to a 2.6.20.4 kernel, along with your
> SystemACE driver. I am fully up and running on a simple ML405-based
> system setup with a Uartlite and a SystemACE. (I made the Kconfig
> changes suggested by Dale Farnsworth to my copy). So, thank you very
> much. I appreciate the neatness of your patches, the fact that I now
> have early boot text support on my uartlite port and the fact that
> (somehow) you've shaved a good couple of seconds of my boot time against
> the Xilinx SystemACE driver. Thanks!

Thanks for your feedback.

I'm glad to hear that the driver is faster; I was hoping that was the
case, but I haven't benchmarked it against the Xilinx driver yet.
Please,
please, PLEASE let me know if you have any problems with it.  Any
information you can provide me on your usage would be fantastic.

So, I assume that your rootfs is mounted from the CF card, correct?
If so, very cool.  I hadn't gotten to that point in my testing, so I
didn't know if that would work.  :-)

> In your reply to Mohamed Sadegh Sadri you mentioned that you will be
> publishing your GIT tree with TEMAC support.  Two very quick questions:
> where do I find this, and does it support auto-negotiation properly?  I
> am having serious problems with auto-negotiation and the various
> flavours of driver out there.  It seems like the best long term plan
> would be to use the PHYLIB support to handle the PHY side of things but
> I have only just started looking into this.

I'll be posting it on my git server at http://git.secretlab.ca, and
yes it does support autonegotiation, at least when using the Phy that
is on the ML403 board.  I'm going to take a close look a the TEMAC
patch that Andrei recently posted on the list which makes use of phylib.  It
looks interesting.

Cheers and thanks,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-04-16 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  8:45 Patchset to establish sanity in Xilinx Virtex support Peter Mendham
2007-04-16 14:48 ` Grant Likely [this message]
2007-04-16 16:11   ` Peter Mendham
  -- strict thread matches above, loose matches on Subject: below --
2007-04-15  7:27 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=528646bc0704160748o5c8ae604ma9ae70afcc649058@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=petermendham@computing.dundee.ac.uk \
    /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).