Re: [U-Boot-Users] M-Systems Disk on Chip and U-boot
From what I've heard, the M-Systems code is NOT GPL.
I think you could only use U-Boot to load a (non-GPL) loader that uses the DoC. It this a correct assumption?
Wasn't there a section in the manual (U-Boot) about this, using U-Boot to load non-GPL applications [i.e. Whatever happened to Chapter 8]
Also, what's the status for "standalone applications", i.e the U-Boot resources mentioned in 5.12 (console I/O, memory allocation, ...)?
My two cents. Philip
On Thu, 02 Sep 2004 07:37:27 -0400, Herb Radford herbr@magma.ca wrote:
We're looking at using a DoC on our next product and I was wondering how the drivers (obviously supplied by M-Systems) are merged into U-Boot code?
Please be cautious with merging drivers supplied my M-Systems into U-Boot code. I have not seen thrie drivers, but I am not 100% sure they are GPL. Including non-GPL code into U-Boot even locally can be the cause of leagal headaches down the road. You may have to see if you can reverse engineer the driver, or base the U-Boot driver off of the kernel driver instead of using the vendor supplied driver. I would be a bit cautious with this as there is no loadable module interface loophole in U-Boot to help you avoid the GPL. Sorry I couldn't be more help technically but I had a few spare cents here to use. Thanks Brian
Dear Philip,
in message 1094135066.41372d1aaba03@webmail.cam.org you wrote:
I think you could only use U-Boot to load a (non-GPL) loader that uses the DoC. It this a correct assumption?
Yes. You can load any type of software, including completely proprietary stuff.
Wasn't there a section in the manual (U-Boot) about this, using U-Boot to load non-GPL applications [i.e. Whatever happened to Chapter 8]
Chapter 8 is a new chapter I intended to add about building and using Linux kernel modules. I just never found time to add any ral content.
This has nothing to do with U-Boot.
Also, what's the status for "standalone applications", i.e the U-Boot resources mentioned in 5.12 (console I/O, memory allocation, ...)?
What do you mean what is the status? It's a standard feature like TFTP download or serial console support... It has always been there, and always will be.
Best regards,
Wolfgang Denk
Quoting Wolfgang Denk wd@denx.de:
Also, what's the status for "standalone applications", i.e the U-Boot
resources
mentioned in 5.12 (console I/O, memory allocation, ...)?
What do you mean what is the status? It's a standard feature like TFTP download or serial console support... It has always been there, and always will be.
Sorry for the ambiguty.
Can a "standalone application" be non-GPL? Are the u-boot resources: console I/O, memory allocation, viewed as LGPL like versions of libc?
Philip
In message 1094151111.41376bc7a4ed5@webmail.cam.org you wrote:
Can a "standalone application" be non-GPL? Are the u-boot resources: console
Yes, this has always been one of the intentions (not the major one, but one of them).
I/O, memory allocation, viewed as LGPL like versions of libc?
Good question. I have to admit that I never thought of that. Yes, I think so.
Is there anyone here who is fluent enough with such legal stuff to comment?
Best regards,
Wolfgang Denk
participants (2)
-
philipv＠cam.org -
Wolfgang Denk