View Single Post
Old 06-29-2015, 06:02 PM   #13
fastrobot
Connoisseur
fastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to beholdfastrobot is a marvel to behold
 
Posts: 53
Karma: 11844
Join Date: Jun 2014
Location: All over the place...
Device: KOBO AuraHD and GLO
Quote:
Originally Posted by PeterT View Post
I've been using the telnet for a long long time
I ended up writing a telnet replacement program based on one I had for my Sony reader because my attempts to follow instructions for enabling Telnet for Kobo on various threads I found on MRforums didn't work for me; eg: busybox for the AuraHD didn't have the telnet server or ftp compiled in when I first got it.

I take it, this telnet server you're talking about is part of nickel -- or am I wrong, and some releases of the firmware support Telnet as part of busybox, and sometimes doesn't ? Or does the ability to enable Telnet depend on which kind of Kobo you own ?

This kind of inconsistency is irritating.... as it's very time consuming to sort out....

I had to give my kids the kobo Glo's I had to experiment with to do their book reading with this week, and that's with the system still locking up every so often if they don't press a key. eg: I ran out of time to find and fix the bug.

On the other hand, my AuraHD has been running the switch mode framebuffer without problems for two days now, no lockups.

So -- I'm buying a third KoboGlo as a spare to do experiments on. But It'll likely be a week before I get it in the mail...


Question: Do you know if the Glo's ARM processor has hardware floating point, or is it somehow different than the AuraHD's processor which might trip up a compiler?

I was wondering if that was different between the Glo and the AuraHD, and might be causing the failures I'm seeing because Kobo's developer tool package has two different gcc cross compilers; and I installed both, they are executed with;

arm-linux-gnueabihf-gcc and arm-none-linux-gnueabi-gcc
for linaro and code sourcery compiler packages.

The one with the 'hf' abi, I think, is a compiler supporting hardware floating point instructions, and that compiler is set up to compile user space applications that link to the standard c libraries. eg: glibc. etc.

But -- The other compiler, is the one I assumed the linux kernel was compiled with; since the linux kernel can do floating point emulation and often doesn't need the standard C libraries.

Am I mistaken ?

Should I have compiled the Kobo Glo's kernel module using the Code sourcery version of the complier instead of the linaro version ?

Last edited by fastrobot; 06-29-2015 at 11:16 PM.
fastrobot is offline   Reply With Quote