- From: wicky.zhang <wicky.zhang_at_gmail.com>
- Date: Tue, 14 Feb 2006 17:10:35 +0800
---There shouldn't be any problem writing a custom Comedi driver for it. All the bus-specific hardware access is confined to the individual device drivers; the Comedi ---core does not depend on hardware at all! ---As this is a fairly specialized application, you probably want to avoid building the full suite of drivers and just build your custom driver and the Comedi core. You ---can edit the comedi/drivers/Makefile.am file to do that (followed by running ./autogen.sh to regenerate and rerun the ./configure script). ---Thank you, I know that the Comedi core does not depend on hardware at all, but for my particular application, i think that choosing an appropriate interface ---should simplify the programming work because lots of reference. Finally, I choose SPI interface A/D and D/A chip, does anyone have experience about it? I have ---not written any Comedi driver at all. ---Thank you! ---Best regards, Another question, If I connect 2 SPI A/D chip together in hardware and connect 2 SPI D/A chip together, I think I need to implement 2 SPI controllers in FPGA and connect them to PPC core. Do I need to treat the 2 SPI controllers as two different devices when writing the Comedi driver? Is there any more convenient hardware connection for writing the driver? what about parallel A/D and D/A chip? Furthermore, I want to design some digital inputs and digital outputs in my daughter boards, what connection method should I choose for the convenient of writing the Comedi driver? Thank you! Best regards, Wicky
Attachments
- text/x-vcard attachment: wicky.zhang.vcf
Received on 2006-02-14Z09:10:35