On Nov 9, 2007 5:03 PM, Steven A. Falco <[EMAIL PROTECTED]> wrote:
>  Your patch makes sense.
>  I have some results, but I'm not sure I understand what they mean.  I've
> attached the test program that I am using.  Here is what it outputs:
>  bash-3.00# ./o2
>  Trying to free nonexistent resource <0000000000000000-00000000c0000001>
>  get leds: -16 Device or resource busy
>  put leds: 0 Success
>  Trying to free nonexistent resource <0000000000000000-ffffffffffffffff>
>  get low_mem: -16 Device or resource busy
>  put low_mem: 0 Success
>  I am a little unclear on request_resource() - the return code is backwards
> of what I would have expected.  Looking at examples in the kernel, it
> appears that request_resource() returns EBUSY when things go well, and it
> returns 0 when things go badly.  Like I said, that seems backwards, but I
> guess it makes sense - EBUSY apparently means that the resource is _now_
> busy?

request_region returns a pointer to a struct resource, and NULL if the
resource is already reserved.

                                               Gilles Chanteperdrix

Xenomai-core mailing list

Reply via email to