public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001187] New port - HAL: Freescale Kinetis variant, TWR-K60N512, TWR-K40X256 plf; Devs: Freescale UART and ENET (Ethernet)
Date: Mon, 17 Oct 2011 21:30:00 -0000	[thread overview]
Message-ID: <20111017213035.DDF192F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001187-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001187

--- Comment #22 from Ilija Kocho <ilijak@siva.com.mk> 2011-10-17 22:30:28 BST ---
(In reply to comment #20)
> As per direct mail, here's a few comments, although I haven't done what I'd
> call a full review:
> 
> 
> - I'll just mention that if extra TTYs are justified, then you should just
> modify CYGPKG_IO_SERIAL.


This has some history. The idea was a provision for adding (as much as needed)
additional tty/termios drivers into target without the need for changing IO.
Luckily after a long session with Sergei the patch was surprisingly short.
Please see: http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00023.html
Also:      Bug #1001180


> 
> - "familly" should be spelt "family", and "acces" -> "access"

Thank you. Luckily there isn't wellcome (pardon welcome) or luckilly :) in my
text.

> 
> - CDL display names shouldn't really end in full-stops ("."). The best way to
> decide what to use for display names is to think of what would be best in the
> graphical configuration tool - even if you, like many maintainers, don't use
> it, lots of eCos users do.

I'm trying to make the displays as appropriate as I can, but sometimes they
resemble sentences - hence full-stops. I'll clean them.

> 
> - Various components which are "flavor none" should also have "no_define".

I don't know why, but I had impression that flavor none are no_define by
default... but now I know they aren't.

> 
> - The CYGPKG_HAL_CORTEXM_KINETIS .cdl file is quite big - perhaps the
> components related to clocking could be split off into a separate file, and
> included. 


Yeah. This clock is more complex than some 8-bit micro-controllers. Good idea.
This brings me an idea of extracting clocking code from kinetis_misc.c?

kinetis_clocking.cdl
kinetis_clocking.c

Any comment?


> 
> - This bit in hal_diag.c:
> +#if defined(CYGOPT_HAL_KINETIS_DIAG_IN_MISC_FLASH_SECTION) && \
> +        CYGOPT_HAL_KINETIS_DIAG_IN_MISC_FLASH_SECTION
> +#  define CYGOPT_HAL_KINETIS_DIAG_FLASH_SECTION_ATTR         \
> +        CYGOPT_HAL_KINETIS_MISC_FLASH_SECTION_ATTR
> +#else
> +#  define CYGOPT_HAL_KINETIS_DIAG_FLASH_SECTION_ATTR
> +#endif
> 
> I think you originally meant to begin that with:
> +#if defined(CYGOPT_HAL_KINETIS_DIAG_IN_MISC_FLASH_SECTION) && \
> +        CYGOPT_HAL_KINETIS_MISC_FLASH_SECTION_ATTR
> 


It probably used to be flavor data or booldata defining section name. Than I
decided to simplify it (literal section name), but preprocessor code remained.
I'll look for eventual other cases.


> But given the CDL you can probably just use:
> #ifdef CYGOPT_HAL_KINETIS_DIAG_IN_MISC_FLASH_SECTION
> 
> 
> Nothing else leapt out at me. It seems a very good quality patch from what I
> can tell.
> 

Thank you for good advices.
Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2011-10-17 21:30 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  9:02 [Bug 1001187] New: New port: Freescale Kinetis variant, Freescale TWR-K60N512, Freescale UART device driver bugzilla-daemon
2011-04-03  9:03 ` [Bug 1001187] " bugzilla-daemon
2011-04-03  9:06 ` bugzilla-daemon
2011-04-03  9:09 ` bugzilla-daemon
2011-04-05 16:48 ` bugzilla-daemon
2011-04-06 16:59 ` bugzilla-daemon
2011-04-14 10:48 ` bugzilla-daemon
2011-04-19 21:08 ` bugzilla-daemon
2011-04-19 21:25 ` bugzilla-daemon
2011-04-27  7:21 ` bugzilla-daemon
2011-05-18 11:04 ` bugzilla-daemon
2011-05-19 10:30 ` bugzilla-daemon
2011-06-04  9:57 ` bugzilla-daemon
2011-06-04  9:58 ` bugzilla-daemon
2011-06-04 10:01 ` bugzilla-daemon
2011-06-04 10:05 ` bugzilla-daemon
2011-08-28 14:15 ` bugzilla-daemon
2011-08-28 14:21 ` bugzilla-daemon
2011-08-28 14:22 ` bugzilla-daemon
2011-08-28 14:25 ` bugzilla-daemon
2011-08-28 14:26 ` bugzilla-daemon
2011-08-28 14:32 ` bugzilla-daemon
2011-08-28 14:35 ` bugzilla-daemon
2011-08-28 14:37 ` bugzilla-daemon
2011-08-29 19:39 ` [Bug 1001187] New port - HAL: Freescale Kinetis variant, TWR-K60N512, TWR-K40X256 plf; Devs: Freescale UART and ENET (Ethernet) bugzilla-daemon
2011-09-27 18:38 ` bugzilla-daemon
2011-09-27 18:39 ` bugzilla-daemon
2011-10-17 20:32 ` bugzilla-daemon
2011-10-17 21:30 ` bugzilla-daemon [this message]
2011-10-17 22:25 ` bugzilla-daemon
2011-10-17 23:28 ` bugzilla-daemon
2011-10-18  6:04 ` bugzilla-daemon
2011-10-23 22:30 ` bugzilla-daemon
2011-10-23 22:31 ` bugzilla-daemon
2011-10-23 22:32 ` bugzilla-daemon
2011-10-23 22:33 ` bugzilla-daemon
2011-10-23 22:34 ` bugzilla-daemon
2011-10-23 22:35 ` bugzilla-daemon
2011-10-23 22:38 ` bugzilla-daemon
2011-10-23 22:41 ` bugzilla-daemon
2011-10-25 11:05 ` bugzilla-daemon
2011-10-27  7:20 ` bugzilla-daemon
2011-10-27  7:21 ` bugzilla-daemon
2011-10-27  7:22 ` bugzilla-daemon
2011-10-27  7:23 ` bugzilla-daemon
2011-10-27  7:25 ` bugzilla-daemon
2011-10-27  7:26 ` bugzilla-daemon
2011-10-27 17:22 ` bugzilla-daemon
2011-10-27 20:38 ` bugzilla-daemon
2011-10-27 22:04 ` bugzilla-daemon
2011-10-29 10:11 ` bugzilla-daemon
2011-10-29 18:31 ` bugzilla-daemon
2011-10-30 20:48 ` bugzilla-daemon
2011-10-30 22:35 ` bugzilla-daemon
2011-10-31 10:34 ` bugzilla-daemon
2011-11-01 11:17 ` 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:
  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=20111017213035.DDF192F78004@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.org \
    /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).