mini210S and ubuntu image

Hi all, I am currently trying to get the mini210 ubuntu image working for
the mini210S board with a H43 4.3" resistive touchscreen.

There seem to be a few issues, some I think I can overcome, others will
need some answers from FriendlyArm.  If anyone has any solutions or ideas
about the following issues it would be great if you could post them :-)

1. I cannot get the touchscreen to work, I think I'm missing a plugin and
some conf files?  I've set lcd=H43 in the commandline for superboot, do I
need ctp=?

2. HDMI does not work at all, other s5pv210 features are missing.  

I've partially tracked this down to the mini210_ubuntu_defconfig in the
kernel sources provided with the ubuntu images.  If you do a diff between
mini210_ubuntu_defconfig and mini210_linux_defconfig, you will see that all
of the hdmi-hpd, cec, fimg-2d, MFC, jpeg etc. items are all not
configured/missing.

If I try and use the mini210_linux_defconfig, the resulting kernel fails to
 boot, it uncompresses and just hangs.

If I use the mini210_ubuntu_defconfig and just enable 'Samsung Multimedia
Devices' in the menuconfig, the kernel builds and loads, hdmi-hpd is then
present and aware of devices attached to it but fails to work because of
missing software, namely:
/bin/hdmi-service

looking at the qtopia-linux rootfs image, It appears that 'hdmi-service
autostart' is run at startup in /etc/init.d/rcS.

I've tried using hdmi-service from the qtopia-linux rootfs image but it
fails to run, with the following error:

hdmi-service autostart
-bash: /bin/hdmi-service: No such file or directory

I think we need FriendlyArm to supply the missing binaries and associated
lib files:
hdmi-service, libfimc.so, libedid.so, libddc.so, libcec.so

And any others files that might be missing.

Regards,
Reggie.

Hi Reggie,

I'm also interested in this work. I'm actually trying to get touchscreen
driver working, but FriendlyARM seems not to be disposed to release the
source code.

Another idea coming to my mind:

PowerVR SGX540 is not used only in mini210, but also in some tablets or in
pandaboard for example. Maybe it is possible to get ideas or source code
from other S5PV210 devices? They probably don't use hdmi-service and manage
to send video over HDMI output.

Hi screwface, I think the hdmi-service app. is linked to a qt app called
'hdmi' in the qtopia-linux image.  That's a good idea to look 

I believe that hdmi app talks to the hdmi-service which in turn talks to
the hdmi driver.

There are other issues with the ubuntu image, I'm working through them
slowly :)

1. There is no root password, the default 'fa' account isn't even part of
sudoers, that's easily fixed though, edit /etc/sudoers on a host PC.

2. It's using unity desktop, not really much use on a 4.3" screen, so I've
put gnome2 back on there, which makes it slightly better as the top/bottom
panels now fit on screen but it still seems to be using a much bigger
desktop area when you maximise an app.

3. You can't access networking as a normal user, you either have to sudo or
be root, the mini210_ubuntu_defconfig still has some android stuff set,
namely CONFIG_PARANOID_ANDROID_NETWORK, this is great for android,
pointless for ubuntu, only way to fix this is to deselect that config
option and recompile the kernel.

whoops, should've finished that 2nd sentence there :D

That's a good idea to look around for other s5pv210 targets.

I've been doing more investigation into the ubuntu image and have managed
to build my own armhf ubuntu core image using the 3.0.8 kernel and the core
rootfs downloaded from ubuntu, the touchscreen now seems to be working
(still don't have a tslib plugin though and probably needs some X stuff
too).

It seems that there are still some android settings left in the
mini210_linux_defconfig, I get a hung task in the cpu freq driver, which I
believe is something to do with cpu throttling in android?

I discovered that it's also giving the lcd a 'virtual size' for each of the
framebuffers as 480x816, I think this is why the top/bottom panels are the
correct size for the screen but when maximising windows it never fits.

I think possibly/probably that all of the samsung multimedia stuff (inc.
hdmi) is controlled by an external app no matter what platform it is but it
would certainly be useful to see how other people do things.

