Re: [ECOS] Re: problem with ecos in fedora 4

[Gary Thomas <gary at mlbassoc dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sébastien Picque wrote:
> Hi Gary,
> 
> I have a problem by send my message to : ecos-discuss@ecos.sourceware.org
> What is the mail to send to the group mail list ?

You've got the address right, but this mailing list does not accept
HTML messages (that's exactly what the report below says!)

Try resending in pure text (as this message is).

> thank u
> It always reply me :
> Hi. This is the qmail-send program at sourceware.org.
> I'm afraid I wasn't able to deliver your message to the following
> addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> 
> <ecos-discuss@ecos.sourceware.org>:
> Invalid mime type "text/html" detected in message text or attachment.
> Please send plain text messages only.
> See http://sourceware.org/lists.html#sourceware-list-info for mailing list
> info for this site.
> Contact ecos-discuss-owner@ecos.sourceware.org if you have questions
> about this. (#5.7.2)
> 
> --- Enclosed are the original headers of the message.
> 
> Hello all,
> 
> I would like to add the profiling function for an ARM7 pltform
> (hal_enable_profile_timer) like in the example (mp8xx or sam1100mm).The
> different steps are the following one, if I well understood :
> 1) Add in the cdl :     implements    CYGINT_PROFILE_HAL_TIMER
> 2) Add in the *misc.c file the function like 
> hal_enable_profile_timer(), profile_isr().
> 3) Do I need to attach an ISR/DSR for the timer I am going to intialize
> ??? or do I only need to set the timer and start it (is it engough).
> 4) The fact that adding hal_enable_profile_timer(), avoid the issue of
> compilation : get the following unresolved conflict:
> CYGINT_PROFILE_HAL_TIMER != 0 ?????????????
> 
> Sorry but I don't understand the link between add function
> hal_enable_profile_timer and CYGINT_PROFILE_HAL_TIMER. Does it add a
> ISR/DSR timer to avoid this conflict. There is something I didn't catch
> or missed...
> 
> Thank you for help and support
> 
> Sébastien
> 
> 
> 
> 
> 
> 
> ----- Original Message ----- From: "Gary Thomas" <gary@mlbassoc.com>
> To: <rmahmoud@sysdsoft.com>
> Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
> Sent: Sunday, June 24, 2007 3:38 PM
> Subject: Re: [ECOS] Re: problem with ecos in fedora 4
> 
> 
> rmahmoud@sysdsoft.com wrote:
>>>> Hi,
>>>> i use ecos 1.3.1, i think the ecos configure by the default values.
>>>> does this ecos version incompatible with fedore?
> 
> You *still* didn't tell us what the target is, how you configured
> eCos, etc.
> 
> If you're trying to use eCos of that vintage using the synthetic target
> (i.e. eCos running as a process on Linux itself), then yes, eCos can't
> run on newer kernels.  Look through the mailing lists - there have been
> many discussions on this part.
> 
> Best advice - update to the latest anonymous CVS :-)
> 
>>>> Please keep replies on the eCos mailing list(s) so that all may benefit.
>>>>
>>>> rmahmoud@sysdsoft.com wrote:
>>>>>>> hello,
>>>>>>> i worked in a project that used Ecos-2 as operating system. the code
>>>>>>> work well at different linux (Ubuntu ,  Mandriva, Susu) except Fedora
>>>>>>> core 4 it gives segmentation faults at the begin of run or debug. i
>>>>>>> think the segmentation fault eccur before calling my own functon
>>>>>>> cyg_user_start(). this is the stack of the segmantion fault:
>>>>>>> l2Testing_device [C/C++ Local Application]
>>>>>>> gdb/mi (06/20/2007 9:29 PM) (Suspended)
>>>>>>> Thread [0] (Suspended: Signal 'SIGSEGV' received. Description:
>>>>>>> Segmentation fault.)
>>>>>>> 6 <symbol is not available> 0x001c0d78
>>>>>>> 5 <symbol is not available> 0x00000001
>>>>>>> 4 <symbol is not available> 0x00a52428
>>>>>>> 3 <symbol is not available> 0xbfdae5b0
>>>>>>> 2 <symbol is not available> 0x00000024
>>>>>>> 1 <symbol is not available> 0x00000000
>>>>
>>>> This doesn't tell me anything about what you are doing, other
>>>> than "it doesn't work on Fedora".
>>>>
>>>> * What source base are you using?  CVS [date]?
>>>> * How did you configure eCos to build this kernel?
>>>> * What application are you running?  Can you share?
>>>> * Have you run the standard eCos tests on this platform?
>>>>
>>>> Without this information, we can't help :-(
> 
>>
- --
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>>

- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD4DBQFGfwUwmaKbSsQGV8ARAqfZAKCfB8pf0BKQ+nX9j4FeWPMLmnXK7QCY1L8f
c2Oa0aSbSY0p55KB2E/lHQ==
=nszg
-----END PGP SIGNATURE-----

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss