The more I read the less I know, which one..

[kacir]

Originally Posted by Ankh

Just open-sourcing the drivers is all that is needed. You want to flash your eReader to turn it into a, say, dedicated Sudoku machine? Fine. Why would Pocketbook care?

The first generation of PocketBooks, especially PB301 ran on generic hardware. We were told that PocketBook programmers (called Guys In Kiev (TM) here) are fiercely independent and are extremely proud of their work. It is very rare in the industry that programmers have any deciding power over software specification.

The programmers wanted to prevent people from flashing PocketBook software to other devices, such as Coolreader, CyBook and others. It is very difficult to provide you with access to the guts of the system without giving competition tools to copy your entire system (including key proprietary parts you have developed entirely in-house).

Look at Sony for example. They provided source codes for parts that use GPL software exactly to the letter of law. What can we do with those parts? NOTHING. We have no access to the system to make any use of that information. Firmware update gave hackers tools to hack the device, not code published as GPL requirement.

Sony devices use proprietary MontaVista Linux, PocketBook uses Embedded Debian.

[HarryT]

There are probably issues with making the whole of the firmware open source. I would guess that, for example, the drivers for the eInk display are proprietary. There's absolutely nothing in the GPL which requires that the released source code be "buildable".

[Ankh]

Originally Posted by kacir

The first generation of PocketBooks, especially PB301 ran on generic hardware. We were told that PocketBook programmers (called Guys In Kiev (TM) here) are fiercely independent and are extremely proud of their work. It is very rare in the industry that programmers have any deciding power over software specification.

The programmers wanted to prevent people from flashing PocketBook software to other devices, such as Coolreader, CyBook and others. It is very difficult to provide you with access to the guts of the system without giving competition tools to copy your entire system (including key proprietary parts you have developed entirely in-house).

Well... a generic hardware is pain in posterior, I am not certain how can one prevent (exclusively from software) dumping of the flash content and moving it to another machine.

But if the hardware is not generic, the proper way to open up what must be opened up under GPL is to provide complete code for u-boot, kernel (e-ink controller drivers too), busybox which can be built to show a simple "hello world" app on the screen. Replacement firmware, should you chose to not use their software.

Generic kernel configuration that has nothing to do with the firmware, partition scheme completely different than one used by Pocketbook... If the resulting image can be booted from the external usb stick or SD card, what else does the customer need?

Pocketbook is more than welcome to keep the app, firmware, encryption schemes and DRM nastiness as closed as they wish. One doesn't, really, need an access to shell, if you can boot the alternate image, right?

[Ankh]

Originally Posted by HarryT

I would guess that, for example, the drivers for the eInk display are proprietary.

That's an insanity of the party who is making the controller. Hardware vendors have a perfect model for open source, they are the ones who 100% know how to make money out of it. You need to buy their stuff to run that code.

Originally Posted by HarryT

There's absolutely nothing in the GPL which requires that the released source code be "buildable".

Yes, there is. GPL mandates giving a customer the complete access to any GPL-tagged code used on product, and any derived works. Since any GPL-protected entity can be compiled, the result can be compiled, as well. It is the missing pieces that prevent you from running your own software on hardware that you own.

[HarryT]

Originally Posted by Ankh

Yes, there is. GPL mandates giving a customer the complete access to any GPL-tagged code used on product, and any derived works. Since any GPL-protected entity can be compiled, the result can be compiled, as well. It is the missing pieces that prevent you from running your own software on hardware that you own.

You misunderstand me. Yes, all code that falls under the remit of the GPL has to be made available. My point was that not all code does have to fall under the remit of the GPL, and hence the system may not be buildable.

[Ankh]

Originally Posted by HarryT

You misunderstand me. Yes, all code that falls under the remit of the GPL has to be made available. My point was that not all code does have to fall under the remit of the GPL, and hence the system may not be buildable.

For embedded systems with Linux under the hood, accessible console (serial port) and the kernel source (GPL) is most frequently sufficient to build a basic load with kernel and busybox. Something that can boot kernel, print stuff on console, run a shell where you can login, then type "ls" and not much more. However crippled, that's still a "system".

[mclien]

Originally Posted by SmokeAndMirrors

I've been looking intently at the Pocketbook series as well.

I bought a PB 603 and really can't reccoment that (hope I find time to post a little revue in a while).

I currently find the MReader1 interessting. Maybe that's my next reader...

[paola]

Originally Posted by mclien

"status report" of the Pocketbooks

an update, Pocketbook have just released an updated version of the SDK (unfortunately, though, most of the time you've got to peruse the Russian language forum to find out about developments)

[mclien]

Originally Posted by mclien

(hope I find time to post a little revue in a while).

Here we go:
https://www.mobileread.com/forums/sho...45#post1830345