Re: [ptxdist] rc.d script

Re: [ptxdist] rc.d script

[Henrik.Kraft]

[-- Attachment #1.1: Type: text/plain, Size: 167 bytes --]

done | (don't forget the pointercal file)

Kind regards

Henrik Kraft
z.Zt. Heidolph GmbH & Co. KG
Walpersdorfer Str. 12
91126 Schwabach
09122 - 99 20 - 58


[-- Attachment #1.2: Type: text/html, Size: 2915 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Henrik.Kraft]

We may close this item. I've got it running.

Thans for your support.

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Jürgen Beisert]

Hi Henrik,

On Monday 22 July 2013 14:05:47 Henrik.Kraft@heidolph.de wrote:
> even with /etc/init.d script my touch panel does not work. I have
>
> if [ -e "/etc/profile" ]; then
>         . /etc/profile
> fi
>
> if [ -e "/etc/profile.environment" ]; then
>         . /etc/profile.environment
> fi
>
> which also includes /etc/profeil.local in my script but it seems not to set
> the right variables. QWS_DISPLAY=linuxfb
> QWS_MOUSE_PROTO=tslib:/dev/input/event0
> QWS_KEYBOARD=USB:/dev/input/event1
> are set.
> Do you know what to set to which values (and can you tellme)?

You can try with the "profile.environment" from my Mini2440 BSP and adapt these 
values to your target:

MINI2440_FBDEV=/dev/fb0
MINI2440_KEYEVENT=/dev/input/buttons
MINI2440_TOUCHEVENT=/dev/input/touchscreen
#
# These LCDs are known. Use the size values only, if the kernel does
# not provide the size information.
#
# LCD (sizes are meant in [mm]):
# - Portrait 240 x 320 display of type "NEC NL2432HC22-23B" (N35)
# - Portrait 240 x 320 display of type "Sony ACX502BMU" (X35)
#      MINI2440_LCD_WIDTH=55 and MINI2440_LCD_HEIGHT=71
# - Portrait 240 x 320 display of type "STD035STED4" (T35)
#      MINI2440_LCD_WIDTH=53 and MINI2440_LCD_HEIGHT=71
# - Landscape 320 x 240 display of type "Sharp LQ035Q1DG06" (W35i)
#      MINI2440_LCD_WIDTH=72 and MINI2440_LCD_HEIGHT=54
# - Landscape 640 x 480 display of type "Innolux AT056TN523" (unknown)
#      MINI2440_LCD_WIDTH=113 and MINI2440_LCD_HEIGHT=85
# - Landscape 800 x 480 display of type "Innolux AT070TN83" (LCD70)
#      MINI2440_LCD_WIDTH=153 and MINI2440_LCD_HEIGHT=92
# - Landscape 480 x 272 display of type "NEC NL4827HC19-01B" (N43)
#      MINI6410_LCD_WIDTH=95 and MINI6410_LCD_HEIGHT=54
#
# MINI2440_LCD_WIDTH=55
# MINI2440_LCD_HEIGHT=71

# touchscreen relevant settings
export TSLIB_TSDEVICE=${MINI2440_TOUCHEVENT}
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=${MINI2440_FBDEV}
#export TSLIB_CALIBFILE
#export TSLIB_CONFFILE
#export TSLIB_PLUGINDIR

# Qt relevant settings
export QWS_MOUSE_PROTO=Tslib:${MINI2440_TOUCHEVENT}

QWS_DISPLAY=LinuxFb:nographicsmodeswitch:tty=none
if [ -n "${MINI2440_LCD_WIDTH}" ]; then
        QWS_DISPLAY=${QWS_DISPLAY}:mmWidth=${MINI2440_LCD_WIDTH}
fi
if [ -n "${MINI2440_LCD_HEIGHT}" ]; then
        QWS_DISPLAY=${QWS_DISPLAY}:mmHeight=${MINI2440_LCD_HEIGHT}
fi
export QWS_DISPLAY
export QWS_KEYBOARD=LinuxInput:${MINI2440_KEYEVENT}

But please keep in mind: "/dev/input/buttons" and "/dev/input/touchscreen" only 
exist because a special udev rule creates them. Otherwise they only are named 
as "event0" and "event1".

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-5121-206917-5128 |
Peiner Str. 6-8, 31137 Hildesheim, Germany    | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Henrik.Kraft]

Hello Juergen,

even with /etc/init.d script my touch panel does not work. I have

if [ -e "/etc/profile" ]; then                              
        . /etc/profile                      
fi

if [ -e "/etc/profile.environment" ]; then                              
        . /etc/profile.environment  
fi

which also includes /etc/profeil.local in my script but it seems not to set the right variables.
QWS_DISPLAY=linuxfb
QWS_MOUSE_PROTO=tslib:/dev/input/event0
QWS_KEYBOARD=USB:/dev/input/event1
are set.
Do you know what to set to which values (and can you tellme)?

-----Ursprüngliche Nachricht-----
Von: Jürgen Beisert [mailto:jbe@pengutronix.de] 
Gesendet: Montag, 22. Juli 2013 12:58
An: ptxdist@pengutronix.de
Cc: Kraft, Henrik
Betreff: Re: [ptxdist] rc.d script ..... cut ....

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Henrik.Kraft]