I gave up with FriendlyARM ubuntu distribution. I found it a bit slow and
was unable to fix the screen dimensions issues (I have a S700 screen). So I
switched to a Debian distro with LXDE as windows manager. Now I'm trying to
get the capacitive touchscreen working. I think I have to compile tslib as
I don't know how to make the debian tslib package work.

I've seen there were some Android stuffs in the linux_defconfig file and
some other annoying things. For example, when the board is idle, I often
get a debug message. It is possible to remove it by echo 1 in the
mentionned file. I think it is for debug purposes. But when I want to
remove all debug options from the kernel configuration, I get a compilation
error.
I think the best thing to do would be creating a BSP from a recent vanilla
kernel like is was done for mini2440, taking ideas and code from
FriendlyARM kernel, but I'm too newbie to do that alone.

Regarding the HDMI output, I have to buy the correct cable to make some
tests and then share with you my findings.

To fix that idle message, you need to edit the cpu settings:
https://github.com/lilstevie/linux_kernel_TF101/commit/41efceb3b782488e1...

set the governer to update and untick the CONFIG_CPU_FREQ_GOV_INTERACTIVE
setting in menuconfig.

For the touchscreen, as far as I know, it needs the tslib plugin, same as
me.  You will probably need a recompiled kernel too that has the
goodix/ft5x0x drivers selected.

I also added lxde for my window manager, it's much quicker than the unity
desktop, I had also tried rolling it back to gnome2.

The problem is there is no driver in the provided kernel. I have asked
friendlyarm, and the onlyone answer I got is "The linux kernel already has
the support for capacitive LCDs you need to make the QT system support
capacitive LCDs."

I noticed that the drivers were compiled as modules in original BSP. If we
look in the provided kernel configuration files, drivers are set to be
builtin the kernel

there *are* drivers of some sort in the kernel for the cap touchscreens
afaik.  They are the goodix and ft5x0x drivers.  However, I *think* we
still need to get the tslib plugin from friendlyarm.  Or ask them how we
configure it correctly.

at the moment, I can do:
cat /dev/touchscreen-1Wire
and touch the screen and see output, so the driver for the h43 resisitve
touch screen is there but it's not hooked into anything like qt because it
needs the tslib plugin as well.

Not sure what else is needed for the cap sense boards.

btw, have you seen this?

http://www.friendlyarm.net/forum/topic/4427

Goodix is an i2c device, not 1-wire. The driver is somehow broken - it
loads into kernel, but doesn't talk to device. If FriendlyARM's driver
works the same way as the other ones - data should be available through
/dev/input/event[0-9].

I confirm that using FriendlyARM driver (modprobe goodix_touch) creates an
/dev/input/eventX file which outputs values when touching the screen. This
is ok with FA's already compiled driver. But I'm unable to recompile the
kernel and get such a file myself, or at least a kernel able to get values
through a built-in driver.
I have also thought about the tslib plugin but have not enough time to
search deeper for the moment

I can recompile a kernel and get data from the H43 touchscreen, what's
lacking is the plugin for tslib which any app. that uses touch will
probably use.  Either way, whatever we need friendlyarm are the only place
to get it unless we use the output and build our own.

I guess you can compile the driver with touchscreen driver because you use
a resistive one, and it should use the samsung driver for S5PV210 which
should be already documented in the kernel. In my case, there is nothing
about goodix I2C capacitive touchscreen, or I missed something.

If I make the parallel with mini2440, the resistive touchscreen was part of
the kernel, there was no patch needed. Also, tslib worked natively and no
special plugin was required to get the touchscreen working.

Oh, or I'm wrong, I missed this one-wire touchscreen with a specific
driver. But I assume it is the same as mini6410. Maybe looking in mini6410
DVD image would provide some sources? If there is a Qtopia image, there is
probably the needed plugin? There is a driver on the FTP website, but I
don't remember about tslib plugin

If not, I don't know how to get FriendlyARM's help. Their answers are the
shortest possible, and with less information. Another idea is looking at
the chinese forums with the help of google translate. They are very active.
But this will take time.

