This manual/wiki attempts to provide a quick and easy guide to help users get started in open source development, including:
Although a major portion of this site uses the Blackfin as an example System on Chip, all the device drivers for various Analog Devices peripherals should run on any architecture that the operating system supports (if it doesn't, it is a bug, and please let us know). This manual is not a replacement for any other mainline documentation; rather this documentation gives an overview of the components essential to working with open source for Analog Devices components, including the Blackfin processor.
The documentation is split into a few main sections (Full Table of Topics)
If you have questions, have a bug report, or want to look at source code, check out our processes and then goto the main web site.
This documentation and courseware project is a small part of the Blackfin Koop. The word “Koop” is derived from the English word cooperative, which typically describes a jointly owned enterprise that produces and distributes goods and services and is run for the benefit of its owners. In this situation, it takes nothing to be an “owner”, except the understanding/acknowledgment that you get out, what you put in — that is, sharing and cooperation. While the Koop does includes a small dedicated team of contributors (some volunteer, some Analog Devices employees), everything is done for the betterment of the entire Koop - collaborating with others (including you) for a common purpose and benefit. What this means is that you (and we) must be willing to adjust to differences in opinion and implementation in order to obtain agreement for the Koop's greater good.
This documentation is all about sharing knowledge and experience. If you feel inspired or just want to make sure you will remember something you found out, please contribute to this wiki by logging in. If you would like to help volunteer to edit, add pages, fix mistakes, or draw better pictures, you can check that your additions will meet the requirements of the copyright information, and then ask. If you just want to point out bugs in the documentation, we like that too.
Complete Table of Contents/Topics

