[Bug 1001115] UART, Ethernet and wallclock driver patches for LPC17XX

[bugzilla-daemon@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

Sergei Gavrikov <sergei.gavrikov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergei.gavrikov@gmail.com

--- Comment #4 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-18 18:19:35 GMT ---
> 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.

Ilija, AFAIK, there is no way to get a value of any CDL option
out-side the CDL expressions. Well there is get_data() built-in
function, but it is for *CDL expressions* only.

The CDL commands 'display' and 'description' as well expect only 1
text argument, I mean that 'description' is something like this
(rough prototype in Tcl)

  proc description text {
    set etext [eval $text]
    ...
  }

So, we see new etext value in ecos.ecc (configtool).

The below is okay

  set ::max 16
  description "There are [expr {$::max - 1}] levels"

In configtool we'll see  'There are 15 levels."

And this one is not possible to evaluate

  set ::max CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS
  description "There is [expr {$::max - 1}] levels"

because the max's value is just string
"CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS".

And get_data() function is out the scope (i.e. it is useless for
'description' command).

IMO, such a variant is quite enough there

decription "
    This option selects the interrupt priority for the EMAC
    interrupts.  There are a few priority levels corresponding to the
    values 0 through CYGNUM_DEVS_ETH_IRQ_PRIORITY_LEVELS-1, 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."

*a few*, *a number* are good substitutions for text descriptions. In any
case user will see what does the number means in ecos.ecc/configtool.

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