Thanks Juergen,

I don't know which variables this should be and as I need to set gain and offset for the touch panel I need to have a script executed so I will switch back to good old SystemV Init.

Do you know if I can have systemd and init scripts in parallel if I choose systemd with ptxdist and create /etc/init.d manually?

This is just a configuration issue. You must tell systemd to export some touchscreen and Qt related environment variables to all new processes it executes.

> With (manual) start via /etc/rc.d script this works well. 

From the old INITV days the script is located in "/etc/init.d" and a link exists in "/etc/rc.d/" pointing to this script. The name of the link defines the order to execute this script at runtime.

> ls -l /etc/rc.d/
total 0
lrwxrwxrwx 1 jbe ptx 14 Jun 19 12:26 S00udev -> ../init.d/udev lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:16 S01rc-once -> ../init.d/rc-once lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:29 S16telnetd -> ../init.d/telnetd lrwxrwxrwx 1 jbe ptx 20 Jun 19 11:30 S21alsa-utils -> ../init.d/alsa-utils lrwxrwxrwx 1 jbe ptx 20 Jun 19 11:29 S26networking -> ../init.d/networking lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:29 S98modules -> ../init.d/modules lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:18 S99startup -> ../init.d/startup

> What used to be done to have those scripts executed on startup?

Install the script itself to "/etc/init.d" with the help of PTXdist's "install_copy/install_alternative" macro and create the link with "install_link":

   @$(call install_alternative, [...], 0, 0, 0644, /etc/init.d/yourscript)
   @$(call install_link, [...], ../init.d/yourscript, /etc/rc.d/S99yourscript)

Regards,
Juergen

--
Pengutronix e.K.                              | Juergen Beisert             | Linux Solutions for Science and Industry      | Phone: +49-5121-206917-5128 | Peiner Str. 6-8, 31137 Hildesheim, Germany    | Fax:   +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Jürgen Beisert]

Hi Henrik,

On Monday 22 July 2013 12:19:52 Henrik.Kraft@heidolph.de wrote:
> as I have created scripts in /etc/rc.d for automatic start of programms
> (and settings) these are not executed on startup. I can't use systemd
> mechanism because if I use it our GUI application has no input from the
> touch panel.

This is just a configuration issue. You must tell systemd to export some 
touchscreen and Qt related environment variables to all new processes it 
executes.

> With (manual) start via /etc/rc.d script this works well. 

From the old INITV days the script is located in "/etc/init.d" and a link 
exists in "/etc/rc.d/" pointing to this script. The name of the link defines 
the order to execute this script at runtime.

