Re: Arcnet drivers

On Mon, 30 Jan 2006, NZG wrote:

> Sure, but Comedi typically fills in that hardware hot spot right?

Well, "typically" is a bit of an overstatement :-) Comedi provides a lot of
drivers for AD/DA cards, but not for communication buses...

>
> On Monday 30 January 2006 12:53 pm, J.D. Yamokoski wrote:
>> Thanks for the clarification. That was my understanding about Orocos
>> being hardware independent. I know others in the past have successfully
>> integrated RTAI and arcnet communication. I guess I was just
>> broadcasting to see if there was anyone paying attention to these lists
>> who has experience with this.
>>
>> Herman Bruyninckx wrote:
>>> On Mon, 30 Jan 2006, NZG wrote:
>>>>> While I am spamming the mailing list, I thought I would start another
>>>>> thread about questions I have on arcnet card drivers. The problem is I
>>>>> am just about clueless when it comes to Linux and device drivers to
>>>>> begin with (I am a native windows programmer).
>>>>
>>>> I don't know much about Arcnet, but IMHO Orocos seems to be a more
>>>> popular choice for open robot control. (If someone disagree's here
>>>> please set me straight, I'm just getting into this field myself)
>>>
>>> Arcnet is about _hardware drivers_ for a particular type of
>>> communication channel; orocos is a set of libraries to control robots
>>> and machine tools, _independent_ of the hardware you use. These driver
>>> issues are what we call "hot spots" in the Orocos framework: _you_ have
>>> to fill them in for your particular hardware, because Orocos wants to
>>> remain hardware neutral.

Herman

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

_______________________________________________
Orocos mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm