Castle USB, ethernet derived from BSDBy Chris Williams. Published: 3rd Jul 2004, 21:26:02 | Permalink | Printable
Powered by open sourceIt's been revealed that Castle's USB and Iyonix ethernet drivers include portions of code originally from NetBSD, FreeBSD and Intel.
Specifically, the Castle USB stack contains copyrighted material from the NetBSD project, the USB mass storage driver includes copyrighted material from FreeBSD and the EtherK driver is derived from copyrighted code from Intel. All the aforementioned code is licensed under the classic BSD licence, which requires redistributions to include appropriate copyright attributions among other things. Unlike the GPL, you don't have to make source code available under the BSD licence.
Today, Castle issued to Iyonix users a documentation pack which included the necessary copyright attributions and other text for the above drivers, as directed by the conditions of the BSD licence. So unlike their previous tussle with open source software, Castle are seemingly playing this one by the book. A note in the documentation release reads, "This update groups all the related documentation, disclaimers and licence conditions in a consistent location for ease of reference. We have re-supplied the relevant documentation in updated form to reflect the current state of play."
"The licence style of BSD derivatives permits their use," Castle's John Ballance commented this morning when we asked Castle if they see the BSDs as providing a route for improving RISC OS. He added, "Indeed, for a long time the [RISC OS] network stack has been based on (and attributed to) NetBSD."
On Friday, Iyonix users were issued beta release USB drivers, which (for the first time) sported an accompanying copyright attribution to NetBSD. A keen reader also spotted similarities between the EtherK module and Intel's gigabit ethernet driver, so we got in touch with Castle. The next day, the updated documentation was issued, which included copyright attributions for EtherK and the USB modules.
Of course, this isn't the first time RISC OS has used BSD derived code (for example, the network stack), and the liberal nature of the BSD licence permits code to be used in closed source commercial products with little disruption. However as the RISC OS platform continues to increasingly rely on open source software to further itself, it's interesting to see where developments are coming from.
Other open source software used by Castle
Previous: X-Ample woos RiScript
Next: Castle conference transcript online
DiscussionViewing unthreaded comments | View comments threaded by reply | Skip to the end
Please login before posting a comment. Use the form on the right to do so or create a free account.
Search the archives
Today's featured article
Of subnets and routers
Part two of IP networking and RISC OS
2 comments, latest by AMS on 7/9/04 8:11PM. Published: 7 Sep 2004
RISC OS South East show this Saturday
Plus Newcastle gossip and RISC OS Now splash
15 comments, latest by markee174 on 21/10/06 4:52PM. Published: 20 Oct 2006
News and media:
RISCOS Ltd •
RISC OS Open •
MW Software •
Advantage Six •
CJE Micros •
Liquid Silicon •
Chris Why's Acorn/RISC OS collection •
The Register •
The Inquirer •
Apple Insider •
BBC News •
Sky News •
Google News •