public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001716] MIPS malta + sead3 update
Date: Thu, 13 Dec 2012 16:06:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Please do not reply to this email. Use the web interface provided at:

Jonathan Larmour <> changed:

           What    |Removed                     |Added
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |
     Ever Confirmed|0                           |1

--- Comment #1 from Jonathan Larmour <> 2012-12-13 16:06:22 GMT ---
Thanks for contributing back! The first thing that will be needed to allow this
to be checked in to the repository is a copyright assignment from MIPS to the
FSF. Please read and fill in the form
linked from the there and submit it to the FSF.

In terms of the patch itself, a few things that stand out that would want
addressing, some are vital licensing issues, some are to match existing eCos
coding standard practice:

- You need ChangeLog entries for all changes

- New files should have the standard form of file banners at the start we use,
and in preparation for the assignment being completed should be marked as
Copyright the Free Software Foundation. Obviously, refer to any other files for
examples. The .ecm files, essentially being generated, can have their copyright
line removed.

- I suspect you would not want to assign copyright of msc01_pci.h to the FSF as
it comes from elsewhere. In which case it should still have a standard eCos
license/information banner at the beginning, but MIPS will also have to provide
a license which this file may be used under, which must be compatible with the
GPL. My suggestion would be either the GNU All-permissive license:

or the modified BSD license:

- CYGPKG_MALTA_QEMU and CYGPKG_SEAD3 need descriptions.

- CYGPKG_IO_MALTA_SERIAL should be an option not a component.

- Naming of globals and functions should either have a cyg_ or hal_ prefix. For
example the functions uart_*, malta_*, arch_pci_config_access(), 

- Can you explain the change in memory address of mlt_mips_malta_ram.ldi ? If
nothing else, this will cause compatibility problems with existing ROM
monitors. Does it reflect a hardware change? If so, we would need existing
hardware to continue working.

- The use of uart2_channel looks a lot like a bodge. There are two serial
devices after all. I think this wants improvement. If you aren't able to do it
(short of time), it should be submitted into bugzilla as a bug report so the
issue is tracked and not forgotten.

- uart_debug and uart2_printf should be removed - standard HAL APIs should be
used instead.

- Is there really a need for the extra .ld files? Can't you just use ifdefs in
the normal mips_mips32.ld file?

That will do for a first pass of comments I think. We'll wait for the
assignment to come through before anything else.


Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  reply	other threads:[~2012-12-13 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13  8:06 [Bug 1001716] New: " bugzilla-daemon
2012-12-13 16:06 ` bugzilla-daemon [this message]
2012-12-13 16:14 ` [Bug 1001716] " bugzilla-daemon
2012-12-13 16:14 ` bugzilla-daemon
2012-12-13 17:15 ` bugzilla-daemon
2012-12-25  7:44 ` bugzilla-daemon
2013-06-03 13:43 ` bugzilla-daemon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).