It seems there is new 2012-10-27 Tiny210v2 iso from FriendlyARM with 3.0.8
kernel and capacitive touchscreen support for Linux. I don't know how to
download it, it's available only via chineese forum:
http://www.arm9home.net/read.php?tid-24305.html

Hi Tomasz, you can download the 3.0.8 kernel from the ftp site (check the
FA downloads page on this site!) it's in the /tmp folder.  It's called
'Android4_Kernel-3.0.8_images-20120907.rar', I don't have a cap sense
screen to test but it does include the goodix/ft5x0x drivers as far as I
can tell.

I'm pretty sure we'll figure this all out soon enough!!

Could you point the folder in which the drivers are Reggie? Because they
appear in menuconfig, but I do not find the *.c files. You can look at the
Makefile in \drivers\input\touchscreen and search for the mentionned file
but for me, it is not present.

Tomasz, try this link. I don't know if it works as it is blocked by my
work's firewall. It was a bit painful to get it: I had to register on the
chinese website and answer the to the tread to get the link visible.

http://dl2.t15.sendfile.vip.xunlei.com:8000/Tiny210V2-20121027.iso?key=1...

Reggie,

Maybe this can be useful for you?

http://translate.googleusercontent.com/translate_c?depth=1&hl=fr&...

Screwface,
Sorry I can't download your Tiny210V2-20121027.iso image (403 Forbidden).

However, I used Reggy's hint and managed to make capacitive touchscreen
working with dvd-images I already had.

- I unpacked image source
Tiny210-20120913.iso/Android/linux-3.0.8-20120912.tgz
- I built kernel using mini210_linux_defconfig as base for kernel
configuration
- it doesn't matter if you check Yes or Module for goodix touchscreen
driver. It won't compile because there is no source code for this driver.
- I copied binary module file goodix_touch.ko from
Android/rootfs_android4.0.3-20120912.tar.gz/system/lib/modules/3.0.8-FriendlyARM

to my running system
- modprobe goodix_touch was successful:
[  147.433732] input: goodix_ts_80x as /devices/virtual/input/input4
[  147.552300] gt80x-ts 2-0055: GT80X Version:
GT801_1R08_2011121501_Goodix_Tech
- hexdump /dev/input/event4 dumps data when screen is being pressed
- goodix_touch is factory calibrated - it returns data in screen
coordinations and doesn't need user calibration

Screwface, thanks for the link, I actually found it earlier on today, I
haven't compiled it yet but I'm sure it will work just fine :)

As for the goodix/ft5x0x c files, they don't appear to exist :(  I've
double checked that they weren't in the original archive and get 'cleaned'
when we do a make etc, so it seems someone made a mistake there!!

I think you can download the goodix_touch.c file from here 
https://bitbucket.org/paulobrien/android_kernel_andypad/src/4c6b4f4c48d1...

as for anyone that wants the focaltech drivers, you can try the 5x0x
drivers on the bitbucket link, or see if this ft5x06_ts.c driver works for
you?



Thanks for the links to the arm9 site, I also joined that earlier today,
I'm in the middle of downloading the dvd but it's still got at least 10
hours to go!!

Tomasz, glad to see you got it working :)

My apologies for not noticing the complete lack of driver, the kernel
didn't ever complain when it was being compiled for me!!

Hi Reggie,

Glad you found the link by yourself, and thank you for having a look at the
cap touchscreen as you are not very interested in it. Sorry to have
insisted so much, but I wondered if I was wrong and missed the driver. So
happy to see that your conclusion is the same as mine.
I have to explore the goodix_touch.c way, I planned to do this before, but
due to time lack, I hoped to find a "plug and play" solution.
By the way, I'm not sure to know how should I proceed: do you think just
putting the goodix_touch.c file in the driver/input/touchscreen directory
will be enough? I'm at work so without the kernel files. Maybe some
goodix_touch.h is missing also, and maybe some makefile tweaking will be
required. I'll try to look at this asap.

We're on the right way to get these 210 touchscreens working!

