All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] User space drivers on PPC440
Date: Wed, 14 Nov 2007 13:45:17 -0500	[thread overview]
Message-ID: <473B423D.1010006@domain.hid> (raw)
In-Reply-To: <47373B92.1050008@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

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 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^64.
>>>
>>> So, attached is a patch to add two new syscalls: rt_misc_get_mem_region
>>> and rt_misc_put_mem_region.
>>>
>>>       
>> Thanks. At this chance, I've reworked the I/O region support to
>> introduce descriptors, so that this API conforms to the
>> one-descriptor-per-object rule commonly followed by other services from
>> the native skin. I've merged your MMIO support on top of this. The added
>> bonus is that auto-cleanup upon process exit becomes available with I/O
>> regions too, since we now have the proper descriptor to hold the cleanup
>> data.
>>
>> The calls supporting this scheme are named rt_io_get_region, and
>> rt_io_put_region, taking a RT_IOREGION object descriptor to hold the
>> internal resource information. The rt_misc_io_get/put_region API is now
>> deprecated starting with 2.4-rc6, albeit still available to allow for
>> smooth transition; one will only get a warning as a reminder to upgrade
>> to the new calls when using the old ones. e.g.
>>
>> RT_IOREGION iorn;
>>
>> rt_io_get_region(&iorn, label, start, len, IORN_IOPORT)
>> is equivalent to calling:
>> rt_misc_get_io_region(start, len, label)
>>
>> the same way,
>>
>> rt_io_get_region(&iorn, label, start, len, IORN_MEMORY)
>>     
>
> s,IORN_MEMORY,IORN_IOMEM,
>
> (for consistency reason with Linux's naming scheme)
>
>   
>> is equivalent to calling:
>> rt_misc_get_mem_region(start, len, label)
>>
>> Conversely,
>>
>> rt_io_put_region(&iorn)
>> is equivalent to calling:
>> rt_misc_put_io/mem_region(start, len)
>>
>>
>>     
>
>
>   

[-- Attachment #2: Type: text/html, Size: 2485 bytes --]

  reply	other threads:[~2007-11-14 18:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 22:46 [Xenomai-core] User space drivers on PPC440 Steven A. Falco
2007-11-08 22:47 ` Steven A. Falco
2007-11-08 23:58 ` Philippe Gerum
2007-11-09 11:41   ` Philippe Gerum
2007-11-09 16:03     ` Steven A. Falco
2007-11-09 16:44       ` Steven A. Falco
2007-11-09 17:02       ` Gilles Chanteperdrix
2007-11-09 17:03       ` Philippe Gerum
2007-11-09 17:31         ` Steven A. Falco
2007-11-10 16:28           ` Philippe Gerum
2007-11-11 17:27             ` Philippe Gerum
2007-11-14 18:45               ` Steven A. Falco [this message]
2007-11-15 22:09       ` [Xenomai-help] buildbot and state of xenomai on PPC440? Niklaus Giger
     [not found]         ` <473CC49D.3030504@domain.hid>
2007-11-19 19:28           ` Niklaus Giger
2007-11-22  9:55         ` Philippe Gerum

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=473B423D.1010006@domain.hid \
    --to=sfalco@domain.hid \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.