Boox (M92) developer community?

[Booxtor]

(also posted in other thread)

Hi,
Could you please check this:
https://github.com/onyx-intl/public_kernel

It was recently published and I hope it is the stuff what you are missing.

If you think it is still incomplete please infom me.

Thank you for your tremendous work!!!


UPD: Oops! Someone did it already before I did Just discovered his post.

[tuxor]

I wrote an article about building software for our M92 using a scratchbox2 environment: https://wiki.mobileread.com/wiki/Boox...th_Scratchbox2

Please feel free to place a link to this article in other wiki articles related to M92 and/or software development.

[Booxtor]

Originally Posted by tuxor

I wrote an article about building software for our M92 using a scratchbox2 environment: https://wiki.mobileread.com/wiki/Boox...th_Scratchbox2

Please feel free to place a link to this article in other wiki articles related to M92 and/or software development.

Good job!

[tuxor]

With today's update of scratchbox2 to version 2.3.57, there are no major bugs any more. Setting up your scratchbox2 environment is really straight forward now. I updated my wiki article according to this and added a link to the pointers at the end of article M92 software development

[tuxor]

Now that we have the kernel sources, was somebody able to compile the kernel module necessary for USB host capabilities (using something like this: http://www.amazon.com/Micro-USB-OTG-...07379&sr=1-4)? I would love to be able to write text with an USB keyboard, like this one: http://www.amazon.co.uk/Hama-Slimlin.../dp/B000VRLLFU or this one: http://www.amazon.co.uk/Flexible-Fol...6507591&sr=1-1

Unfortunately my knowledge about compiling kernel modules is sparse... Would be cool to have a short introductory article in the wiki

[rkomar]

Originally Posted by tuxor

Now that we have the kernel sources, was somebody able to compile the kernel module necessary for USB host capabilities...

You would also need USB host hardware on the device, as well. Most readers have client hardware, so that they show up as UMS devices when connected to computers. Does the M92 have host hardware?

[tuxor]

That a device shows up as UMS doesn't mean anything. The M92 can show up as serial console or UMS simply depending on which kernel module is loaded when connected.

[kodomo]

Originally Posted by rkomar

You would also need USB host hardware on the device, as well. Most readers have client hardware, so that they show up as UMS devices when connected to computers. Does the M92 have host hardware?

The loaded module's
arcotg_utc
I'm not sure whether there are non-hostmode compatible devices driven by this module, but it leaves hope for host mode suport.

I'm not sure we can go all the way to full OTG support, but I hope we'll get to the point of manual/scripted switching.

Cheers.

P.S.: I don't think I'll get there this week, but having at least a look at this is on my todo-list... anyone interested in joining me in this? I hope/think I'll find a bit of time mid of next week, when I have a really usable internet connection again

[rkomar]

Originally Posted by kodomo

The loaded module's
arcotg_utc
I'm not sure whether there are non-hostmode compatible devices driven by this module, but it leaves hope for host mode suport.

I'm not sure we can go all the way to full OTG support, but I hope we'll get to the point of manual/scripted switching.

Cheers.

Interesting. This is the first I've heard of OTG. I wish you every success.

[kodomo]

Originally Posted by tuxor

Yes, and I already tested that module. It's working perfectly fine, but maybe you need shared sqlite libs (libsqlite3.so).

(Context was: running peter-x's annotation export on the M92)

Indeed - one needed the shared libraries - they were easy to generate...
...now it's complaining about a missing python module (QtSvg)

Could you please add it to your python package?

Cheers!

[tuxor]

Originally Posted by kodomo

(Context was: running peter-x's annotation export on the M92)

Indeed - one needed the shared libraries - they were easy to generate...
...now it's complaining about a missing python module (QtSvg)

Could you please add it to your python package?

No way. I can't add any parts of Qt that are not provided with the version of Qt used by Onyx and provided with their devices. And QtSvg is not part of the Onyx Qt libs.

[kodomo]

Originally Posted by tuxor

No way. I can't add any parts of Qt that are not provided with the version of Qt used by Onyx and provided with their devices. And QtSvg is not part of the Onyx Qt libs.

ok - ic... this puts an end to this mini project...

As the color scribbles in pdf mini project is done, the next one would be to get a working kernel devel environment... did anyone manage to compile the kernel in the repository, so far? (possibly even using build.sh?)
Did anyone try?

Cheers.

[kodomo]

Originally Posted by rkomar

Interesting. This is the first I've heard of OTG. I wish you every success.

thx - chances are increasing:
- the default M92 kernel configuration in the repository includes EHCI support with an extension for a Freescale USB controller (+ "support for the USB OTG port in HS/FS Host mode.")

On the other side, kexec is not enabled, which will make it somewhat risky to test kernels with new options compiled into it (e.g., the devpts support needed for ssh, USB runtime power management, or USB HID support :-| )... does someone feel lucky enough or is someone aware of a JTAG interface on the M92 board (just in case)?

Anyway... the latter will just become an issue once we have a compiling kernel...

btw.: Does someone know which digitizer tablet model is built into the M92? The 'touchscreen' input device category is selected, but no driver is selected... thus it looks like the device driver were not published.

Cheers.

[FDD]

Originally Posted by kodomo

btw.: Does someone know which digitizer tablet model is built into the M92? The 'touchscreen' input device category is selected, but no driver is selected... thus it looks like the device driver were not published.

Hello Komodo, the digitizer is based on the HW0818 chip from Hanwang. I've been trying to get technical documentation, but the person in charge of this chip never replied to my emails (Mr Scott Zhang <zhangyanhui At hanwang.com.cn> forwarded me to Mrs Zeng (XianJie Zeng) <zengxianjie At hanwang.com.cn>, but I never heard anything back from her).

However the digitizer is connected to the CPU via a serial interface, and all the processing happens in user space, via tslib, "hanvon.c" driver. There is no kernel's input device layer involved, that should explain why there is nothing selected there.

Ciao!

[alphabee]

Hi tuxor, the link seems unavailable now, can you post it again?