On Fri, Mar 26, 2010 at 12:04 AM, Paul Goyette wrote:
> On Thu, 25 Mar 2010, Matthias Drochner wrote:
>
>>
>> jeanyves.mig...@free.fr said:
>>>
>>> There should be some way to serialize/deserialize prop/plistref
>>> objects within the kernel, but I never found a solution. I suppose
>>> you will h
On Fri, 26 Mar 2010, haad wrote:
I think it should be avoided at all costs. With proplists, you give up
type
safety
and you create a lot of overhead. This is acceptable for kernel-user
interfaces
in some cases but not within the kernel.
So would it be appropriate for me to expose sysmon_envsys
On Thu, Mar 25, 2010 at 11:54 PM, Matthias Drochner
wrote:
>
> jeanyves.mig...@free.fr said:
>> There should be some way to serialize/deserialize prop/plistref
>> objects within the kernel, but I never found a solution. I suppose
>> you will have to dig deeper than I did :/
>
> I think it should
On Thu, 25 Mar 2010, Paul Goyette wrote:
> So would it be appropriate for me to expose sysmon_envsys's "global mutex" and
> its device list in order for acpi_apm to scan for battery sensors and A/C
> adapters?
I think better to not expose subsystem internals.. but can you split the
sysmon_envsys
On 03/25/10 23:54, Matthias Drochner wrote:
jeanyves.mig...@free.fr said:
There should be some way to serialize/deserialize prop/plistref
objects within the kernel, but I never found a solution. I suppose
you will have to dig deeper than I did :/
I think it should be avoided at all costs. W
On Thu, 25 Mar 2010, Matthias Drochner wrote:
jeanyves.mig...@free.fr said:
There should be some way to serialize/deserialize prop/plistref
objects within the kernel, but I never found a solution. I suppose
you will have to dig deeper than I did :/
I think it should be avoided at all costs
jeanyves.mig...@free.fr said:
> There should be some way to serialize/deserialize prop/plistref
> objects within the kernel, but I never found a solution. I suppose
> you will have to dig deeper than I did :/
I think it should be avoided at all costs. With proplists, you give up type
safety
and
On 03/25/10 19:08, Paul Goyette wrote:
I have a situation where I would like to invoke sysmonioctl_envsys()
from within some other kernel code. But I'm not quite sure what variable
type should be used for the 3rd argument. The call requires a 'void
*data' which gets cast to a 'struct plistref *'
I have a situation where I would like to invoke sysmonioctl_envsys()
from within some other kernel code. But I'm not quite sure what
variable type should be used for the 3rd argument. The call requires a
'void *data' which gets cast to a 'struct plistref *' and is eventually
used as the argum
