Some of the Cybook Gen 3 source code has been released by Bookeen:

Bookeen is pleased to make available to you for download an archive file of the ebook reader source code ("Source Code") corresponding to modified software packages used in the Cybook device.

Available here: http://www.bookeen.com/support/ebook-gpl.aspx.

Related: GPL violation? (http://www.mobileread.com/forums/showthread.php?t=21074)

That's a giant leap forward for humanity :D

Why would they do this?

Probably due to ongoing lawsuit from the SFLC and busybox copyright holders.

It is great that Bookeen is starting to take copyright more seriously.

Does this mean that Bookeen now is in compliance with their licenses or are we still missing something?

kernel sources seem to be full.

I did not check whether userspace contains anything GPL-licensed beside busybox.

Why would they do this? They were supposed to do this for all the open source code they use when the device was released. Some vendors won't do this without the threat of a lawsuit. This does not generally happen with Linux, but the authors of BusyBox are more active in protecting their copyright and have actually sued several times. So far as I know, all these suits have been settled before trial in favour of BusyBox - since this isn't a grey area of copyright law and the infringer's would certainly loose at trial.

kernel sources seem to be full.

I did not check whether userspace contains anything GPL-licensed beside busybox.

Did you not check that the pfd reader included gpl:ed code and this is in user space?

Did you not check that the pfd reader included gpl:ed code and this is in user space?

Ah, I remember now. But someone will need to check it again - they may have replaced GPLed libraries in newer firmware with alternatives. Maybe roxfan?

As kernel is everything OpenInkpot needs, I don't know will anybody from the project spend time checking it.

The software does as far as I can see still not mention that it contains GPLed code (build 796). So Bookeen is still violating the terms. Why? Are they stupid or ignorant?

At least they're working on it - don't be too harsh.

Well this has already been discussed in length in the other thread (http://www.mobileread.com/forums/showthread.php?t=21074). IMHO Bookeen's behaviour in this case can only be explained by stupidity or ignorance.

As it turned out, Bookeen "forgot" to add eink driver source code (and several other files) to zip file. As this code is compiled into the kernel, not as module, this is a serious violation.

As it turned out, Bookeen "forgot" to add eink driver source code (and several other files) to zip file. As this code is compiled into the kernel, not as module, this is a serious violation.

Did the kernel compile so they just distributed a general kernel source or had they removed just the source files and they distributed the modified kernel source?

The usual people complaining about blatant copyright violations all around the forum are strangely silent in this case...

There are lots of changes in kernel beside removed files, and provided source can't be compiled. Jekhor and me are working on finding out what exactly has been omitted (Bookeen did not provide pointers for the toolchain (another problem!), and this makes situation harder).

> The usual people complaining about blatant copyright violations all around the forum are strangely silent in this case...

Talk is cheap, copyright-related work is hard :)