From: Michael Jones <mjones@linear.com>
To: ecos-maintainers@ecos.sourceware.org
Cc: "john@dallaway.org.uk Dallaway" <john@dallaway.org.uk>
Subject: Copyright and maintainability question for new ARM Cortex A9 HAL
Date: Thu, 05 Sep 2013 03:52:00 -0000 [thread overview]
Message-ID: <77A01081-8A89-4D60-B7B1-78D774946EC6@linear.com> (raw)
Hi,
John Dallaway suggested I post a question I asked him to this list for comment, so here it goes...
I wanted to talk about copyright assignment issues with my Freescale iMX6X work early in the process.
The status is:
- Project not registered yet
- Uses Freescale SDK macros
- Uses Freescale SDK code for MMU, GIC, etc
- UART working
- Runs on a single core of an iMX6Q Sabre SD board
- Debuggable with JLink
- Runs a ported SDK primes app as a two thread eCos program
Before I register, I want to have a strategy in place to deal with Freescale code. Do I replace all the Freescale code line by line until nothing is left, or see if Freescale will assign copyright? I need advice on options before I spend a bunch of time rewriting the Freescale code I am using.
I have to make a trip to Freescale in Austin TX Sept 24th, so I have an opportunity to discuss with them if you know the appropriate people to discuss with.
Things on my road map not related to copyright:
- Getting SMP running
- Multicore debugging with JLink
- Getting Mentor Probe Working with a true multicore debugger (not separate GDB sessions in Eclipse)
- Building bin files for SD or flash
- Peripherals like Ethernet
- Registering the project
- Building a releasable toolchain (works for me, but nothing like works for everyone)
next reply other threads:[~2013-09-05 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 3:52 Michael Jones [this message]
2013-09-07 3:04 ` Jonathan Larmour
2013-09-07 13:40 ` Michael Jones
2013-12-04 12:08 ` "Ilija Kocho [Илија Кочо]"
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=77A01081-8A89-4D60-B7B1-78D774946EC6@linear.com \
--to=mjones@linear.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).