>In the Updating LinuxCNC documentation, section 12.2.2 Homing says
typo: should say homing.h
updated:
https://github.com/LinuxCNC/linuxcnc/commit/4977d559411
--
Dewey Garrett
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
In the Updating LinuxCNC documentation, section 12.2.2 Homing says
Ø A homing api is provided by src/emc/motion/homing.ini to support users'
custom homing code in out-of-tree homing.c source files.
What is this? Where is this?
___
On 8/14/19 6:48 AM, Les Newell wrote:
I am working on a hal module that may need a variable amount of memory
depending on it's configuration. Is it acceptable to use malloc in a hal
module? Should I use hal_malloc or is that specifically for pins?
Memory management is different for realtime
Hi Andy,
Thanks for looking into this.
Looking at the kinematics modules I suspect malloc can only be used in
user space modules. For example genserkins.c seems to use hal_malloc if
RTAPI is defined and malloc if ULAPI is defined. I also see references
to rtapi_kmalloc. hm2 seems to be
On Wed, 14 Aug 2019 at 15:08, Les Newell wrote:
> I am working on a hal module that may need a variable amount of memory
> depending on it's configuration. Is it acceptable to use malloc in a hal
> module? Should I use hal_malloc or is that specifically for pins?
As I understand it, hal_malloc
Further to this question, how do I go about deleting the memory at
shutdown? I see a reference in the halcompile docs to EXTRA_CLEANUP but
the docs aren't too clear on how I iterate through each loaded module to
delete it's memory (if allocated).
Les
On 14/08/2019 13:48, Les Newell wrote:
I
I am working on a hal module that may need a variable amount of memory
depending on it's configuration. Is it acceptable to use malloc in a hal
module? Should I use hal_malloc or is that specifically for pins?
Les
___
Emc-developers mailing list
