Re: [Xenomai-core] User space drivers on PPC440

2007-11-14 Thread Steven A. Falco
That works perfectly. Thanks! Steve Philippe Gerum wrote: Philippe Gerum wrote: Steven A. Falco wrote: Solved. As you pointed out, Xenomai inverts the returned value from request_region. So, that was a bug in my application. However, turns out that instead of request_region, I

Re: [Xenomai-core] User space drivers on PPC440

2007-11-11 Thread Philippe Gerum
Philippe Gerum wrote: > Steven A. Falco wrote: >> Solved. As you pointed out, Xenomai inverts the returned value from >> request_region. So, that was a bug in my application. >> >> However, turns out that instead of request_region, I have to use >> request_mem_region. This is because the I/O reg

Re: [Xenomai-core] User space drivers on PPC440

2007-11-10 Thread Philippe Gerum
Steven A. Falco wrote: > Solved. As you pointed out, Xenomai inverts the returned value from > request_region. So, that was a bug in my application. > > However, turns out that instead of request_region, I have to use > request_mem_region. This is because the I/O region only goes up to > 2^32,

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Philippe Gerum
Steven A. Falco 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 <-c001> > get

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Steven A. Falco
Solved. As you pointed out, Xenomai inverts the returned value from request_region. So, that was a bug in my application. However, turns out that instead of request_region, I have to use request_mem_region. This is because the I/O region only goes up to 2^32, but the mem region goes up to 2

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Gilles Chanteperdrix
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 res

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Steven A. Falco
Many apologies. I forgot to build the user library. Now the addresses look better: bash-3.00# ./o2 req: start = 0001c002 len = 000d rel: start = 0001c002 len = 000d Trying to free nonexistent resource <0001c002-0001c00e> get leds: -16 Device or resou

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Steven A. Falco
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 <-c001> get leds: -16 Device or resource busy pu

Re: [Xenomai-core] User space drivers on PPC440

2007-11-09 Thread Philippe Gerum
Philippe Gerum wrote: > Steven A. Falco wrote: >> The rt_misc_get_io_region() has the "start" argument as an unsigned >> long. On the PPC440, we have a 36-bit address space, where the I/O >> registers are generally above the 4GB area. For example, the UART is at >> address 0x1ef600300. >> >> T

Re: [Xenomai-core] User space drivers on PPC440

2007-11-08 Thread Philippe Gerum
Steven A. Falco wrote: > The rt_misc_get_io_region() has the "start" argument as an unsigned > long. On the PPC440, we have a 36-bit address space, where the I/O > registers are generally above the 4GB area. For example, the UART is at > address 0x1ef600300. > > The Linux request_region call

Re: [Xenomai-core] User space drivers on PPC440

2007-11-08 Thread Steven A. Falco
> (i.e. CONFIG_RESOURCES_64BIT is set even though this is a 23-bit > processor). Make that a 32-bit processor. :-[ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core

[Xenomai-core] User space drivers on PPC440

2007-11-08 Thread Steven A. Falco
The rt_misc_get_io_region() has the "start" argument as an unsigned long. On the PPC440, we have a 36-bit address space, where the I/O registers are generally above the 4GB area. For example, the UART is at address 0x1ef600300. The Linux request_region call has "start" typed as a resource_siz