netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Mugunthan V N <mugunthanvnm@ti.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	linux-omap@vger.kernel.org
Subject: Re: [net-next PATCH 1/1] drivers: net: cpsw: Add support for new CPSW IP version
Date: Wed, 31 Jul 2013 22:20:07 +0200	[thread overview]
Message-ID: <20130731202006.GE8027@netboy> (raw)
In-Reply-To: <20130731200756.GA3737@radagast>

On Wed, Jul 31, 2013 at 11:07:56PM +0300, Felipe Balbi wrote:
> 
> what I'm saying is that we can give new IP revision a chance to work if
> they have no programming model differences (except for, perhaps, new
> features and different erratas).

But it also has a chance to fail when there are differences.
Comparing CPSW V1 with V2, it appears that TI likes to move the
registers around between versions. To me, this is reason enough to
make the driver defensive.

Thanks,
Richard

  reply	other threads:[~2013-07-31 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 12:12 [net-next PATCH 1/1] drivers: net: cpsw: Add support for new CPSW IP version Mugunthan V N
2013-07-31 14:49 ` Richard Cochran
2013-07-31 15:28   ` Felipe Balbi
2013-07-31 16:38     ` Richard Cochran
2013-07-31 18:45       ` Felipe Balbi
2013-07-31 19:22         ` Richard Cochran
2013-07-31 19:43           ` Felipe Balbi
2013-07-31 19:45             ` Felipe Balbi
2013-07-31 20:04               ` Richard Cochran
2013-07-31 20:07                 ` Felipe Balbi
2013-07-31 20:20                   ` Richard Cochran [this message]
2013-07-31 20:26                     ` Felipe Balbi
2013-07-31 20:34                       ` Richard Cochran
2013-07-31 21:11                         ` Felipe Balbi
2013-08-01  4:43                           ` Richard Cochran
2013-08-01  4:46             ` Richard Cochran
2013-07-31 23:55 ` David Miller

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=20130731202006.GE8027@netboy \
    --to=richardcochran@gmail.com \
    --cc=balbi@ti.com \
    --cc=davem@davemloft.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    /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).