kreyren/OSHW-System-On-Module
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Rewording the proprietary module section

Browse Source
This commit is contained in:
Jacob Hrbek 2023-08-04 04:25:26 +02:00 committed by Gitea
parent 52b7066911
commit 50af800b83
Signed by: Gitea
GPG Key ID: 0DD13DBC6B5433D3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -38,9 +38,9 @@ This effectically allows us to make variety of OSHW projects very economically t
### Use of proprietary module boards ### Use of proprietary module boards
Additionally many chips are near impossible to get as OSHW-compatible due to consumer-hostile business plan and strategy until the chip reaches it's peak economical cycle and becomes obsolete. Additionally many chips are near impossible to get as OSHW-compatible due to consumer-hostile business plan and strategy until the chip reaches it's peak economical cycle and becomes obsolete (some not even after obsolescence such as Apple, Inc.).
To allow us to use better hardware this would allow the module boards to be produced in batches of 1000+ to keep the cost down while not affecting the hackability and flexibility of the OSHW project as the user can always use OSHW Module Board and only have the option to use proprietary module board until it's manufacturer decides to release the required documents (documentation for the chips, reference schematics/design, etc..) In order to use more resource efficient hardware this would allow the module boards to be produced in batches of 1000+ to keep the cost economical while significantly limiting tha bad impact from proprietary components on hackability and flexibility of the OSHW project (though the security and privacy concerns will remain) as the user will still be able to adjust the platform board to fit their requirements.
## Issue ## Issue