public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001933] New HAL for the M4 core of Freescale Vybrid targets
Date: Tue, 28 Jan 2014 01:46:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Please do not reply to this email, use the link below.

Ilija Kocho [Илија Кочо] <> changed:

           What    |Removed                     |Added
         Depends on|                            |1001397

--- Comment #4 from Ilija Kocho [Илија Кочо] <> ---
Stefan / Jochen

Thank you for your contribution. It would be nice to have Vybrid in our

I applied your patches to current eCos CVS and got some warnings and conflicts:

   - Wallclock seems to be missing.
   - Some conflicts pointing to I2C and SPI drivers. It seems that your earlier
patch Attachment 2350 from BUG 1001397 fixes I2C conflicts.
  - Is Attachment 2350 up to date or yiu have newer I2C driver version?
  - What about SPI? There should be some patch.
  - What about drivers that show no conflicts: UART, ENET, eDMA, etc? I would
be very happy and proud if they work with Vybrid unmodified but it seeem too
good to be true.

Looking the code:

   - There are a lot of "reg*.h" files in HAL include directory. Devices in
eCos are decoupled from HAL in order to enable usage of device drivers with
different architectures. I know that this philosophy is not perfectly
implemented, but I aim to do best for new packages. It is especially benefit
for Freescale's chips that re-use peripherals on different architectures.

   - Also there are some type-case problems Vybrid_irq_scheme vs
vybrid_irq_scheme that may work under windows but cause errors on case
sensitive Linux

  - I'm glad to see SGML docs, but they seem incomplete and their compilation
raises errors.

The attached diff contains modifications that I did against current CVS. This
removes conflicts but there are still compilation errors.


  -Please prepare new patches that shall work against current CVS. Also provide
patches to device drivers where needed. It would be good to split variant anf
platform patches in separate files.
 - Also for devices - separate patches.
 - Update year in copyright messages (2013 or 2014).
 - Cross-check SGML docs.
 - Remove "reg*.h" headers.
 - I have noticed CDL for Compiler selection. It is unnecessary because user
can specify compiler prefix and flags in "Global Build Options". Please remove


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

  parent reply	other threads:[~2014-01-28  1:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2014-01-27 12:04 ` bugzilla-daemon
2014-01-27 12:05 ` bugzilla-daemon
2014-01-28  1:46 ` bugzilla-daemon [this message]
2014-01-28  1:49 ` bugzilla-daemon
2014-02-03 19:33 ` bugzilla-daemon
2014-02-05  8:59 ` bugzilla-daemon
2016-12-02  7:07 ` 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).