From: Werner Almesberger <werner@almesberger.net>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Alexander Aring <alex.aring@gmail.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
Subject: Re: Strategy for permament extended/EUI64 address writing and updating in atusb
Date: Thu, 11 Jun 2015 13:14:09 -0300 [thread overview]
Message-ID: <20150611161409.GU5054@ws> (raw)
In-Reply-To: <55798F76.8020708@osg.samsung.com>
Stefan Schmidt wrote:
> o It read the EUI64 from EEPROM during probe and is no further
> touching it at all
That's then functionally equivalent to the "copying to RAM"
I proposed.
> o Furthermore, after the EEPROM write a mcu_reset() done to
> re-enumerate on the USB bus
I'm just saying that we already have a generic mechanism for
getting the device to re-enumerate.
> Not compelling at all if you ask me. We have an EEPROM
> available to store such device properties so we better use it.
While I disagree with any reasoning that one should use the
EEPROM because it's there, I also think that attaching the
address to the firmware binary would add too many operational
complications.
- Werner
prev parent reply other threads:[~2015-06-11 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 12:28 Strategy for permament extended/EUI64 address writing and updating in atusb Stefan Schmidt
2015-06-10 14:49 ` Marcel Holtmann
2015-06-10 15:29 ` Alexander Aring
2015-06-10 15:38 ` Marcel Holtmann
2015-06-10 16:09 ` Alexander Aring
2015-06-10 21:23 ` Werner Almesberger
2015-06-11 8:17 ` Alexander Aring
2015-06-11 8:23 ` Marcel Holtmann
2015-06-11 9:39 ` Stefan Schmidt
2015-06-11 12:48 ` Werner Almesberger
2015-06-11 13:39 ` Stefan Schmidt
2015-06-11 16:14 ` Werner Almesberger [this message]
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=20150611161409.GU5054@ws \
--to=werner@almesberger.net \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=phoebe.buckheister@itwm.fraunhofer.de \
--cc=stefan@osg.samsung.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.