public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] net: gpio PHY driver
Date: Wed, 01 Jul 2009 12:02:46 -0700	[thread overview]
Message-ID: <4A4BB2D6.40703@gmail.com> (raw)
In-Reply-To: <4A4BA8C5.3020101@gmail.com>

Hi Darius,

Darius Augulis wrote:
> On 07/01/2009 09:12 PM, Richard Retanubun wrote:
>   
>> Darius Augulis wrote:
>>     
>>> On 07/01/2009 03:37 PM, Jerry Van Baren wrote:
>>>       
>>>> Darius Augulis wrote:
>>>>         
>>>>> Hi,
>>>>>
>>>>> I need to control RGMII PHY connected to GPIO.
>>>>> Seems there isn't such driver in u-boot.
>>>>> I would like to discuss how is better to implement this?
>>>>> I could port mdio_gpio driver from Linux Kernel,
>>>>> but u-boot does not have universal gpio driver.
>>>>> Off course I could make this very board specific, but It may be useful for
>>>>> other boards, interfacing PHY with GPIO's.
>>>>>
>>>>> Any ideas welcome!
>>>>>
>>>>> Darius A.
>>>>>           
>>>> It sounds like you are looking for CONFIG_BITBANGMII.
>>>>         
>>> Probably. Even it has MPC specific things, I guess should be easy to
>>> re-use it in my system.
>>>       
>> Wow, what a coincidence!
>> Just in case you system is MPC83XX based, I just submitted a patch for consideration
>> that adds bitbang SMI to uec_phy.c<stolen from gvb's implementation, of course>
>>     
>
>   
It sure would be nice to see a patch that gets the CPU-specific crap out 
of the miiphybb driver.  This type of problem has been dealt with in 
other places such as I2C and SPI.  Any takers?
> No, my system is not MPC based. I'm working on new board and CPU 
> (Gemini) support in u-boot. My SoC has two GMAC controllers.
> btw, what is the right way to add new Ethernet driver?
> Should I define CONFIG_CMD_NET and CONFIG_NET_MULTI in my board config?
> Or should I define eth_* funtions right in the driver code?
>
>   
I'm looking forward to your submission.

As Richard mentioned, CONFIG_CMD_NET enables networking.

CONFIG_NET_MULTI really means "use the networking code that supports 
multiple interfaces".  It doesn't mean "my board has more than one 
interface".  Going forward, this is mandatory for all Ethernet 
drivers.   Support for the old-style API (eth_* in drivers) is 
deprecated and is scheduled for removal this fall:

http://git.denx.de/?p=u-boot.git;a=blob;f=doc/feature-removal-schedule.txt;h=9bbdc0a83226aa1158ddd73d253e4742c0124159;hb=HEAD

regards,
Ben

  parent reply	other threads:[~2009-07-01 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 12:28 [U-Boot] net: gpio PHY driver Darius Augulis
2009-07-01 12:37 ` Jerry Van Baren
2009-07-01 16:31   ` Darius Augulis
2009-07-01 18:12     ` Richard Retanubun
2009-07-01 18:19       ` Darius Augulis
2009-07-01 18:43         ` Richard Retanubun
2009-07-01 18:54           ` Darius Augulis
2009-07-01 19:02         ` Ben Warren [this message]
2009-07-01 19:07           ` Darius Augulis
2009-07-01 19:18           ` Scott Wood

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=4A4BB2D6.40703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox