All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx28evk: Convert to phylib framework
Date: Fri, 12 Jul 2013 01:48:57 -0300	[thread overview]
Message-ID: <CAOMZO5BiFfjNG043r49-6qP0c+YxGyM_wxBBk16wiocmwyiouw@mail.gmail.com> (raw)
In-Reply-To: <201307120640.02896.marex@denx.de>

On Fri, Jul 12, 2013 at 1:40 AM, Marek Vasut <marex@denx.de> wrote:
> Dear Fabio Estevam,
>
>> From: Fabio Estevam <fabio.estevam@freescale.com>
>>
>> mx28evk has a LAN8270 ethernet phy and we can use the phylib framework.
>>
>> One of the advantages of converting to phylib is that we no longer see a
>> timeout prior to the first transfer in the 'tftp' command.
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>> After applying this patch I get:
>>
>> U-Boot 2013.04-11810-gd6d75ec-dirty (Jul 12 2013 - 01:15:03)
>>
>> CPU:   Freescale i.MX28 rev1.2 at 454 MHz
>> BOOT:  SSP SD/MMC #0, 3V3
>> DRAM:  128 MiB
>> MMC:   MXS MMC: 0
>> Video: MXSFB: 'videomode' variable not set!
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Net:   Phy not found
>>
>> I still get this 'Phy not found' message, but I think this is not related
>> to the board code.
>
> This is because PHYlib doesn't know your PHY. You might need to add a definition
> for it into drivers/net/phy/smsc.c

mx28evk uses a LAN8270.

drivers/net/phy/smsc.c has an entry for "SMSC LAN8710/LAN8720", so not
sure why it fails to recognize it.
I haven't debugged it yet.

Which phy does sc_sps_1.h use? Is it also a 8720? Is the phy recognized on boot?

Regards,

Fabio Estevam

  reply	other threads:[~2013-07-12  4:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  4:28 [U-Boot] [PATCH] mx28evk: Convert to phylib framework Fabio Estevam
2013-07-12  4:40 ` Marek Vasut
2013-07-12  4:48   ` Fabio Estevam [this message]
2013-07-12  4:58     ` Marek Vasut
2013-07-12  5:00       ` Alexandre Pereira da Silva
2013-07-12 11:48         ` Marek Vasut

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=CAOMZO5BiFfjNG043r49-6qP0c+YxGyM_wxBBk16wiocmwyiouw@mail.gmail.com \
    --to=festevam@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.