public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gonçalo Antunes" <gmma@gmma.net>
To: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Minimum RAM space required for ecos
Date: Fri, 27 May 2005 16:43:00 -0000	[thread overview]
Message-ID: <002001c5625d$9feac150$0200a8c0@pcgoncalo> (raw)
In-Reply-To: <15d22f8cc.f8cc15d22@vsnl.net>

Just for curiosity... wich bluetooth stack will you deploy?



----- Original Message ----- 
From: <aprakash@tataelxsi.co.in>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Sent: Thursday, May 26, 2005 1:50 PM
Subject: Re: [ECOS] Minimum RAM space required for ecos


>
>          So minimum 256KB is required, if i'd included Network support.. 
> should i spend more memory for bluetooth ?... or would it share with this 
> 256KB ?...
>
>
> Thanks
> Prakash
> ----- Original Message -----
> From: Gary Thomas <gary@mlbassoc.com>
> Date: Thursday, May 26, 2005 6:14 pm
> Subject: Re: [ECOS] Minimum RAM space required for ecos
>
>> On Thu, 2005-05-26 at 17:37 +0500, aprakash@tataelxsi.co.in wrote:
>> > Hi,
>> >
>> >              Thanks for your reply .... I'd like to deploy
>> bluetooth
>> > stack and network support.i have ROM in MB and RAM in KBs ..
>> >
>>
>> Any sort of networking is going to require a fair amount of RAM.  I'd
>> think you'd want no less than 256KB.  Much less than that and you're
>> just dreaming (IMO).
>>
>> >
>> > Thanks
>> > Prakash
>> >
>> > ----- Original Message -----
>> > From: Gary Thomas <gary@mlbassoc.com>
>> > Date: Thursday, May 26, 2005 6:00 pm
>> > Subject: Re: [ECOS] Minimum RAM space required for ecos
>> >
>> > > On Thu, 2005-05-26 at 17:48 +0530, Annamalai Prakash wrote:
>> > > > Hi List,
>> > > >
>> > > >           Is there any minimum RAM requirement to run ECOS on
>> my
>> > > ARM board
>> > > > ?.. Would it be run on few kbs of RAM ?..
>> > >
>> > > This completely depends on what you are expecting the board to
>> do/run.> > It is possible to configure a minimal eCos application,
>> running
>> > > from
>> > > ROM, that only uses a very small amount (probably less than
>> 32KB) of
>> > > RAM.  Of course, such a minimal application won't be able to
>> really> > do much.
>>
>> -- 
>> ------------------------------------------------------------
>> 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
>
> 



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

  reply	other threads:[~2005-05-27  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 23:01 aprakash
2005-05-27 16:43 ` Gonçalo Antunes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 13:57 aprakash
2005-05-26 21:45 ` Gary Thomas
2005-05-26 13:01 Annamalai Prakash
2005-05-26 13:32 ` Gary Thomas

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='002001c5625d$9feac150$0200a8c0@pcgoncalo' \
    --to=gmma@gmma.net \
    --cc=ecos-discuss@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).