Hi Screwface, I'm glad you insisted :)  You should be able to put
goodix_touch.c into driver/input/touchscreen, there are no promises that it
will work but we can at least start there :)  goodix_touch.h does exist
though!!

I found some more information about the hdmi but I'm still not sure how it
all works, v4l-utils needs to be installed and 'v4l2-ctl --list-dv-presets'
should show all of the available video modes for tvout/hdmi.  If I try and
set a mode it segfaults or does nothing or gives me a permission denied
error.  I believe the tv out stuff is on /dev/video14 but the v4l2-ctl
information that I found suggests that it should be to /dev/video0 but that
segfaults.

Where did you find v4l-utils and v4l2-ctl ? In the ubuntu image?
Did you manage to get the whole new DVD file image? I'm not able to
download it completely. Downloading gets stopped after several time.
Did you manage to solve this virtual screen size? I think I have the same
problem with Debian. Must be due to the kernel?

I'll buy a hdmi cable soon and try to investigate with you on this item

I managed to download Tiny210V2-20121027.iso. The situation haven't changed
too much. You can recompile 3.0.8 kernel, but you still need binary modules
for touchscreen and audio - for example from
"rootfs/rootfs_qtopia_qt4-20121027.tar.gz"

There is no Ubuntu on this iso.

If you need v4l-utils - you can always download armel package from debian
site:
http://packages.debian.org/wheezy/armel/v4l-utils/download
Then you extract necessary files on PC and copy them to target machine.

Hi Tomasz, I forgot to mention that I had also finished my download
yesterday and as you, no goodix/focaltech touch drivers exist in the image.

I built my own ubuntu armhf from scratch, it's simple enough and it's got
apt already installed, so installing v4l-utils is simple enough :)  It just
doesn't do what I expected it to.

to sort out the screensize (so that at least the desktop bars fit the
screen) you need to put lcd=H43 in the Linux-CommandLine line in
FriendlyARM.ini, obviously if you have a different screen the put that
value in instead of H43!!

Basically the screen is supposed to default to 800x480 if you don't put the
lcd= bit in the commandline.


Screwface, I managed to get the download done by installing 'thunder', the
chinese download manager, it was incredibly slow, took about 24hours in
total, with speeds ranging from 0KB/s-90KB/s :(

The touch drivers for the qtopia rootfs won't work with my self-made ubuntu
rootfs as it's armhf and they're armel.

Hi Reggie, Tomasz

I managed to download the new DVD image and like you Tomasz, no evolution.
The kernel still doesn't contain any driver for touchscreen which as I
expected. But I thought using the pre-built images would help.
Using the provided linux kernel makes my board looping infinitely sending
this message : "s5p-nand: ECC uncorrectable error detected".
I tried to use the previous DVD release kernel with the new rootfs and then
touchscreen still doesn't work: during init I get these messages 

[   27.432144] s3c_idma_preallocate_buffer:  VA-e08c0000  PA-C0000000 
163840byt
es
[   27.432763] asoc: WM8960 <-> s5pc1xx-i2s mapping ok

[   27.626976] ft5x06_ts: Unknown symbol mini210_get_ctp (err 0)
[   27.642401] goodix_touch: Unknown symbol mini210_get_ctp (err 0)
[   27.870899]
[   27.870905] rtw driver version=v3.3.2_3192.20120103
[   27.870964] ##########rtw_suspend_lock_init ###########
[   27.875955] usbcore: registered new interface driver rtl8192cu

The mini210_get_ctp seems to be the blocking error. Do you have an idea?

The newest image is for MLC Nand Flash. I'm not sure if it will work. I ran
it by unpacking rootfs_qtopia_qt4-20121027.tar.gz and rebuilding the image
using mkyaffs2image-128M tool. It worked fine with provided 3.0.8 kernel.

I saw mini210_get_ctp symbol somewhere in kernel sources. It is inside
arch/arm/mach-s5pv210/mini210-lcds.c file.

These kernel sources are full of traps and black holes in documentation.
I lost a day trying to activate sound card. I hope these commands will help
the others:

#binary FA closed-source modules
modprobe snd-soc-wm8960
modprobe snd-soc-mini210-wm8960
#magic FA util from DVD
fa_codec_ctrl mini210
#broken mixer initialization, OSS aumix won't work without these lines
amixer -q set "Right Output Mixer PCM" unmute
amixer -q set "Left Output Mixer PCM" unmute

Tomasz, great work on getting the audio working!!

The newest image being for MLC nand shouldn't make a difference, there is
an initrd/cpio in the kernel sources that should be able to handle booting
from SD, you just need to create an ext3 image (dd a file, then mkfs.ext3
it, then mount it and untar the ubuntu image to it), once you've created
the ext3 image you can put it in your /images/Linux folder and use the run
method to boot the rootfs via the image file.

I wonder what has changed between 2.6.35 and 3.0.8 to break the nand
driver?  I wonder if it's because the ubuntu zImages might not be compiled
for the 210S but the 210?

Also, there are a lot of orphaned android options in the ubuntu kernel, I
wonder how many more there are that we haven't found yet?

Here is a rough translation of the ubuntu readme file that is on the ftp
server (I got google to translate it last night), it mentions about the
audio, it also mentions about the touchscreen not being supported and in
section 4c, it also mentions about the multimedia stuff being turned off:

README

---------------------------------------------------------------------------
1. File description 1. File description

a) arm-linux-gcc-4.5.1-v6-vfp-20120301.tgz a)
arm-linux-gcc-4.5.1-v6-vfp-20120301.tgz
   Toolchain for building kernel zImage Toolchain for building kernel
