On Fri, Jun 12, 2009 at 9:58 PM, Kumar Gala wrote:
>
> On Jun 12, 2009, at 8:27 AM, Li Yang wrote:
>
>> On Thu, Jun 11, 2009 at 9:32 PM, Kumar Gala
>> wrote:
>>>
>>> On Jun 11, 2009, at 4:47 AM, Li Yang-R58472 wrote:
>>>
> On May 12, 2009, at 3:35 AM, Li Yang wrote:
>
>> Add the mapping
On Jun 12, 2009, at 8:27 AM, Li Yang wrote:
On Thu, Jun 11, 2009 at 9:32 PM, Kumar
Gala wrote:
On Jun 11, 2009, at 4:47 AM, Li Yang-R58472 wrote:
On May 12, 2009, at 3:35 AM, Li Yang wrote:
Add the mapping functions used to support direct IO memory
access of
rapidIO.
Signed-off-by: Zh
On Thu, Jun 11, 2009 at 9:32 PM, Kumar Gala wrote:
>
> On Jun 11, 2009, at 4:47 AM, Li Yang-R58472 wrote:
>
>>> On May 12, 2009, at 3:35 AM, Li Yang wrote:
>>>
Add the mapping functions used to support direct IO memory access of
rapidIO.
Signed-off-by: Zhang Wei
Signed-off
On Jun 11, 2009, at 4:47 AM, Li Yang-R58472 wrote:
On May 12, 2009, at 3:35 AM, Li Yang wrote:
Add the mapping functions used to support direct IO memory access of
rapidIO.
Signed-off-by: Zhang Wei
Signed-off-by: Li Yang
Use inbnd/outbnd instead of inb/outb which make one think of
byte l
>On May 12, 2009, at 3:35 AM, Li Yang wrote:
>
>> Add the mapping functions used to support direct IO memory access of
>> rapidIO.
>>
>> Signed-off-by: Zhang Wei
>> Signed-off-by: Li Yang
>
>Use inbnd/outbnd instead of inb/outb which make one think of
>byte level io accessors.
>
>As I look at t
On May 12, 2009, at 3:35 AM, Li Yang wrote:
Add the mapping functions used to support direct IO memory access of
rapidIO.
Signed-off-by: Zhang Wei
Signed-off-by: Li Yang
Use inbnd/outbnd instead of inb/outb which make one think of byte
level io accessors.
As I look at this I don't thin
Add the mapping functions used to support direct IO memory access of
rapidIO.
Signed-off-by: Zhang Wei
Signed-off-by: Li Yang
---
drivers/rapidio/rio.c | 95 +++
include/linux/rio.h | 25
include/linux/rio_drv.h | 24 +
