Ticker problem on ppc405 - FIXED

Joel Sherrill <joel@OARcorp.com> joel.sherrill at OARcorp.com
Wed Oct 20 17:42:01 UTC 2004


Smith, Gene wrote:
> Ralf Corsepius wrote, On 10/20/2004 10:49 AM:
> 
> <big snip>
> 
>>> Just add
>>> #define <bsp.h>
>>> ?
>>
>>
>> Yes, cf. PR 696
>> http://www.rtems.org/cgi-bin/gnatsweb.pl?debug=&database=RTEMS&cmd=view+audit-trail&cmd=view&pr=696 
>>
>>  
> 
> 
> How do you get a uid/pw to enter bugs or comments here?
> (guest seems to work for read-only)

And for creating new PRs.  I have emailed you a write privileged
account and password.

>>>> To let bspopts.h contain it, you have to add the corresponding
>>>> configure-script magic to your BSP's configure.ac
>>>> (cf. c/src/lib/libbsp/powerpc/helas403/configure.ac) and then to run
>>>
>>>
>>> configure.ac here already contains line:
>>> RTEMS_BSPOPTS_SET([PPC_USE_SPRG],[*],[1])
>>> Is this the "magic" for defining it to 1?
>>
>>
>> Not quite, it is the magic to let it default to 1.
>>
>> You can override it when invoking the configure script via an
>> environment variable.
> 
> 
> So if I want PPC_USE_SPRG to zero in bspopts.h I could do something like:
> $ export PPC_USE_SPRG=0
> $ ../configure ......
> $ make all

That's my understanding.  Yes.

>>> Is the above magic what causes bspopts.h to contain:
>>> #define PPC_USE_SPRG 1
>>> ?
>>
>>
>> Yes.
>>
>>
>>> Why does <BSP>/include/bspopts.h.in contain
>>> #undef PPC_USE_SPRG
>>> ?
>>
>>
>> This file is an "autoheader", i.e. it is automatically generated by
>> autoheader reading configure.ac as input file.
>>
>> bspopts.h.in later is used as input template for generating bspopts.h
>> when running the configure script.
>>
>> Ralf
>>
>>


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985




More information about the users mailing list