All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PHY library?
Date: Wed, 21 Nov 2007 10:38:23 -0600	[thread overview]
Message-ID: <1195663103.26187.1.camel@ld0161-tx32> (raw)
In-Reply-To: <47444864.30509@qstreams.com>

On Wed, 2007-11-21 at 09:01, Ben Warren wrote:

> Absolutely. In fact, I'm working on one right now... Access methods to 
> PHYs are currently common (miiphybb.c and miiphyutil.c) but there's no 
> reason why the TSEC, UCC and other drivers should have hard wiring for 
> individual PHY devices. Any design suggestions you or others have are 
> welcome.


Well, there _is_ the long standing tradition of, er, borrowing
code from Linux...where there just happens to be a PHY lib
already in place, written by somebody named Andy Fleming.
We might consider leveraging that some...?

jdl

  parent reply	other threads:[~2007-11-21 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 12:51 [U-Boot-Users] PHY library? David Saada
2007-11-21 13:29 ` Haavard Skinnemoen
2007-11-21 15:01 ` Ben Warren
2007-11-21 15:08   ` Stefan Roese
2007-11-21 16:38   ` Jon Loeliger [this message]
2007-11-21 16:49     ` Ben Warren
2007-11-21 20:46       ` Andy Fleming

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=1195663103.26187.1.camel@ld0161-tx32 \
    --to=jdl@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.