netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Bryan.Whitehead@microchip.com
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v1 net-next] lan743x: Provide Read/Write Access to on chip OTP
Date: Mon, 21 Jan 2019 23:33:45 +0100	[thread overview]
Message-ID: <20190121223345.GA23208@lunn.ch> (raw)
In-Reply-To: <CY4PR1101MB23425FFEA3EED03BC74AF501FA9F0@CY4PR1101MB2342.namprd11.prod.outlook.com>

> > This is breaking backwards compatibility. I think you need to respect the
> > magic value, independent of how adapter->flags.
> 
> Is backwards compatibility a requirement?

Hi Bryan

You should not change the ABI. And this is an ABI. So yes, backwards
compatibility should be maintained. Maybe there is a manufacturer out
there that has a script in their factory programming MAC addresses
into their devices using the current API. This change is going to
break their system. You really should be trying to avoid that.
 
> If so, this only breaks OTP backward compatibility, which was
> extremely restrictive and ultimately not very useful.

Was it sufficiently useful to actually program something into the OTP
to make the hardware work? If yes, somebody is probably using it. Or
is there some other way you expect a manufacturer to be programming
the OTP? Do you tell them the current API is horribly broken, don't
use it, always use JTAG?

You also need to think about the new ABI you are putting into
place. Is it really what you want? You cannot change it
afterwards. You need to support this forever.

	    Andrew

  reply	other threads:[~2019-01-21 22:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 21:54 [PATCH v1 net-next] lan743x: Provide Read/Write Access to on chip OTP Bryan Whitehead
2019-01-20 19:32 ` Andrew Lunn
2019-01-21 18:06   ` Bryan.Whitehead
2019-01-21 18:16     ` Andrew Lunn
2019-01-21 20:30       ` Bryan.Whitehead
2019-01-21 18:26 ` Andrew Lunn
2019-01-21 21:12   ` Bryan.Whitehead
2019-01-21 22:33     ` Andrew Lunn [this message]
2019-01-22 19:21       ` Bryan.Whitehead

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=20190121223345.GA23208@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Bryan.Whitehead@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --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).