devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Bastian Hecht <hechtb+renesas@gmail.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM: shmobile: r8a7740 dtsi: Add Ethernet support
Date: Sun, 11 May 2014 17:48:38 +0400	[thread overview]
Message-ID: <536F7FB6.5090508@cogentembedded.com> (raw)
In-Reply-To: <20140511010043.GZ31760@verge.net.au>

Hello.

On 05/11/2014 05:00 AM, Simon Horman wrote:

>>>>>      Mine was the same (but for BOCK-W board) but DT people didn't give a
>>>>> damn. :-) So there's still no Ethernet support in BOCK-W DT.

>>>> Yes there is: ethernet@18300000.

>>>     That's for an on-board SMSC911x, not for sh_eth.

>> Oh, it has two Ethernet ports? Didn't know that.

> IIRC only the SMSC911x is exposed on the Bock-W board.

    Not really. You're probably mixing it with Marzen.

> From my point of view I would be happy to accept support for
> the other port if there was some way (for someone to) verify it.

    There is, and you have accepted such support in the legacy board file.
I had to postpone Ether DT support to the time when CCF support is available, 
though I have posted corresponding patches without the "clocks" property already.

WBR, Sergei


  reply	other threads:[~2014-05-11 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 20:32 [PATCH 1/3] ARM: shmobile: r8a7740: Correct name of DT Ethernet clock Geert Uytterhoeven
     [not found] ` <1399494750-31996-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2014-05-07 20:32   ` [PATCH 2/3] ARM: shmobile: r8a7740 dtsi: Add Ethernet support Geert Uytterhoeven
2014-05-08 13:00     ` Sergei Shtylyov
     [not found]       ` <536B7FD3.5090506-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-05-08 13:06         ` Geert Uytterhoeven
2014-05-08 13:14           ` Sergei Shtylyov
2014-05-08 13:21             ` Geert Uytterhoeven
2014-05-08 17:52               ` Sergei Shtylyov
2014-05-08 18:46                 ` Geert Uytterhoeven
2014-05-08 18:52                   ` Sergei Shtylyov
2014-05-08 19:01                     ` Geert Uytterhoeven
2014-05-11  1:00                       ` Simon Horman
2014-05-11 13:48                         ` Sergei Shtylyov [this message]
     [not found]                           ` <536F7FB6.5090508-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-05-11 22:49                             ` Simon Horman
2014-05-11  2:25                     ` Simon Horman
2014-05-07 20:32 ` [PATCH 3/3] ARM: shmobile: armadillo-reference dts: " Geert Uytterhoeven

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=536F7FB6.5090508@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=hechtb+renesas@gmail.com \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).