Difference between revisions of "Talk:Diagnostic & repair"
(HACKING File) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
--[[User:Ilya|Ilya]] 08:45, 30 October 2005 (CST) | --[[User:Ilya|Ilya]] 08:45, 30 October 2005 (CST) | ||
| + | |||
| + | == HACKING File == | ||
| + | |||
| + | Is there a file that gives a reasonably thorough introduction to the software? I understand that for GPL systems this is normally in a file called HACKING. It should include information such as a list of the major source files, functions, block diagram indicating the basic program flow, how data is passed from web client to Axis to FPGA, and so on. Since it is open hardware, a tutorial on the architecture and key circuit design features would be useful too. It would be very helpful in reducing the potential barrier (i.e. the cost of entry) to making improvements or customization of the software or hardware. | ||
Latest revision as of 01:09, 1 January 2006
Ilya, it is not exactly "User information" - users will can get cameras with capacitors that need to be re-soldered :-)
Diagnosis of the bad boards is helpful only for the production - to find out what was wrong in the process.
So it is good to have a list of encountered failures (we do not have to keep it secret)- some can show up later and that needs improving production testing. But it should clearly be separate from the user docs. --Andrey.filippov 01:50, 30 October 2005 (CST)
OK, I understand it now. I will delete that chapter from Cameras Manual.
--Ilya 08:45, 30 October 2005 (CST)
HACKING File
Is there a file that gives a reasonably thorough introduction to the software? I understand that for GPL systems this is normally in a file called HACKING. It should include information such as a list of the major source files, functions, block diagram indicating the basic program flow, how data is passed from web client to Axis to FPGA, and so on. Since it is open hardware, a tutorial on the architecture and key circuit design features would be useful too. It would be very helpful in reducing the potential barrier (i.e. the cost of entry) to making improvements or customization of the software or hardware.
