All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PHY lib
Date: Tue, 08 Jul 2008 11:53:17 -0700	[thread overview]
Message-ID: <4873B79D.5080603@gmail.com> (raw)
In-Reply-To: <487303E5.7030202@seznam.cz>

Hi Michal,

Michal Simek wrote:
> Hi Ben,
>
>   
>> Hi Michal,
>>
>> Michal Simek wrote:
>>     
>>> Hi Ben and others,
>>>
>>> do you have any plan to start with PHY libs?
>>> I saw to tsec driver - there are some phy description.
>>> I would like to use phy description for one eth driver which I do.
>>>
>>>   
>>>       
>> I'm finally finding time to work on refactoring U-boot's networking
>> support, one of the parts of which is a proper PHY library.  For several
>> reasons, it pulls a lot from the TSEC driver.  Cutting and pasting the
>> PHY descriptions from TSEC is probably a good idea (in as much as
>> cutting and pasting is a good idea :)).
>>     
>
> That's great. What next changes do you plan?
> Thanks for information.
>
>   
So many things...  Here are what I see as the low-hanging fruit:

1. Move all ethernet initializations into 
cpu_eth_init()/board_eth_init().  You can see this is underway.
2. Get rid of the CONFIG_NET_MULTI option.  The trick here is to keep 
the code size of single-controller boards as small as possible.
3. PHY library.

With these implemented, I think we can start to look at more interesting 
problems.  Feel free to brainstorm here!

regards,
Ben

      reply	other threads:[~2008-07-08 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 14:27 [U-Boot-Users] PHY lib Michal Simek
2008-07-07 22:03 ` Ben Warren
2008-07-08  6:06   ` Michal Simek
2008-07-08 18:53     ` Ben Warren [this message]

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=4873B79D.5080603@gmail.com \
    --to=biggerbadderben@gmail.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.