All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
	linux-sh@vger.kernel.org, phil.edworthy@renesas.com
Subject: Re: [PATCH 2/2] sh_eth: add R-Car support for real
Date: Mon, 08 Apr 2013 13:34:53 +0000	[thread overview]
Message-ID: <5162C77D.4050802@cogentembedded.com> (raw)
In-Reply-To: <20130408023936.GA1643@verge.net.au>

Hello.

On 08-04-2013 6:39, Simon Horman wrote:

>> Commit d0418bb7123f44b23d69ac349eec7daf9103472f (net: sh_eth: Add eth support
>> for R8A7779 device) was a failed attempt to add support for one of members of
>> the R-Car SoC family.  That's for three reasons: it treated R8A7779 the  same
>> as SH7724 except including quite dirty hack adding ECMR_ELB  bit  to the mask
>> in sh_eth_set_rate() while not removing ECMR_RTM bit (despite it's reserved in
>> R-Car Ether), and it didn't add a new register offset array despite the closest
>> SH_ETH_REG_FAST_SH4 mapping differs by 0x200 to the offsets all the R-Car Ether
>> registers have, and also some of the registers in this old mapping don't exist
>> on R-Car Ether (due to this, SH7724's 'sh_eth_my_cpu_data' structure is not
>> adequeate for R-Car too).  Fix all these shortcomings, restoring the SH7724
>> related section to its pristine state...

>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

> Hi Sergei,

> thanks for this and sorry for not noticing it earlier.
> I will try exercising it on the r8a7790 lager.

> IIRC you previously mentioned that you were doing work on unravelling
> the #define mess in sh_eth. I am wondering if you have made any progress
> in that area.

    Not much -- I was swithced to USB work.

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
	linux-sh@vger.kernel.org, phil.edworthy@renesas.com
Subject: Re: [PATCH 2/2] sh_eth: add R-Car support for real
Date: Mon, 08 Apr 2013 17:34:53 +0400	[thread overview]
Message-ID: <5162C77D.4050802@cogentembedded.com> (raw)
In-Reply-To: <20130408023936.GA1643@verge.net.au>

Hello.

On 08-04-2013 6:39, Simon Horman wrote:

>> Commit d0418bb7123f44b23d69ac349eec7daf9103472f (net: sh_eth: Add eth support
>> for R8A7779 device) was a failed attempt to add support for one of members of
>> the R-Car SoC family.  That's for three reasons: it treated R8A7779 the  same
>> as SH7724 except including quite dirty hack adding ECMR_ELB  bit  to the mask
>> in sh_eth_set_rate() while not removing ECMR_RTM bit (despite it's reserved in
>> R-Car Ether), and it didn't add a new register offset array despite the closest
>> SH_ETH_REG_FAST_SH4 mapping differs by 0x200 to the offsets all the R-Car Ether
>> registers have, and also some of the registers in this old mapping don't exist
>> on R-Car Ether (due to this, SH7724's 'sh_eth_my_cpu_data' structure is not
>> adequeate for R-Car too).  Fix all these shortcomings, restoring the SH7724
>> related section to its pristine state...

>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

> Hi Sergei,

> thanks for this and sorry for not noticing it earlier.
> I will try exercising it on the r8a7790 lager.

> IIRC you previously mentioned that you were doing work on unravelling
> the #define mess in sh_eth. I am wondering if you have made any progress
> in that area.

    Not much -- I was swithced to USB work.

WBR, Sergei

  parent reply	other threads:[~2013-04-08 13:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 20:50 [PATCH 2/2] sh_eth: add R-Car support for real Sergei Shtylyov
2013-03-28 21:51 ` Sergei Shtylyov
2013-03-29 19:31 ` David Miller
2013-03-29 19:31   ` David Miller
2013-04-08  2:39 ` Simon Horman
2013-04-08  2:39   ` Simon Horman
2013-04-08  9:04   ` Simon Horman
2013-04-08  9:04     ` Simon Horman
2013-04-08 13:45     ` Sergei Shtylyov
2013-04-08 13:45       ` Sergei Shtylyov
2013-04-08 14:40       ` phil.edworthy
2013-04-08 14:40         ` phil.edworthy
2013-04-09 13:08         ` Sergei Shtylyov
2013-04-09 13:08           ` Sergei Shtylyov
2013-04-08 13:34   ` Sergei Shtylyov [this message]
2013-04-08 13:34     ` 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=5162C77D.4050802@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nobuhiro.iwamatsu.yj@renesas.com \
    --cc=phil.edworthy@renesas.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.