+ Antworten
Seite 2 von 6 ErsteErste 1234 ... LetzteLetzte
Ergebnis 11 bis 20 von 54
  1. #11
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    634
    Thanks
    144
    Thanked 712 Times in 304 Posts
    The project approach

    The reason I started to try and bring Enigma2/Neutrino to the 4th generation Fortis receivers is twofold:
    • The duckbox-developers-git has an entry for the DP7000, so somebody (j00zek) already had provided a starting point;
    • I owned a DP7001 at that point in time.


    I first set out to explore the DP7000 stuff in the git mentioned, and soon found out that it probably contained some files directly originated from Fortis, but also that apart from some basic aspects, not much had been done with regard to receiver specific development. In addition, apart from the initial commit, the git has been stationary with regard to the DP7000 up to now.

    Then I devised an approach of my own. The first step was to build a debug kernel that can be loaded and started with the stock bootloader already present in the receiver. Once the printk output can be seen on the serial port of the receiver, its config can be tuned and the required features can be added one by one. This has led to the .config I am using for about two months now, although it is not finished and/or optimized. The current kernel loads (with one error remaining) and starts the /etc/init.d/.rcS. Later on in the project I succeeded in retrieving the .config used by Fortis from the kernel in one of the their stock firmwares and used that info to further tune the .config I use. So far I have only built with patch level 215.

    The next step is one I foresaw I could not finish on my own (and one of the reasons I started this thread): try and get/build all the drivers. Some are simply missing and not created yet in any git like the frontpanel driver, others do probably exist but are not available publicly or not found yet (like the FDMA firmware). I have tried to write the missing drivers on my own, and succeeded for some. The order of building is simply the order the rcS script uses to install them.

    When the essential drivers are all ready, the next step would be to adapt Enigma2/Neutrino to the receiver(s), but that point has not been reached yet.

    More to come, the kernel is in the next posting...

    Regards,

    Audioniek.
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark TripleX, Amiko Alien 2+, Sogno Spark Revolution, Kathrein UFS910(1 & 14W)/912/913/922(CX24116 & AVL2108 tuners), Vizyon revolution 820HD PVR, AB IPBox 91HD/9000HD/9000HD rev.2, Xsarius Alpha HD10, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  2. The Following 5 Users Say Thank You to Audioniek For This Useful Post:



  3. #12
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    634
    Thanks
    144
    Thanked 712 Times in 304 Posts
    The kernel

    As explained in the previous posting, the kernel .config has been determined through trial and error at first, after which the .config used by Fortis themselves was retrieved from a stock firmware kernel. This led to both a further refinement of the .config as well as confirmation of most of the choices made so far. The .config currently used is not final and can certainly be optimized, but my first goal was to build a kernel that would start and try to execute the /etc/init.d/rcS, and that first goal has been achieved.

    The second part that is receiver specific is the modification of the kernel source files to adapt them to the main board specifics. Here the files already provided for the DP7000 in the duckbox-developer git came in handy, as they seemed to originate from Fortis directly.

    Fortis has based the models DP6010 and DP7001 on the B2067 Rev C board; the EPP8000 is based on the similar B2064 board. For the moment I assume that the DP7000 and DP7050 are based on the B2067C as well, but this needs confirmation. For the EP8000 which is possibly a stripped EPP8000 and the GPV8000 which is also a twin tuner model, your guess is as good as mine. My guess is the B2067C for the moment until confirmed otherwise, although the loader version 8.37 points to the B2064 board.
    These boards use the TM1668 driver chip as display/keyboard driver for the front panel as standard. As reported, Fortis uses an ET6226 for the LED models and an ET16315 for the VFD ones. I removed the TM1668 code from the kernel, and decided to add the driver code to the frontpanel driver to be loaded by the /etc/init.d/rcS script, which has been the usual approach with Enigma2/Neutrino.

    I added the usual patch to add the MAC address from the bootargs into the kernel command line and proceeded with adding the mtd blocks, which are the same as the setup used by Fortis. This approach is needed to be able to use the factory supplied boot loader, and as explained before yield a memory layout that is quite suitable for both Enigma2 and Neutrino. I was lucky with respect to printk output through the RS-232 console connection, as the setting of the DP7000 .config and setup patches worked immediately.
    The GPIO numbers were determined by adding a temporary test programme to the initial kernel code and observing the behaviour of the LEDs and control lines of the front panel driver. In some setup patches it is still present, but will be removed of course when things get more definitive.
    As of this posting, the result of all this can be found in the Fortis-4G git.

    When built and flashed in an EPP8000, the console output of the kernel startup is currently this:
    Code:
    Error: Bad gzipped data -> normal boot loader message when no valid boot up picture .gz file is present in mtd3 block
    FrTs###*#2
    Linux version 2.6.32.61_stm24_0215 (ndv@TEST-PC) (gcc version 4.8.2 20131016 (STMicroelectronics/Linux Base 4.8.2-131) (GCC) ) #1 PREEMPT Thu Feb 12 17:51:19 CET 2015
    Boot params:
    ... MOUNT_ROOT_RDONLY - 00000001
    ... RAMDISK_FLAGS     - 00000000
    ... ORIG_ROOT_DEV     - 00000200
    ... LOADER_TYPE       - 00000000
    ... INITRD_START      - 00000000
    ... INITRD_SIZE       - 00000000
    Booting machvec: epp8000
    Node 0: start_pfn = 0x40000, low = 0x52800
    Zone PFN ranges:
      Normal   0x00040000 -> 0x00052800
    Movable zone start PFN for each node
    early_node_map[1] active PFN ranges
        0: 0x00040000 -> 0x00052800
    Fortis EPP8000 board initialisation
    STxH205 version 2.x
    bpa2: partition 'bigphysarea' created at 0x48000000, size 32768 kB (0x02000000 B)
    bpa2: partition 'LMI_IO' created at 0x4a000000, size 65536 kB (0x04000000 B)
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 75184
    Kernel command line: console=ttyAS0,115200 root=/dev/mtdblock2 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rw init=/bin/devinit coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 console_loglevel=7 stmmaceth=ethaddr:00:1e:b8:0f:e9:92
    PID hash table entries: 2048 (order: 1, 8192 bytes)
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    PVR=04909420 CVR=60880000 PRR=0000aa00
    I-cache : n_ways=2 n_sets=512 way_incr=16384
    I-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
    D-cache : n_ways=2 n_sets=512 way_incr=16384
    D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
    Memory: 188160k/303104k available (3478k kernel code, 1692k data, 128k init)
    Hierarchical RCU implementation.
    NR_IRQS:600
    Console: colour dummy device 80x25
    console [ttyAS0] enabled
    sh_tmu: TMU0 used for clock events
    sh_tmu: TMU0 used for periodic clock events
    sh_tmu: TMU1 used as clock source
    Calibrating delay loop... 645.12 BogoMIPS (lpj=322560)
    Mount-cache hash table entries: 512
    CPU: STxH205
    [STM][PM-Sys]: ilc3 @ 4096
    NET: Registered protocol family 16
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    Generic PHY: Registered new driver (0xffffffff)
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    DMA: Registering DMA API.
    Switching to clocksource TMU1
    NET: Registered protocol family 2
    IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    TCP established hash table entries: 16384 (order: 5, 131072 bytes)
    TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
    TCP: Hash tables configured (established 16384 bind 16384)
    TCP reno registered
    NET: Registered protocol family 1
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    [STM]: [PM]: Suspend support registered
    [STM]: [PM]: HoM support registered
    [STM]: [PM]: [HoM]: Early console @ fe530000
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    Slow work thread pool: Starting up
    Slow work thread pool: Ready
    NTFS driver 2.1.29 [Flags: R/W].
    fuse init (API version 7.13)
    msgmni has been set to 367
    alg: No test for stdrng (krng)
    io scheduler noop registered
    io scheduler anticipatory registered (default)
    io scheduler deadline registered
    io scheduler cfq registered
    lirc_dev: IR Remote Control driver registered, major 61 
    lirc-stm: probe found data for platform device lirc-stm
    lirc-stm: STM LIRC plugin using IRQ 181 in IR mode
    lirc_dev: lirc_register_driver: sample_rate: 0
    STMicroelectronics LIRC driver initialized.
    STMicroelectronics ASC driver initialized
    stm-asc.0: ttyAS0 at MMIO 0xfe530000 (irq = 219) is a stm-asc
    loop: module loaded
    MiPHY driver style MiPHYA40X probed successfully
    MiPHYA40X, c2.1 Claimed by ahci 
    ahci ahci: forcing PORTS_IMPL to 0x1
    ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
    scsi0 : ahci
    ata1: SATA max UDMA/133 mmio [0xfd548000-0xfd548fff] port 0x100 irq 234
    ONFI flash detected
    ONFI param page 0 valid
    NAND device: Manufacturer ID: 0x01, Chip ID: 0xda (AMD S34ML02G1)
    stm-nand-flex: Using legacy platform timing data
    stm-nand-flex: Using boot partition name [boot] (from kernel config)
    cmdlinepart partition parsing not available
    Creating 9 MTD partitions on "stm-nand-flex":
    0x000000000000-0x000000100000 : "boot"
    0x000000400000-0x000000800000 : "kernel"
    0x000000800000-0x00000be00000 : "rootfs"
    0x000000180000-0x000000380000 : "logo"
    0x000000380000-0x000000400000 : "eeprom"
    0x000008000000-0x000008100000 : "config"
    0x00000be00000-0x00000fe00000 : "user"
    0x000000000000-0x000010000000 : "ALL"
    0x00000fe00000-0x000010000000 : "config1"
    stm-nand-flex: Found BOOT parition[boot], updating ECC paramters
    boot-ECC 0x00000000->0x00100000
    UBI: attaching mtd2 to ubi0
    UBI: physical eraseblock size:   131072 bytes (128 KiB)
    UBI: logical eraseblock size:    129024 bytes
    UBI: smallest flash I/O unit:    2048
    UBI: sub-page size:              512
    UBI: VID header offset:          512 (aligned 512)
    UBI: data offset:                2048
    UBI: attached mtd2 to ubi0
    UBI: MTD device name:            "rootfs"
    UBI: MTD device size:            182 MiB
    UBI: number of good PEBs:        1456
    UBI: number of bad PEBs:         0
    UBI: max. allowed volumes:       128
    UBI: wear-leveling threshold:    4096
    UBI: number of internal volumes: 1
    UBI: number of user volumes:     1
    UBI: available PEBs:             0
    UBI: total number of reserved PEBs: 1456
    UBI: number of PEBs reserved for bad PEB handling: 14
    UBI: max/mean erase counter: 1/0
    UBI: image sequence number: 184918554
    UBI: background thread "ubi_bgt0d" started, PID 403
    ICPlus IP1001: Registered new driver (0x02430d90)
    ICPlus IP101A: Registered new driver (0x02430c54)
    ICPlus IP175C: Registered new driver (0x02430d80)
    stmmac - user ID: 0x10, Synopsys ID: 0x36
     DMA HW capability register supported
     Enhanced/Alternate descriptors
     RX Checksum Offload Engine supported
     TX Checksum insertion supported
     Wake-Up On Lan supported
    mdio_bus 0:00: IC+101G: disable EEE advertise
    STMMAC MII Bus: probed
    eth0: PHY ID 02430c54 at 0 IRQ 201 (0:00) active
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    stm_usb_probe: usb_phy_clk clock not found for stm-usb.0
    stm-ehci stm-ehci.0: STMicroelectronics EHCI Host Controller
    stm-ehci stm-ehci.0: new USB bus registered, assigned bus number 1
    stm-ehci stm-ehci.0: irq 235, io mem 0xfe0ffe00
    stm-ehci stm-ehci.0: USB 0.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    stm-ohci stm-ohci.0: STMicroelectronics OHCI Host Controller
    stm-ohci stm-ohci.0: new USB bus registered, assigned bus number 2
    stm-ohci stm-ohci.0: irq 238, io mem 0xfe0ffc00
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata1.00: ATA-9: WDC WD10JPVX-22JC3T0, 01.01A01, max UDMA/133
    ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access     ATA      WDC WD10JPVX-22J 01.0 PQ: 0 ANSI: 5 -> my EPP8000 has indeed a WD hard drive built in...
    sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    sd 0:0:0:0: [sda] 4096-byte physical blocks
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
     sda:
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    stm_usb_probe: usb_phy_clk clock not found for stm-usb.1
    stm-ehci stm-ehci.1: STMicroelectronics EHCI Host Controller
    stm-ehci stm-ehci.1: new USB bus registered, assigned bus number 3
    stm-ehci stm-ehci.1: irq 236, io mem 0xfe1ffe00
     sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    stm-ehci stm-ehci.1: USB 0.0 started, EHCI 1.00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 1 port detected
    stm-ohci stm-ohci.1: STMicroelectronics OHCI Host Controller
    stm-ohci stm-ohci.1: new USB bus registered, assigned bus number 4
    stm-ohci stm-ohci.1: irq 239, io mem 0xfe1ffc00
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 1 port detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    i2c /dev entries driver
    Linux video capture interface: v2.00
    sh_tmu: TMU0 kept as earlytimer
    sh_tmu: TMU1 kept as earlytimer
    [STM][PM-Sys]: emi @ 40
    [STM][PM-Sys]: gpio @ 20
    [STM][PM-Sys]: sysconf @ 10
    [STM][PM-Sys]: clk @ 30
    stm-lpm stm-lpm.0: firmware: using built-in firmware lpm_fwSTxH205.elf
    LPM: Found sbc f/w 
    STM_LPM driver registered
    Memory region request failed for stm-sysconf.4! -> only remaining kernel startup error (memory allocation problem)
    stm-sysconf: probe of stm-sysconf.4 failed with error -16
    DMA: Registering fdma_dmac.0 handler (16 channels).
    IRQ 203/fdma_dmac.0: IRQF_DISABLED is not guaranteed on shared IRQs
    stm-fdma stm-fdma.0: firmware: requesting fdma_STxH205_0.elf
    DMA: Registering fdma_dmac.1 handler (16 channels).
    IRQ 205/fdma_dmac.1: IRQF_DISABLED is not guaranteed on shared IRQs
    stm-fdma stm-fdma.1: firmware: requesting fdma_STxH205_1.elf
    stm-rng hardware driver 1.0 configured
    stm-rtc stm-rtc: rtc core: registered stm-rtc as rtc0
    Advanced Linux Sound Architecture Driver Version 1.0.21.
    sound/stm/stx7200.c:215: Not supported (other than STx7200) SOC detected!
    ALSA device list:
      No soundcards found. -> No solution for sound driver yet
    TCP cubic registered
    NET: Registered protocol family 10
    NET: Registered protocol family 17
    stm-rtc stm-rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    UBIFS: recovery needed
    stm lpm: configuring gpio_power: GPIO[3][7]
    stm-rtc-sbc stm-rtc-sbc.0: rtc core: registered stm-rtc-sbc as rtc1
    usb 3-1: new high speed USB device using stm-ehci and address 2
    UBIFS: recovery completed
    UBIFS: mounted UBI device 0, volume 0, name "rootfs"
    UBIFS: file system size:   184117248 bytes (179802 KiB, 175 MiB, 1427 LEBs)
    UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
    UBIFS: media format:       w4/r0 (latest is w4/r0)
    UBIFS: default compressor: zlib
    UBIFS: reserved for root:  0 bytes (0 KiB)
    VFS: Mounted root (ubifs filesystem) on device 0:12.
    Freeing unused kernel memory: 128k freed
    INIT: version 2.88 booting
    usb 3-1: configuration #1 chosen from 1 choice
    hub 3-1:1.0: USB hub found
    hub 3-1:1.0: 3 ports detected
    [rcS] Start
    I sure hope you like the looks of this.

    More to come (drivers and rcS for example)...

    Regards,

    Audioniek.
    Geändert von Audioniek (16.02.2015 um 09:58 Uhr)
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark TripleX, Amiko Alien 2+, Sogno Spark Revolution, Kathrein UFS910(1 & 14W)/912/913/922(CX24116 & AVL2108 tuners), Vizyon revolution 820HD PVR, AB IPBox 91HD/9000HD/9000HD rev.2, Xsarius Alpha HD10, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  4. The Following 8 Users Say Thank You to Audioniek For This Useful Post:



  5. #13
    Erfahrener Benutzer
    Registriert seit
    11.03.2013
    Beiträge
    138
    Thanks
    14
    Thanked 57 Times in 41 Posts
    hi audioniek,
    i use this one to display iboot logo, but i merged it to i-boot binary. maybe its worth a try to cat it to mtd3 so we would know if fortis uses the same coding
    i-bootlogo7.gam.gz

  6. The Following 3 Users Say Thank You to solala For This Useful Post:



  7. #14
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    634
    Thanks
    144
    Thanked 712 Times in 304 Posts
    Hello solala,

    Thank you for your input, and you were spot on. File size and header info are exactly the same as the pictures used by Fortis. If I rename the unpacked .gam picture to duckbox.Booting.gam and gzip it, then add the .gz as user data (partition type 9) to the fup arguments, flash the .ird, then the Linux and Atemio logos (plus the text Titanit) are shown on power on. Can you enlighten me on how to create my own .gam pictures?

    Meanwhile I have added support for the bootpicture to the flash environment: if X/cdk/root/bootscreen/bootscreen.gz is found, that file is used as the bootpicture file.

    Regards,

    Audioniek.
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark TripleX, Amiko Alien 2+, Sogno Spark Revolution, Kathrein UFS910(1 & 14W)/912/913/922(CX24116 & AVL2108 tuners), Vizyon revolution 820HD PVR, AB IPBox 91HD/9000HD/9000HD rev.2, Xsarius Alpha HD10, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  8. The Following User Says Thank You to Audioniek For This Useful Post:



  9. #15
    Neuer Benutzer
    Registriert seit
    14.10.2014
    Beiträge
    8
    Thanks
    47
    Thanked 0 Times in 0 Posts
    what's new


  10. #16
    Neuer Benutzer
    Registriert seit
    17.12.2014
    Beiträge
    2
    Thanks
    0
    Thanked 1 Time in 1 Post
    Hello.
    I have Xcruiser XDSR 420 Avant receiver.
    I want to change channels via Up and Down buttons (they are on the top and bottom of the OK button). I mean that I want these buttons to do CH+/CH- functions.
    But when I press Up or Down there is channel menu on the screen.
    How to change that, because it is very uncomfortable?


  11. #17
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    634
    Thanks
    144
    Thanked 712 Times in 304 Posts
    @zozman

    At the moment I am, very busy solving problems on Spark7162, as many HDMU users are affected by them. So that takes precedence at the moment.

    @Kodov
    Assuming your are talking about the original Xcruiser firmware: all Fortis firmwares have this behaviour by design, and it cannot be changed as these firmwares are closed source. And why do you want to have functions on these keys that have their own keys quite nearby on the remote?

    Regards,

    Audioniek.
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark TripleX, Amiko Alien 2+, Sogno Spark Revolution, Kathrein UFS910(1 & 14W)/912/913/922(CX24116 & AVL2108 tuners), Vizyon revolution 820HD PVR, AB IPBox 91HD/9000HD/9000HD rev.2, Xsarius Alpha HD10, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  12. The Following User Says Thank You to Audioniek For This Useful Post:



  13. #18
    Neuer Benutzer
    Registriert seit
    17.12.2014
    Beiträge
    2
    Thanks
    0
    Thanked 1 Time in 1 Post
    Zitat Zitat von Audioniek Beitrag anzeigen
    @Kodov
    Assuming your are talking about the original Xcruiser firmware: all Fortis firmwares have this behaviour by design, and it cannot be changed as these firmwares are closed source. And why do you want to have functions on these keys that have their own keys quite nearby on the remote?

    Regards,

    Audioniek.
    I want to change this because I use to have functions on these keys.
    But I solved the problem. You can use plugin SX key_redefine to change the keys.
    Best regards, Kodov.

  14. The Following User Says Thank You to Kodov For This Useful Post:



  15. #19
    Erfahrener Benutzer Avatar von harryhase
    Registriert seit
    26.01.2013
    Beiträge
    197
    Thanks
    34
    Thanked 55 Times in 31 Posts
    can you please send a link for this plugin?


  16. #20
    Neuer Benutzer
    Registriert seit
    07.05.2012
    Beiträge
    10
    Thanks
    25
    Thanked 5 Times in 3 Posts
    Geändert von souhai (12.05.2015 um 17:05 Uhr)

  17. The Following 2 Users Say Thank You to souhai For This Useful Post:



Berechtigungen

  • Neue Themen erstellen: Ja
  • Themen beantworten: Ja
  • Anhänge hochladen: Ja
  • Beiträge bearbeiten: Ja
  •