public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Tony Dinh <mibodhi@gmail.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Simon Glass <sjg@chromium.org>,
	Ramon Fried <rfried.dev@gmail.com>,
	Joe Hershberger <joe.hershberger@ni.com>
Cc: Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 0/3] common: Add fdt network helper
Date: Thu, 12 Aug 2021 08:18:59 +0200	[thread overview]
Message-ID: <a925df38-3b9b-e802-4370-8af93cc5f536@denx.de> (raw)
In-Reply-To: <20210806044910.23500-1-mibodhi@gmail.com>

Hi Ramin, Hi Joe,

On 06.08.21 06:49, Tony Dinh wrote:
> 
> At the moment, there is no common fdt helper function specific to decoding network related
> information from FDTs. This new helper functional group fdt_support_net is intended to be used
> by board-specific code within U-Boot for various network related chores.
> 
> In this patch, create the 1st function fdt_get_phy_addr to parse the device tree to find
> the PHY addess of a specific ethernet device.

Ramon & Joe, could you please also take a look at this patchset? And
let us know if this is okay or if you have some comments?

Thanks,
Stefan

> 
> Tony Dinh (3):
>    Add fdt network helper header file
>    Add fdt network helper functions
>    Add fdt network helper to Makefile
> 
>   common/Makefile           |  2 +-
>   common/fdt_support_net.c  | 46 +++++++++++++++++++++++++++++++++++++++
>   include/fdt_support_net.h | 39 +++++++++++++++++++++++++++++++++
>   3 files changed, 86 insertions(+), 1 deletion(-)
>   create mode 100644 common/fdt_support_net.c
>   create mode 100644 include/fdt_support_net.h
> 


Viele Grüße,
Stefan

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr@denx.de

  parent reply	other threads:[~2021-08-12  6:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06  4:49 [PATCH 0/3] common: Add fdt network helper Tony Dinh
2021-08-06  4:49 ` [PATCH 1/3] Add fdt network helper header file Tony Dinh
2021-08-12  6:17   ` Stefan Roese
2021-08-13 22:26   ` Ramon Fried
2021-09-25 15:15   ` Simon Glass
2021-08-06  4:49 ` [PATCH 2/3] Add fdt network helper functions Tony Dinh
2021-08-12  6:15   ` Stefan Roese
2021-08-12  9:12     ` Tony Dinh
2021-08-13 22:27       ` Ramon Fried
2021-08-06  4:49 ` [PATCH 3/3] Add fdt network helper to Makefile Tony Dinh
2021-08-12  6:17   ` Stefan Roese
2021-08-13 22:28   ` Ramon Fried
2021-08-12  6:18 ` Stefan Roese [this message]
2021-08-15  0:17 ` [PATCH v2 1/3] common: Add fdt network helper Tony Dinh
2021-08-15  0:17   ` [PATCH v2 2/3] common: Add fdt network helper header file Tony Dinh
2021-08-15  0:17   ` [PATCH v2 3/3] common: Add fdt network helper functions Tony Dinh
2021-08-15 14:09 ` [PATCH 0/3] common: Add fdt network helper Simon Glass
2021-08-15 21:27   ` Tony Dinh
2021-08-16 23:36     ` Tony Dinh
2021-08-17 16:09     ` Simon Glass
2021-08-27  4:00       ` Tony Dinh
2021-09-01  9:21         ` Tony Dinh
2021-09-02 16:41           ` Simon Glass
2021-09-03  2:24             ` Tony Dinh

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=a925df38-3b9b-e802-4370-8af93cc5f536@denx.de \
    --to=sr@denx.de \
    --cc=joe.hershberger@ni.com \
    --cc=mibodhi@gmail.com \
    --cc=rfried.dev@gmail.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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