zImage

b) gcc-linaro-arm-linux-gnueabihf-2012.05-20120523_linux.tar.bz2
   Toolchain for building applications
   Note: DON'T use it to compile kernel Note: DON'T use it to compile
kernel

c) linux-2.6.35.7-20120629.tgz
   Kernel source code, includes kernel config (mini210_ubuntu_defconfig)
for Ubuntu

d) ubuntu-desktop-1204_20120628.tgz
   Ubuntu desktop rootfs

e) ubuntu-server-1204_20120628.tgz
   Ubuntu server rootfs

f) zImage e) zImage
   Prebuild kernel zImage for ubuntu


---------------------------------------------------------------------------
2. Ubuntu desktop Descriptions

a) Login ordinary user name fa, the password is fa root user password has
been modified to fa

b) Desktop automatically log fa
   Modify /etc/lightdm/lightdm.conf automatic sign-on support to increase

c) support USB mouse and keyboard, and does not support touch screen

d) Increase /etc/init/s3c2410_serial0.conf, the serial port can log

e) Increase /sbin/fa_codec_init and /etc/init/fa_codec_ctrl.conf used to
initialize audio
   Normal playback wav files, mp3 files prompted the need to arrange for
plug

f) Increase the kernel modules and the firmware

g) Ethernet and SDIO Wi-Fi can be connected to the serial port can ping,
but Firefox is always unable to connect, reason unknown
   If you are using Wi-Fi, it is recommended not to insert the Ethernet
cable, you may also need to restart

h) Serial login and su to root, apt normal use


---------------------------------------------------------------------------
3. Ubuntu server brief

a) Login ordinary user name fa, the password is fa root user password has
been modified to fa

b) Support USB mouse and keyboard, and does not support touch screen

c) Increase / etc/init/s3c2410_serial0.conf, the serial port can log

d) Increase / sbin / fa_codec_init and / etc / init / fa_codec_ctrl.conf
used to initialize audio

e) install alsa support
   Serial login can use the command aplay normal play wav file

f) Increase the kernel modules and the firmware

g) Ethernet connection, serial port can ping
   SDIO Wi-Fi can be identified to the equipment, but need further package
installed and configured to use

h) Serial login and su to root, apt normal use

i) X window, the display can be used with the USB keyboard for the console
login screen


---------------------------------------------------------------------------
4. Build kernel

a) Install the arm-linux-gcc-4.5.1-v6-vfp-20120301.tgz and set the
environment variable PATH

b) unpacked linux-2.6.35.7-20120629.tgz and enter the appropriate directory

