- To: Elad Yosef <elad.yosef@xxxxxxxxx>
- Subject: Re: removing all interrupts code and data from RedBoot image
- From: Gary Thomas <gary@xxxxxxxxxxxx>
- Date: Thu, 05 Jan 2012 14:55:27 -0700
- Cc: ecos-discuss@xxxxxxxxxxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <CAOFa9c3JqNyohwoHm7zP8RaqXBkznN2Q3L_9Azhm=W=xODm6EA@mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0
On 2012-01-05 14:03, Elad Yosef wrote:
Hi all,
I'm short in RAM& ROM for my Redboot run
What I want to do is to eliminate all the interrupts code and data.
In the hal_mon_init I'll register the exception handler to handle
interrupts (it will halt CPU since no interrupt is expected...)
Can someone give me points where to start?
Since RedBoot doesn't use interrupts, you may not find much to save.
What's your target architecture?
Have you looked at a load map to see what might be cut, etc?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
[Linux Embedded]
[U-Boot V2]
[Linux Kernel]
[Linux MIPS]
[Linux ARM]
[Linux for the Blind]
[Linux Resources]
[Photo]
[Yosemite]
[ISDN Cause Codes]
[ECOS Home]
[Site Home]