public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Larry Johnson <lrj@arlinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 2/2 (resubmit)] NET: Add Ethernet 1000BASE-X support for PPC4xx
Date: Wed, 14 Nov 2007 11:59:02 -0500	[thread overview]
Message-ID: <473B2956.6050607@arlinx.com> (raw)
In-Reply-To: <4729E1A0.3010200@qstreams.com>

Ben Warren wrote:
> Larry Johnson wrote:
>> Hi Ben,
>>
>> Thank you for your comments.  See below...
>>
>> Ben Warren wrote:
>>  
>>> Larry,
>>>
>>> I think this can be simplified a bit. More later on...
>>>
>>> Larry Johnson wrote:
>>>    
>>>> This patch adds a new switch: "CONFIG_PHY_DYNAMIC_ANEG".  When this symbol
>>>> is defined, the PHY will advertise it's capabilities for autonegotiation
>>>> based on the capabilities shown in the PHY's status registers, including
>>>> 1000BASE-X.  When "CONFIG_PHY_DYNAMIC_ANEG" is not defined, the PHY will
>>>> advertise hard-coded capabilities, as before.
>>>>
>>>> Signed-off-by: Larry Johnson <lrj@acm.org>
>>>> ---
>>>>
>>>>  common/miiphyutil.c |  155
>>>> +++++++++++++++++++++++++++++++++------------------
>>>>  include/miiphy.h    |   21 +++++++
>>>>  2 files changed, 121 insertions(+), 55 deletions(-)
>>>>
>>>> diff --git a/common/miiphyutil.c b/common/miiphyutil.c
>>>> index 58ebc5e..b2f62d0 100644
>>>> --- a/common/miiphyutil.c
>>>> +++ b/common/miiphyutil.c
>>>> @@ -344,101 +344,146 @@ int miiphy_reset (char *devname, unsigned char
>>>> addr)
>>>>
>>>>  /*****************************************************************************
>>>>
>>>>
>>>>   *
>>>> - * Determine the ethernet speed (10/100).
>>>> + * Determine the ethernet speed (10/100/1000).  Return 10 on error.
>>>>   */
>>>>  int miiphy_speed (char *devname, unsigned char addr)
>>>>  {
>>>> -    unsigned short reg;
>>>> +    u16 bmcr;
>>>>
>>>>  #if defined(CONFIG_PHY_GIGE)
>>>> -    if (miiphy_read (devname, addr, PHY_1000BTSR, &reg)) {
>>>> -        printf ("PHY 1000BT Status read failed\n");
>>>> -    } else {
>>>> -        if (reg != 0xFFFF) {
>>>> -            if ((reg & (PHY_1000BTSR_1000FD | PHY_1000BTSR_1000HD))
>>>> -                != 0) {
>>>> -                return (_1000BASET);
>>>> -            }
>>>> +    u16 btsr;
>>>> +
>>>> +#if defined(CONFIG_PHY_DYNAMIC_ANEG)
>>>>         
>>> I don't think you need this CONFIG. It doesn't really do anything.
>>>     
>>
>> I only put it in to keep the footprint smaller for boards that aren't
>> using fiber, so I'll get rid if it.
>>
>>   
> Yeah, and I like that train of thought, but I think clarity wins out
> here, and I doubt there are that many GigE boards that can't handle a
> few extra bytes (Don't tell Wolfgang I said that)
> 
[snip]

Hi Ben and Stefan,

Thank you for incorporating my patch, Ben.

I have merged my changes into the PPC4xx "for-1.3.1" branch.  When I do
the MAKEALL there, the build for Ocotea board fails because the binary
is now 0xAC byte too large.  What are your opinions on the best way to
handle this?

Best regards,
Larry

  parent reply	other threads:[~2007-11-14 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 16:21 [U-Boot-Users] [PATCH 2/2 (resubmit)] NET: Add Ethernet 1000BASE-X support for PPC4xx Larry Johnson
2007-10-31 17:45 ` Ben Warren
2007-10-31 20:31   ` Larry Johnson
     [not found]     ` <4729E1A0.3010200@qstreams.com>
2007-11-14 16:59       ` Larry Johnson [this message]
2007-11-14 20:04         ` Stefan Roese
2007-11-14 21:37           ` Larry Johnson
2007-11-15  6:05             ` Stefan Roese
2007-11-19 20:00               ` [U-Boot-Users] " Larry Johnson
2007-11-19 20:19                 ` Larry Johnson
2007-11-14 20:21         ` [U-Boot-Users] [PATCH 2/2 (resubmit)] " Ben Warren
  -- strict thread matches above, loose matches on Subject: below --
2007-11-01 13:46 Larry Johnson

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=473B2956.6050607@arlinx.com \
    --to=lrj@arlinx.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