From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-sh@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RFT v2] net: sh_eth: add support for SH7786
Date: Tue, 8 Jan 2019 10:16:15 +0100 [thread overview]
Message-ID: <20190108101615.165c5a4b@windsurf> (raw)
In-Reply-To: <cbc7976d-2376-15d4-0fc1-febdf142887b@cogentembedded.com>
Hello Sergei,
Thanks for your work on this topic!
On Fri, 4 Jan 2019 15:53:24 +0300, Sergei Shtylyov wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> This commit adds the sh_eth_cpu_data structure that describes the
> SH7786 variant of the IP.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I tried to test this patch today, and it doesn't work for the moment.
However, I've rebased my whole SH7786 patch stack on top of 4.20, and
with my original sh_eth patch, network is also not working, so I can't
say whether it's really this patch that has an issue, or some other
aspects.
(And yes, I remember to adjust the base address of the sh_eth
platform_device:
diff --git a/arch/sh/boards/board-wdc-cont4.c b/arch/sh/boards/board-wdc-cont4.c
index c72209822899..7ca1bfcc20ae 100644
--- a/arch/sh/boards/board-wdc-cont4.c
+++ b/arch/sh/boards/board-wdc-cont4.c
@@ -80,7 +80,7 @@ static int wdc_cont4_clk_init(void)
static struct resource sh_eth_resources[] = {
{
- .start = 0xFEE00200,
+ .start = 0xFEE00000,
.end = 0xFEE00400 - 1,
.flags = IORESOURCE_MEM,
}, {
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-sh@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RFT v2] net: sh_eth: add support for SH7786
Date: Tue, 08 Jan 2019 09:16:15 +0000 [thread overview]
Message-ID: <20190108101615.165c5a4b@windsurf> (raw)
In-Reply-To: <cbc7976d-2376-15d4-0fc1-febdf142887b@cogentembedded.com>
Hello Sergei,
Thanks for your work on this topic!
On Fri, 4 Jan 2019 15:53:24 +0300, Sergei Shtylyov wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> This commit adds the sh_eth_cpu_data structure that describes the
> SH7786 variant of the IP.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I tried to test this patch today, and it doesn't work for the moment.
However, I've rebased my whole SH7786 patch stack on top of 4.20, and
with my original sh_eth patch, network is also not working, so I can't
say whether it's really this patch that has an issue, or some other
aspects.
(And yes, I remember to adjust the base address of the sh_eth
platform_device:
diff --git a/arch/sh/boards/board-wdc-cont4.c b/arch/sh/boards/board-wdc-cont4.c
index c72209822899..7ca1bfcc20ae 100644
--- a/arch/sh/boards/board-wdc-cont4.c
+++ b/arch/sh/boards/board-wdc-cont4.c
@@ -80,7 +80,7 @@ static int wdc_cont4_clk_init(void)
static struct resource sh_eth_resources[] = {
{
- .start = 0xFEE00200,
+ .start = 0xFEE00000,
.end = 0xFEE00400 - 1,
.flags = IORESOURCE_MEM,
}, {
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-08 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 12:53 [PATCH RFT v2] net: sh_eth: add support for SH7786 Sergei Shtylyov
2019-01-04 12:53 ` Sergei Shtylyov
2019-01-04 13:01 ` Sergei Shtylyov
2019-01-04 13:01 ` Sergei Shtylyov
2019-01-08 9:16 ` Thomas Petazzoni [this message]
2019-01-08 9:16 ` Thomas Petazzoni
2019-01-10 9:10 ` Sergei Shtylyov
2019-01-10 9:10 ` Sergei Shtylyov
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=20190108101615.165c5a4b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=thomas.petazzoni@free-electrons.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 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.