[vtpad]

Following the fantastically successful software bounty started by xdpirate (for Win CE with touchscreen support), I'd like to start a bounty for Debian with touchscreen support.Thousands of sophisticated applications await an onscreen keyboard and finger stroke. And this time no fear of secret agents from Redmond saying nix. Just the satisfaction of knowing the world is ten digits more accessible. What could be better? Amaze your friends!I'll throw in $25 to start it off(As xdpirate created the last bounty, I'll quote his words here -- with OS name changed to protect the innocent...): This is a donation thread. Offer up any amount you'd be willing to pay to the person(s) who gets Debian fully working, with touchscreen drivers, and I'll list you here, with username and amount.Donor list:vtpad - 25 USDSlateDroid - 50 USDbobobobo1618 -10 USDTotal prize pool: =85 USDPM me (vtpad) or post in this thread with the amount you'd be willing to donate for a working Debian touchscreen build. If a team releases it, it will be donated to the leader of that team. If several people get it working at the same time, it will be split. If a single person performs this feat, they will collect all the donations. There is no minimum donation amount. You can donate everything from $1, so feel free to chip in with any amount!BREAKING NEWS!!!! Debian with touchscreen a reality on the Eken M001! Won by by jacob019. See Post #33

 

[zyntax]

http://bento-linux.org/wiki/vt8505/wm8505/debianIf you follow what it says on this page you should be able to run debian...

 

[Hopelessness]

Didn't work when I tried it, a bit of browsing suggests that the SD card is mounted as read only, so Debian wouldn't boot.

 

[projectgus]

The netbook steps don't work without a bit of tweaking. If you follow the steps on this page then you'll be able to run Debian on the M001:http://projectgus.com/2010/07/debian-on-the-eken-m001/You still won't have a functioning touchscreen, though. If the promised kernel source release from VIA comes, then this should be quite easy. As-is, I could get it to register one touch with coordinates but no subsequent touches had coordinates...

But I didn't try very hard. If people really want it, then I'll have another poke around.

 

[pierut]

i really want this.

 

[Mp4]

hello allOnce again Team SlateDroid would like to offer fifty dollars for a working touchscreen version of debian linux I personally think Projectgus will be the one to pull it off as I have read his blog. But if not good luck to all ThanksThe SlateDroid Team

 

[vtpad]

And if Debian wins the fickle finger of functionality, could Slack and Ubu be far behind?www.armedslack.org/http://wiki.ubuntu.com/ARM

 

[Mike]

Ubuntu lucid targets armv7 and higher only, See https://wiki.ubuntu.com/ARM/Thumb2.

Nice, 10,04 on M001, that would be great xD

 

[imayoda]

[quote name='Mike;21787]Nice' date=' 10,04 on M001, that would be great xD[/QUOTE'] ehm.. armv7 means cortex.. we can hope for debian as they still compile in armv4 aka oldest arm7 processors

 

[vtpad]

Though' date='[QUOTE'] Ubuntu jaunty targets the ARM EABI, with an expectation of minimum compliance with the ARMv5t instruction set.

Slack on the other hand:

Target Minimum CPU Starting with Slackware ARM 13.1, packages are compiled for the following minimum target:

• ARMv4t
• Little endian
• EABI (Version 4+)

This means that the user space will run on the majority of ARM devices on the market today. Unlike the x86, usually each type of ARM device requires a specific kernel. So even on an "unsupported" ARM device, the majority (if not all) Slackware ARM packages will run on the device, you will need a specific Linux kernel for your device. Please read this article for a great introduction to this topic. Debian also have a detailed discussion regarding "old" and "EABI"

But of course, I don't mean to distract here from the Debian effort.

 

[imayoda]

slack... too difficult and pure jaunty... too old and mainstream.. old mainstream is something evil ahahha debian... the way

 

[vtpad]

Back to theoriginal topic, is there anything to be learned about touchscreen drivers in the WinCE version now working on the Eken that could be of value to the Debian touchscreen effort?

 

[imayoda]

[quote name='vtpad;22196]Back to theoriginal topic' date=' is there anything to be learned about touchscreen drivers in the WinCE version now working on the Eken that could be of value to the Debian touchscreen effort?[/QUOTE'] i think not, cause driver approach is slightly different from win to linux kernel... too bad.. bushing should be more informed about this, as he is rebuilding the wm8xxx kernel.. i think

 

[fering]

I am far from a linux expert wouldn't the opensource driver from Wolfsonmciro help?http://opensource.wolfsonmicro.com/content/wm97xx-touchscreen

 

[projectgus]

I am far from a linux expert wouldn't the opensource driver from Wolfsonmciro help?

It would! Coincidentally, the WM97xx drivers from Wolfson are now part of the main Linux kernel tree - as of 2.6.29 (coincidentally the same version that the M001 is running.)However, for reasons unknown, VIA chose to reimplement WM9715 support in their own proprietary kernel modules - wm9715-api.ko and friends.So, a while ago I tried compiling the open source WM97xx modules and loading them in place of wm9715-api.ko. However, this doesn't work.The reason, best as I can tell, is that WM97xx is connected via an ac97 bus (same bus as the audio.) The standard Linux kernel has a module called ac97_bus that provides access to the bus, this is what the open source WM97xx drivers use. VIA, for whatever reason, seem to have their own ac97 support which is just called 'ac97'. The two are not compatible, and VIA's ac97 support is compiled in to the kernel so it can't be removed - preventing the open source ac97_bus for working.That's what I think is going on, anyhow.However, there is some good news. I had another quick look last night, and I think I might have identified two custom ioctls that are used to initialise VIA's WM97xx driver. When I have time (maybe over the weekend) I'll write a little program that calls the ioctls and we'll see if that's enough to get the touchscreen talking to us properly.If that doesn't work, if VIA release the promised kernel sources then we should be able to remove their proprietary ac97/WM9715 support entirely and roll it all into the existing open source modules.

 

[vtpad]

[quote name='imayoda;22197]. bushing should be more informed about this' date=' as he is rebuilding the wm8xxx kernel.. i think [IMG]http://www.slatedroid.com/public/style_emoticons/<#EMO_DIR#>/smiley.gif[/IMG][/QUOTE']Wow.......

 

[projectgus]

Actually there's at least two people I know of working on WM8505 kernel support:http://github.com/bushing/android_wm8505http://www.spinics.net/lists/arm-kernel/msg92934.htmlIt's early days, and IMHO it's a pretty uphill battle with the vague datasheets that exist. Good challenge, though.

 

[vtpad]

great admiration for all of you at your level of ability

 

[Mp4]

I agree with vtpad I am impressed everyday I am on this site. I wish i had 1/10 the skills of most of you.

 

[jacob019]

Any way to expose the hardware? I would be willing to write a user space driver for the x-server if I could get any kind of raw data from the hardware. How is android getting at the hardware anyway?