c) cp mini210_ubuntu_defconfig. config
   The kernel configuration prohibits multimedia, such as MFC, FIMC, in
order to save memory

d) make


---------------------------------------------------------------------------
5. Install Ubuntu rootfs to SD card
   The ext4 partition SD card read / write performance than nand flash,
ubuntu rootfs installed to the SD card, the steps are as follows:

a) prepare a 4G or SDHC card

b) in PC Windows SD-Flasher.exe is the Scan, ReLayout again Fuse SD card
partition Superboot has been written

c) in the PC Linux, repartition, points must be retained according to the
existing partitions on the SD card starting area
   1) The first note of Dir a partition of the starting position, such as
the 309,248 existing partitions, delete partition
   2) add a Area 1G FAT32, to establish an ext4 District after the first
partition;
   3) use mkfs.ext4 to create a file system, and then the mount to unpack
the ubuntu rootfs package and copied to the card;

d) back to the PC Windows, reformat the FAT32 area, copy the images
directory to the SD card

e) Insert the card to the board, the first programming superboot and kernel
to nand flash, nand boot switch is complete, keep the card does not pop
   Ubuntu You can restart into Ubuntu

On my side, I tried to compile the kernel with goodix_touch.c file to
generate the driver. But without success. A goodix_queue.h file is missing,
and I can not find it anywhere. And looking for it, I saw the
goodix_touch.c file was never the same between the different websites I
went. I tried to contact Goodix hotline, but the mentionned
support@goodix.com mail address seems to be broken.

I found this link but didn't test it yet
http://translate.google.com/translate?hl=fr&sl=auto&tl=en&u=...

Screwface, here are the drivers from the arm9 site:

http://db.tt/zihcQfOW

I don't think it actually needs the goodix_queue.h file :)  It's commented
out!

Hi guys,

I managed to get the goodix capacitive touchscreen working with Linux
Qtopia environment. I used the Qtopia rootfs I got from the last Tiny210
DVD image we recently downloaded, and I used a kernel I compiled using the
3.0.8 stock mini210_linux_defconfig file.
Then everything works fine.
I noticed TSLIB_TSDEVICE reports /dev/touchscreen-1wire
and /etc/ts.conf is as follow:
module_raw friendlyarm-ts-input
module pthres pmin=1
module variance delta=30
module dejitter delta=10000
module linear

so we will need FriendlyARM to release this friendlyarm-ts-input code to
compile it for other projects I think...

there is code, called one-wire-ts-input.c in the /src/ dir on the ftp site.
 However, it doesn't appear to work with the 3.0.8 kernel.  The
friendlyarm-ts-input module from the 2.6.35 kernel source doesn't work
either.

I'm not sure whether it's an issue with the driver code or something to do
with tslib (I'm getting an error in tslib that is apparently to do with
versions).

I saw that code but didn't try it. I assumed it was for mini6410 as the
names are different than mini210. And if I remember correctly, it was
released befor mini210s was sold.

The problem we have: we must have a consistent userland as far as I know.
So we should compile tslib with friendlyarm input plugin with the same
toolchain than the one which was used to create the ubuntu/debian packages.

- So which toolchain?
- Where to get the correct tslib plugin?
and in capacitive case, I have to try to success in compiling the driver
you provided.

I integrated it in the kernel et chose it to be builtin the kernel. But I
saw nothing detected. First I thought it was working and in fact, it was
FriendlyARM's one which was modprobed by /etc/init.d/rcS
I have to find how to get the makefile working.

But in any way, for the moment we are stuck with FA's kernel and OSes as we
are not able to have drivers working (audio, touchscreen and so on) with
another kernel (a vanilla one for example).

Another job we should do but I don't know how is trying to share cleaned
kernel config files because as you mentionned a few posts ago, they are
polluted with Android stuffs

My kernel actually feels quite nice, I built the adc-test.c app. and ran it
and it works, I can build with the compiler they supply or the one with my
ubuntu armhf core rootfs.

