From: Gary Thomas <gthomas@redhat.com>
To: pengyu xue <pyxue@t2-design.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] dynamic allocation memory
Date: Wed, 06 Sep 2000 05:17:00 -0000 [thread overview]
Message-ID: <XFMail.20000906061654.gthomas@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0009061500180.5066-100000@Gaotian>
On 06-Sep-2000 pengyu xue wrote:
>
> Hi, all:
>
> I use the malloc function in my device driver, but it seems
> something is wrong with this function. So I wonder that ecos-131 support
> the dynamic memory allocation in the target vrc4300-4373. Can someone
> tell me more information about this? And I used memory pool, the same
> result I meet. How to use the memory pool functions?
What does 'something is wrong' mean? Does it work at all? Do you run
out of malloc memory before you think you should? We'll need more data
before we can help much.
As was also pointed out, calling malloc() in an ISR or even DSR is probably
not a really good idea. Can you tell us more about what you're trying to
do?
prev parent reply other threads:[~2000-09-06 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 0:10 pengyu xue
2000-09-06 0:30 ` Andrew Lunn
2000-09-06 5:17 ` Gary Thomas [this message]
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=XFMail.20000906061654.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=pyxue@t2-design.com \
/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).