> ls -l /etc/rc.d/
total 0
lrwxrwxrwx 1 jbe ptx 14 Jun 19 12:26 S00udev -> ../init.d/udev
lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:16 S01rc-once -> ../init.d/rc-once
lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:29 S16telnetd -> ../init.d/telnetd
lrwxrwxrwx 1 jbe ptx 20 Jun 19 11:30 S21alsa-utils -> ../init.d/alsa-utils
lrwxrwxrwx 1 jbe ptx 20 Jun 19 11:29 S26networking -> ../init.d/networking
lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:29 S98modules -> ../init.d/modules
lrwxrwxrwx 1 jbe ptx 17 Jun 19 11:18 S99startup -> ../init.d/startup

> What used to be done to have those scripts executed on startup?

Install the script itself to "/etc/init.d" with the help of 
PTXdist's "install_copy/install_alternative" macro and create the link 
with "install_link":

   @$(call install_alternative, [...], 0, 0, 0644, /etc/init.d/yourscript)
   @$(call install_link, [...], ../init.d/yourscript, /etc/rc.d/S99yourscript)

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-5121-206917-5128 |
Peiner Str. 6-8, 31137 Hildesheim, Germany    | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Alexander Dahl]

Am 2013-07-22 12:19, schrieb Henrik.Kraft@heidolph.de:
> as I have created scripts in /etc/rc.d for automatic start of
> programms (and settings) these are not executed on startup. I can't
> use systemd mechanism because if I use it our GUI application has no
> input from the touch panel. With (manual) start via /etc/rc.d script
> this works well.
> 
> What used to be done to have those scripts executed on startup?

This very much depends on your startup method. In ptxdist menuconfig you
gi "Root Filesystem" ---> "init" ---> "init method".

We use busybox init which uses init scripts put to /etc/init.d/ and
where you have symbolic links in rc.d pointing to the scripts in
/etc/init.d -- At system boot if you have the default /etc/inittab the
script /etc/init.d/rcS is executed which calls `run-parts -a start
/etc/rc.d` by default. "run-parts" is part of busybox itself. That's how
it goes with busybox init. I hope this contains some hints for you where
to look.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Henrik.Kraft]

Of course they are

-----Ursprüngliche Nachricht-----
Von: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] Im Auftrag von Josef Holzmayr
Gesendet: Montag, 22. Juli 2013 12:26
An: ptxdist@pengutronix.de
Betreff: Re: [ptxdist] rc.d script

Howdy!

> What used to be done to have those scripts executed on startup?

Primarily, the name must be SxxWhateverYouLike (e.g., start with an uppercase letter S)

Greetz
_____________________________________________________________
Josef Holzmayr
Dipl-Ing. (FH)
Entwicklung Embedded Devices / Software

Tel.: +49 8444 9204-48>
Fax:  +49 8444 9204-50
holzmayr@rsi-elektrotechnik.de

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548



--
ptxdist mailing list
ptxdist@pengutronix.de

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rc.d script

[Josef Holzmayr]

Howdy!

Am 22.07.2013 12:19, schrieb Henrik.Kraft@heidolph.de:
 > What used to be done to have those scripts executed on startup?

Primarily, the name must be SxxWhateverYouLike (e.g., start with an 
uppercase letter S)

Greetz
_____________________________________________________________
Josef Holzmayr
Dipl-Ing. (FH)
Entwicklung Embedded Devices / Software

Tel.: +49 8444 9204-48>
Fax:  +49 8444 9204-50
holzmayr@rsi-elektrotechnik.de

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548



-- 
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] rc.d script

[Henrik.Kraft]

[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]

Hello,

as I have created scripts in /etc/rc.d for automatic start of programms (and settings) these are not executed on startup. I can't use systemd mechanism because if I use it our GUI application has no input from the touch panel. With (manual) start via /etc/rc.d script this works well.

What used to be done to have those scripts executed on startup?

Kind regards

Henrik Kraft
currently at Heidolph GmbH & Co. KG
Walpersdorfer Str. 12
91126 Schwabach
09122 - 99 20 - 58


[-- Attachment #1.2: Type: text/html, Size: 3402 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de