From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001115] UART, Ethernet and wallclock driver patches for LPC17XX
Date: Tue, 18 Jan 2011 13:02:00 -0000 [thread overview]
Message-ID: <20110118130207.B96D22F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001115-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=1001115
--- Comment #3 from Ilija Kocho <ilijak@siva.com.mk> 2011-01-18 13:02:05 GMT ---
(In reply to comment
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001114#c12)
Sorry for jumping into another bug but I think it is for good reason.
>
> For each affected package, we could optionally change the CDL "display" and
> "description" strings and the zeroth package "alias" string in ecos.db
> (displayed by configtool) to make them more generic. We should not change any
> CDL macro names or the API.
Talking about "description" there is one issue for which I planned to ask for
help but I forgot. It affects:
http://bugs.ecos.sourceware.org/attachment.cgi?id=1079 and
http://bugs.ecos.sourceware.org/attachment.cgi?id=1080
Descriptions for interrupt priority look like this:
description "
This option selects the interrupt priority for the EMAC interrupts.
There are CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS priority levels
corresponding to the values 0 through
CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS-1 decimal, of which the highest
value is the lowest priority. The reset value of
these registers defaults all interrupts to the lowest priority,
allowing a single write to elevate the priority of an
individual interrupt."
I know that this is less than perfect, but with my limited knowledge of tcl/CDL
I failed to find a way to enforce substitution of
CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS. I tried something like
"xxx" . CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS . "xxx"
and some other combinations involving braces and brackets.
Hope there is a way to do it.
--
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.
next prev parent reply other threads:[~2011-01-18 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1001115-104@http.bugs.ecos.sourceware.org/>
2011-01-16 8:53 ` bugzilla-daemon
2011-01-18 2:00 ` bugzilla-daemon
2011-01-18 13:02 ` bugzilla-daemon [this message]
2011-01-18 18:19 ` bugzilla-daemon
2011-01-19 5:28 ` bugzilla-daemon
2011-02-03 15:27 ` bugzilla-daemon
2011-02-21 18:17 ` bugzilla-daemon
2011-02-21 18:19 ` bugzilla-daemon
2011-02-27 16:26 ` bugzilla-daemon
2011-02-27 16:28 ` bugzilla-daemon
2011-02-27 18:25 ` bugzilla-daemon
2011-03-13 14:21 ` bugzilla-daemon
2011-03-13 14:24 ` bugzilla-daemon
2011-03-13 16:44 ` 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=20110118130207.B96D22F78004@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).