Unofficial Mackie User Forums > DL1608/DL806/DL32R/ProDX Mixers

Alternative control and recording.

<< < (2/12) > >>

WK154:
Thanks for the info. If this is the case (need to be careful here) then Mackie is in violation of GNU GPL 2. Seems like the legal department is getting bored and needs some exercise. I dismissed it as a choice a while ago since they do have reference to GNU licensing for the multi-logon code. Ass-u-me strikes again. Could be why they've been so closed mouth about everything. The details of uCLinux for the hardware if used in the DL is here.   http://blackfin.uclinux.org/doku.php
for those interested.

metacom:
They aren't violating it. Their "modifications" dont deal with GPL stuff. They wrote their own application on a GPL platform. What's under the hood GPL wise is not relevant to the sound part of the device.
Quote from them a while ago

"We will provide the applicable GPL source code files via CD-ROM upon request for a nominal cost to cover media shipping and handling charges.
Please send me back your shipping address and I will reply with the total cost. If you are still interested, please allow 2-4 weeks for delivery."

The toolchain and build env are available for the board straight from AD. It is not required for Mackie to present them as an easy dl.
If they suddenly decided to open up the whole thing, they could.. but why would they do that....
I have a build rig that seems to work.. it is a fairly standard embedded build. The DSP code is. understandably, not open. That's what is tasking me right now!

Wynnd:
Welcome.  I'm interested in anything you're doing that has some level of success.  And if you create a commercial product, I'd be likely to purchase a license.

WK154:
As I understand it if the Blackfin is running uCLinux, no mater what the source of the code is, it's based on Linux. They need to comply with the GNU GPL. Receiving it from AD does not release them from that responsibility. As a mater of fact it's now back in the main Linux code base after a brief forking. Disclosure of that fact (using uClinux) is the minimum required, yes their add-ons can be proprietary. Linksys found that out the hard way. The statement in the manual refers to the log-on code not uCLinux unless they "forgot" to mention that. I'll ask them and see what they say. If on the other hand your implying that they used uCLinux as a development platform only then what your saying is correct but also lame on Mackie's part. In any case libraries still need to be considered.
Some reading required.
Licenses

Click any of these links for further information on Software Copyright, Software Licenses, Patent Licenses, Cryptographic Software, Support, External Links and your lack of Warranty.
This is off the AD site.   http://blackfin.uclinux.org/doku.php

WK154:
By "it" I believe you are referring to the DL hardware. Can you shed some light on the header info.

Image name:   bf518-2.6.36-ADI-2011R1-pre-main
Created:   Fri Jan 31 18:35:34 2014
Image type:   AVR32 Linux Kernel (gzip compressed)
Data size:   1075595 Bytes

I interpret this as an AD BF518 Blackfin part using Linux Kernel V2.6.36 in the ADI environment of uClinux 2011 R1 a pitifully outdated release barely supported by ADI.
The Image type AVR32 refers to Atmel's AVR32 which has nothing to do with a Blackfin AFAIK.
Some contradictions here.

Navigation

[0] Message Index

[#] Next page

[*] Previous page