public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Possible PHYLIB issue
Date: Sat, 9 Jun 2012 17:02:28 +0200	[thread overview]
Message-ID: <201206091702.29047.marex@denx.de> (raw)

Hi Joe,

I'm sending you this snipped of network-related problem (maybe). It's from u-
boot IRC.

23:32 < demigod2k> you said a few hours ago to look at PHYLIB
23:32 < demigod2k> it defers the config properly
23:32 < demigod2k> however in drivers/net/phy/marvell.c for example, the values 
in _config don't belong in that file. they're not universal config. they're 
different for every 
                   board depending how you've hooked up the i/o or strapped the 
chip
23:33 < demigod2k> so somebody using CONFIG_PHY_MARVELL needs to modify and edit 
drivers/net/phy/marvell.c with values appropriate to their board
23:33 < demigod2k> no big deal I just did it in my local copy
23:49 < demigod2k> and a related problem -- with new ethernet separation, a 
register step and a deferred initialization step in eth_init() the variables 
ethprime and ethact don't 
                   work quite right
23:50 < demigod2k> README.drivers.eth doesn't say if you need to check link 
status in eth_init and rather few of the drivers do it.... but if you don't 
return an error for "link 
                   down" in eth_init the round robin behavior doesn't work and 
uboot won't cycle through eth0, eth1, eth2, etc.. checking for a link
23:50 < demigod2k> I'm out. Hopefully somebody sees that later!

                 reply	other threads:[~2012-06-09 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201206091702.29047.marex@denx.de \
    --to=marex@denx.de \
    --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