From: Werner Almesberger <werner@almesberger.net>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Stefan Schmidt <stefan@osg.samsung.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: Wed, 10 Jun 2015 18:23:51 -0300 [thread overview]
Message-ID: <20150610212351.GS5054@ws> (raw)
In-Reply-To: <20150610152925.GD6647@omega>
Alexander Aring wrote:
> I think the endpoint 0 is different between bootloader (dfu) and the
> application (atusb). Maybe then add this functionality for the
> bootloader only.
If you add it to the boot loader, then you need to flash your
enhanced boot loader via in-circuit programming (or find a way
to bypass the write protection. NB: no such way should exist.)
Not everyone may find that convenient ;)
I'd leave the boot loader as it is and just add a new operation
to the application part of the firmware.
- Werner
next prev parent reply other threads:[~2015-06-10 21:24 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 [this message]
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
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=20150610212351.GS5054@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox