Hello, I’m currently looking into creating a driver for a family of fields interfaces that share a common hardware connector implementation. (http://www.anybus.com/products/abcc30.shtml). By the looks of it, I think it would make sense to separate the driver into a kind of „hardware interface“ part and a „protocol“ part. The reasoning is: - there can be one or more hardware connectors in a system. - those connectors can be be populated with a variety of different modules that implement a different fields each - they can even be left unpopulated - the protocol, on the other hand can only exist if there is a hardware connector that it can use. - this is a one-to-none or one-to-one relation. I’m aware that this is a very generic and top-level question, but maybe someone can give me a few pointers or keywords to proceed: - The subsystems i found that offer such relations are overly complex (like PCI or USB), so if possible I would rather not use them as templates. Is there anything recommendable to look at? - Is there a recommendable way to for creating such relations? - Did I go horribly wrong in my reasoning somewhere?
Thanks! Josef -- _____________________________________________________________ R-S-I Elektrotechnik GmbH & Co. KG Woelkestrasse 11 D-85301 Schweitenkirchen Fon: +49 8444 9204-0 Fax: +49 8444 9204-50 www.rsi-elektrotechnik.de _____________________________________________________________ Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg USt-IdNr.: DE 128592548 _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
