From: Alexander Aring <alex.aring@gmail.com>
To: Werner Almesberger <werner@almesberger.net>
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: Thu, 11 Jun 2015 10:17:49 +0200 [thread overview]
Message-ID: <20150611081745.GB972@omega> (raw)
In-Reply-To: <20150610212351.GS5054@ws>
On Wed, Jun 10, 2015 at 06:23:51PM -0300, Werner Almesberger wrote:
> 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.
>
yea, this was just an idea because Marcel said:
"... you might want to push that device into a special mode to allow
programming of these settings"
and that's for me the dfu mode. My idea was just make the "new
operation" accessable in dfu endpoint only.
Nevertheless I am also fine with normal application operation, or making
some special bus access cycles to get into "privileged mode" or
something else, everything is possible.
- Alex
next prev parent reply other threads:[~2015-06-11 8:17 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 [this message]
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=20150611081745.GB972@omega \
--to=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 \
--cc=werner@almesberger.net \
/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