*Taps microphone* Is this thing on?
Hello? Hello? Hello? Ah yeah...
Anyway, coming to you from #openinkpot, here are the latest news!
Progress on OpenInkpot by the core members (dottedmag, and jekhor) has been quiet lately owing to their busy schedule.
But all is not quiet. The OpenInkpot/GSoc students have been hard at work investigating their chosen projects.
Unfortunately, due to the recent Sichuan earthquake, Wenjie has not gotten his Sony Reader yet. However, he is hard at work investigating support for various components that make up the hardware in the Linux system - which is essential to getting OpenInkpot to run on the Sony Reader.
Ondrej Herman - Bookeen Cybook port.
Ondrej has been able to find the serial port on the Cybook, and has managed to dump the original firmware for further analysis. However, he is in danger of being overtaken by a rival on the horizon - roxfan! (See below).
Alex Kerner - FBReader and EFL port.
Finally, but not least, LunohoD has managed to get FBReader ported to OpenInkpot already! However, it is lacking a GUI at the moment whilst he moves on to working on the EFL libraries. For those unfamiliar with EFL, it is basically a GUI manager - similar to Gnome, KDE, and Windows!
However, OpenInkpoter regular - roxfan, (a.k.a. igorsk on mobileread) has been hard at work on tweaking the Bookeen Cybook firmware to allow it to run on the Netronix EB-100 and the STAReBook, as well as other book readers that use the same hardware internally. This has provoked a fast and furious debate on the legalities of installing the Cybook firmware on other ebook reader, as well as the viral nature of the GPL.
Whilst this does not have any direct influence on OpenInkpot, this is a very welcome development, as it proves that once OpenInkpot is ready for the Bookeen Cybook platform, it can easily be ported to other ebook readers based on the same hardware.
If you have any questions or information you want to see on this blog, just come on in - the water's warm!
Till next time...
2008-06-04
2008-04-30
Slind: armel toolchain & mktpkg(1)
I just finished patching mktpkg and dpkg-cross Slind tools to make it possible to bootstrap GNU EABI (armel) toolchain for OpenInkpot from source.
Just get dpkg, dpkg-cross and toolchain-package from our Git repository, build them and install to the Slind chroot.
Then get *-source-*.deb from packages and install to the Slind chroot too (not sure why pkg-config-source is marked as i386).
Now simple 'mktpkg armel' should bootstrap toolchain from source.
Just get dpkg, dpkg-cross and toolchain-package from our Git repository, build them and install to the Slind chroot.
Then get *-source-*.deb from packages and install to the Slind chroot too (not sure why pkg-config-source is marked as i386).
Now simple 'mktpkg armel' should bootstrap toolchain from source.
2008-04-22
GSoC2008: accepted applications
GSoC 2008 is very promising for OpenInkpot: we've got three slots for a students, and three very interesting applications.
I'm happy to introduce our students and scope of ther GSoC work:
I also posted announcement in our mailing list: link.
I'm happy to introduce our students and scope of ther GSoC work:
- Alexander Egorov (aka LunohoD), porting FBReader to OI
- Ondřej Herman, Cybook Gen3 support
- Wenjie Zhang, Sony PRS-505 support
I also posted announcement in our mailing list: link.
2008-04-21
Welcome Slind.
I blogged about the problems with OI buildsystem. Some time ago we discussed it in IRC chat and xl0 suggested to take a second look at Slind.
After looking at sources and chatting with Slind developers we decided that it really worth to try it: Slind provides very controlled build environment by leveraging Debian build tools and extending them to the cross-build.
I bootstraped ARM EABI toolchain for Slind (not yet available - I had to add crude hack to dpkg to do it :), and soon will be publishing both patches back to the Slind and source/binary packages for the OpenInkpot.
Slind has it's own problems - it is very young and has much less userbase than OpenEmbedded, so we will have to package many pieces of software. Fortunately, it is as easy as taking Debian package, stripping all the unnecessary stuff and making it cross-compile (yeah, might not be as easy as it sounds :).
P.S.: GSoC information in next post.
After looking at sources and chatting with Slind developers we decided that it really worth to try it: Slind provides very controlled build environment by leveraging Debian build tools and extending them to the cross-build.
I bootstraped ARM EABI toolchain for Slind (not yet available - I had to add crude hack to dpkg to do it :), and soon will be publishing both patches back to the Slind and source/binary packages for the OpenInkpot.
Slind has it's own problems - it is very young and has much less userbase than OpenEmbedded, so we will have to package many pieces of software. Fortunately, it is as easy as taking Debian package, stripping all the unnecessary stuff and making it cross-compile (yeah, might not be as easy as it sounds :).
P.S.: GSoC information in next post.
2008-03-18
GSoC: we're in
"Congratulations!
Your organization "OpenInkpot" has been accepted in to the Google
Summer of Code(tm) 2008"
'nuff said.
Your organization "OpenInkpot" has been accepted in to the Google
Summer of Code(tm) 2008"
'nuff said.
2008-02-25
GSoC 2008 is coming
We're going to apply for Google Summer of Code this year: http://openinkpot.org/wiki/GSoC2008Participation
If you want to participate and have a brilliant idea which is not yet in our list - give us know, we'll add it.
If you want to participate and have a brilliant idea which is not yet in our list - give us know, we'll add it.
2008-02-23
full rebuild: it hurts
make build-package-openinkpot-image-lbook 5996.70s user 1412.30s system 156% cpu 1:18:39.16 total
It is too long for being practical. Probably I can come up with "make clean-target" or something like this, which cleans the packages built for the target machine, but keeps toolchain and host tools intact.
It is too long for being practical. Probably I can come up with "make clean-target" or something like this, which cleans the packages built for the target machine, but keeps toolchain and host tools intact.
Subscribe to:
Posts (Atom)
