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] [PATCH 2/2] net: phy: Add ability to program the ksz9031 skew values from the uboot env
Date: Sun, 15 Feb 2015 15:43:30 +0100	[thread overview]
Message-ID: <201502151543.30642.marex@denx.de> (raw)
In-Reply-To: <54DE29DB.1010404@denx.de>

On Friday, February 13, 2015 at 05:44:11 PM, Stefan Roese wrote:
> Hi Vince,
> 
> On 13.02.2015 17:19, Vince Bridgers wrote:
> > ....
> > 
> >> No. But with your comments above (which make total sense), I tend to NAK
> >> this ability to configure the PHY skew timings via environment
> >> variables.
> > 
> > Understood, I'll focus on the devicetree implementation and a README to
> > 
>  > help non-expert users use the MII command for board bringup & debug
>  > purposes.
> 
> This README is a good idea and will be helpful. Thanks for doing this.

Hi!

Thank you for doing this indeed :)

Best regards,
Marek Vasut

  reply	other threads:[~2015-02-15 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 14:44 [U-Boot] [PATCH 0/2] Add getenv_long and Micrel ksz9031 skew settings Vince Bridgers
2015-02-09 14:44 ` [U-Boot] [PATCH 1/2] cmd: Add getenv_long to support reading signed integers from the uboot env Vince Bridgers
2015-02-09 19:12   ` Marek Vasut
2015-02-09 14:44 ` [U-Boot] [PATCH 2/2] net: phy: Add ability to program the ksz9031 skew values " Vince Bridgers
2015-02-09 19:18   ` Marek Vasut
2015-02-09 21:31     ` Vince Bridgers
2015-02-10 18:51       ` Marek Vasut
2015-02-11  7:08         ` Stefan Roese
2015-02-11  8:07           ` Joe Hershberger
2015-02-11  8:26             ` Stefan Roese
2015-02-13 16:19               ` Vince Bridgers
2015-02-13 16:44                 ` Stefan Roese
2015-02-15 14:43                   ` Marek Vasut [this message]
2015-02-13 16:17             ` Vince Bridgers
2015-02-13 16:05           ` Vince Bridgers
2015-02-13 15:57         ` Vince Bridgers

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=201502151543.30642.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