I'll post a tutorial on how to build an abuntu rootfs from scratch, it'll
be a bit like emdebian stage 1, most stuff is missing to start off with, I
have no idea really what should and shouldn't be on a system in the way of
initial packages, so it would be useful to find out.  I apt-get xorg and
lxde and get a pretty nice little desktop, none of that unity junk!

My kernel also has the multimedia stuff enabled too, although I'm not
entirely sure if any of it works right now.

But your kernel is 3.0.8, built with the provided toolchain isn't it? In
that case, of course everything works fine, I mean, the drivers modules.

In my case, I installed Debian with debootstrap, the same way as emdebian.

Here is the post associated to the one-wire-ts-input you mentionned.
http://www.friendlyarm.net/forum/topic/3366

Thanks for that link Screwface, that was the bit I was really missing, it
hasn't helped though :) I seem to have lost the ability to cat
/dev/touchscreen-1wire :(  I *think* I've probably messed with a kernel
config option.

That patch doesn't work with the latest tslib, I tried to figure out how to
 patch the latest tslib but failed, I'll try again later.

I tried to copy tslib in my debian system:
I transfered the whole /lib/modules/3.0.8-FriendlyARM for the goodix_touch
driver, /usr/lib/ts for tslib modules, /etc/ts.conf, /usr/lib/libts* and
finally /usr/local/bin/* for ts_calibrate.

Here is the script I use to test if it works:

#!/bin/bash
export TSLIB_TSEVENTTYPE=friendlyarm-ts-input
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/touchscreen-1wire
export TSLIB_CALIBFILE=/etc/ts.calib
export TSLIB_CONFFILE=/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

if [-f -etc-ts.calib]; then
  echo "Touchscreen already calibrated..."
else
  echo "Calibrating Touchscreen..."
  /usr/local/bin/ts_calibrate /etc/ts.calib
fi

export QWS_MOUSE_PROTO=tslib:/dev/input/touchscreen-1wire

Then ts_calibrate launches correctly, but still no reaction when touching
the screen. If I use /dev/input/event2 instead, I get an error (ts_open: No
such file or directory)

Still investigating on this issue...

touchscreen-1wire is for resistive 6410 and 210 touchscreens with 8-bit
microcontroller on LCD's PCB.
The only way to communicate with capacitive touchscreen is an i2c
interface, which is available through input subsystem
/dev/input/event[0-9].

I can't say which event[0-9] number you should use, because for example it
increases when you connect USB keyboard.

Before configuring tslib - try to hexdump these special devices. You are
looking for device, which outputs data on your screen only when you are
touching the screen.

If you get "no such file or directory" error, these commands should help:
mknod /dev/input/event2 c 13 66
mknod /dev/input/event3 c 13 67

I simply tried to configure tslib the same way as Qtopia environment which
worked with the capacitive touchscreen as mentionned in my previous post of
the 21th.
As I also mentionned, I tried with /dev/input/event2 which corresponds to
the touchscreen and it doesn't work, ts_calibrate won't run.

Reggie, maybe you would have better luck with your resistive H43?

I haven't had any luck with the resistive screen yet, my touchscreen
stopped outputting data on /dev/touchscreen1-wire and I'm not sure why.  I
ran the qtopia-linux image on it and teh touchscreen works fine still, so
it must be a configuration issue with my kernel setup.

To be fair though, I've probably trashed my ubuntu install for the mini210S
as I've been testing out other stuff, so I probably need to sit down and
start from scratch, once that's done I think I should be able to use the TS
again.

Another thing I would like to do is get the login screen sorted out, my
background just doesn't look right, the letters on the image are massive.

hello all (excuse me for my question in this forum)
I have problem with touchscreen in debian I install debian WITH DEBOOTSTRAP
ANDIN NEXT INSTALL LXDE. my bourd is mini6410 and do an open source tslib
tutorial(http://www.friendlyarm.net/forum/topic/3366), but not work . mknod
1wire has input when touching screen but every thinds(export
TSLIB_TSEVENTTYPE=friendlyarm-ts-input
...................) not work . i think problem is zimage and should change
it  or add touchscreen ko or so file in it or modprobe in startup
script.any idea ?!?!excuse me AGAIN.