GeezerVison is showing github.com — Sources for MCU binaries? · Issue #2 · OSVR/OSVR-HDK
Sources for MCU binaries? #2DescriptionWill the microcontroller firmware be made open source? It would be nice to have that available so support for other displays could be added. Reacted by Arto Bendiken and Samuel Sarle ActivityIvanChen0 commented on Dec 22, 2015 Oxore commented on Mar 2, 2016 Btw, what about Spartan FPGA RTL firmware? Going to build all hardware by myself and can't find FPGA firmware here. heluozhijian commented on Mar 22, 2016 The same question: Will the microcontroller firmware be made open source? Kasijjuf commented on Aug 10, 2016 Still waiting for the firmware source. Hurry up and release the firmware source code or stop falsely claiming this project is open source. artob commented on Jan 30, 2018 Reacted by Justin Clift, Samuel Sarle, Jonathan Frederickson and Alex Gleason danuker commented on Jul 29, 2018 I'm not buying this hardware, for this very reason. MulanVR commented on Jul 30, 2018 Ryan, can you make the firmware public? It's in sensics repo. Razer had been also asking (for 2 years now) to make this public... Reacted by Justin Clift, Iliya Miroslavov Iliev and Arto Bendiken rpavlik commented on Aug 11, 2018 Sorry about the miscommunications - the asks hadn't made it down to my level, thought there might still be some approval required. (There might be some weird almost-useless include that I wasn't fully assured of the Apache 2-ness of IIRC, but those should be easy to replace if they exist.)
Have now opened the repo, at last - sorry this took so long, I am quite happy it finally is open though I wish it was earlier too: https://github.com/OSVR/OSVR-HDK-MCU-Firmware
I don't remember what the various non-master branches are - probably in-progress attempts at cleanup or refactoring, since parts of the code were fairly "legacy". However, I had been tagging releases and such in this specific repo for some time, so it should be fairly useful. Reacted by Justin Clift and Arto Bendiken Reacted by Arto Bendiken rpavlik commented on Aug 11, 2018 (And of course, @MulanVR , if there are any other Sensics repos that you'd like me to flip the "open-source" switch on [that aren't otherwise restricted by third-party NDAs], just let me know the repos and licenses! :D ) ShalokShalom commented on Nov 3, 2018 Is there still any plan to release the hardware also? godbyk commented on Nov 3, 2018 ShalokShalom commented on Nov 3, 2018 justinclift commented on Nov 3, 2018 Interesting question. Looking at the License in the GitHub repo, it's clearly not Open Source. Clause 3 includes this:
... you may not use, sell or distribute the MDK, Modules or Module Interface Technology nor the IPR contained therein for any purposes whatsoever ...
As a data point, clause 8 specifically excludes the source code from that license:
Any software, namely Source Code or Object Code that is made available on the OSVR Project is excluded from the terms of this License. Such software will be governed by separate terms and conditions set out elsewhere at www.osvr.com.
Not sure what the source code license is, as I didn't see anything obvious when checking the www.osvr.com website quickly. The license for the non-source-code pieces is very clear though. MulanVR commented on Nov 3, 2018 Any OSVR partner is allowed to produce and sell derivative work. The limitations are based on aknowledgement of being in fact derivative, and guidance on "powered by OSVR" logo plus marketing messaging if any. The logo guidance is available on the marketing section.
The goal here as always been to strengthen an open and horizontal ecosystem, which by the way it's entirely free and owned by the community, and allow everybody to accelerate their development to go focus on the hard problems of VR without wasting too much time on reinventing the wheel.
Go produce something awesome! ShalokShalom commented on Nov 4, 2018
Any OSVR partner is allowed to produce and sell derivative work. The limitations are based on aknowledgement of being in fact derivative, and guidance on "powered by OSVR" logo plus marketing messaging if any. The logo guidance is available on the marketing section.
That would be the case in BSD licences too. Why is OSVR not accepted as an open source license by Github and why is OSVR using an own license in the first place?
Thy rpavlik commented on Nov 4, 2018 It's not really worth it to debate this at this point - it's perhaps not the greatest license but it's only for the hardware part, and open source hardware licensing is still fairly immature in general compared to the situation for software (few permissive, vs copyleft-style, licenses, no overwhelming precedent, and a totally different legal background - copyright not really being as important for a finished product, compared to, e.g. patents), and was even more nebulous when the hardware files were released years ago. It's not really a custom license - it's basically the license for the (ill-fated) Google Project Ara modular smartphone effort. (And as such, is a bit more stringent than you might expect, due to plans to comply with rf regulatory frameworks,etc)
In any case it doesn't affect you if you're using the hardware, or even modifying the firmware: basically everything except the physical bits are Apache 2.0. (the tracking hardware and firmware is Apache2 as well, and the firmware for the headset is now also Apache2...) Even with any perceived flaws in the hardware plans license, the hardware is still more open than the vast majority of other HMDs out there, and these releases played an important part in setting standards and moving the industry forward. Reacted by ShalokShalom and Justin Clift Reacted by ShalokShalom ShalokShalom commented on Nov 4, 2018
it's perhaps not the greatest license but it's only for the hardware part
🙄
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|