Bazaar

Just about everything about Red Pitaya
DJ2NL
Posts: 5
Joined: Tue Jan 19, 2016 3:55 pm

Re: Bazaar

Post by DJ2NL » Thu Jan 21, 2016 4:35 pm

Where can I find the version/ release of the OS?

PA0TRT
Posts: 6
Joined: Sun Jan 10, 2016 11:17 pm

Re: Bazaar

Post by PA0TRT » Thu Jan 21, 2016 6:22 pm

Hi RP
Today I have checked my RP with the one of a friend.
We swapped the SD cards of both board and used an entirely ethernet.
Result was that the problem sticks to my RP board while the my SD cards worked fine in the other RP.

My conclusion is that there must be a difference with my RP board in firmware or hardware.

Note: Both RP's are in use with SDR radio.

Kind regards
Rien

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: Bazaar

Post by Nils Roos » Thu Jan 21, 2016 11:05 pm

DJ2NL wrote:Where can I find the version/ release of the OS?
In version.txt on the first partition's root directory (or /opt/redpitaya/version.txt in the Red Pitaya console).

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: Bazaar

Post by Nils Roos » Thu Jan 21, 2016 11:11 pm

PA0TRT wrote:My conclusion is that there must be a difference with my RP board in firmware or hardware.
Well, the MAC address of the ethernet adapter is a property of the board. With DHCP this usually means that your board will also retain its assigned IP address and associated configuration in the network.

PA0TRT
Posts: 6
Joined: Sun Jan 10, 2016 11:17 pm

Re: Bazaar

Post by PA0TRT » Fri Jan 22, 2016 2:37 am

All
Here is the dump from my RP console after power on
Regards Rien
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

U-Boot 2015.04 (Dec 21 2015 - 12:25:29), Build: jenkins-RedPitaya-Ecosystem-inte
rnal-master-558

Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 480 MiB
I2C:EEPROM selection failed
MMC: zynq_sdhci: 0
In: serial
Out: serial
Err: serial
Board: Xilinx Zynq
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Running script from SD...
Device: zynq_sdhci
Manufacturer ID: 41
OEM: 3432
Name: SD4GB
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading u-boot.scr
576 bytes read in 16 ms (35.2 KiB/s)
## Executing script at 02000000
Set devicetree and ramdisk high loading address to 512MB-64MB
Loading from SD card (FAT file system) to memory
Device: zynq_sdhci
Manufacturer ID: 41
OEM: 3432
Name: SD4GB
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading uImage
3973424 bytes read in 263 ms (14.4 MiB/s)
reading devicetree.dtb
12509 bytes read in 17 ms (717.8 KiB/s)
Booting Linux kernel with ramdisk and devicetree
## Booting kernel from Legacy Image at 02001000 ...
Image Name: Linux-3.18.0-xilinx
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3973360 Bytes = 3.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 04000000
Booting using the fdt blob at 0x4000000
Loading Kernel Image ... OK
Loading Device Tree to 1bff9000, end 1bfff0dc ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 3.18.0-xilinx (jenkins@dragon) (gcc version 4.9.3 20141031 (prerel
ease) (Linaro GCC 2014.11) ) #1 SMP PREEMPT Mon Dec 21 12:30:22 CET 2015
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: xlnx,zynq-7000
cma: Reserved 16 MiB at 0x1d000000
Memory policy: Data cache writealloc
PERCPU: Embedded 10 pages/cpu @5cc10000 s8704 r8192 d24064 u40960
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 121920
Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 ro rootfstype=ext
4 earlyprintk rootwait
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)
Memory: 462656K/491520K available (5444K kernel code, 336K rwdata, 1776K rodata,
216K init, 238K bss, 28864K reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
vmalloc : 0x5e800000 - 0xff000000 (2568 MB)
lowmem : 0x40000000 - 0x5e000000 ( 480 MB)
pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
.text : 0x40008000 - 0x40715384 (7221 kB)
.init : 0x40716000 - 0x4074c000 ( 216 kB)
.data : 0x4074c000 - 0x407a00e0 ( 337 kB)
.bss : 0x407a00e0 - 0x407db9bc ( 239 kB)
Preemptible hierarchical RCU implementation.
Dump stacks of tasks blocking RCU-preempt GP.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76360001
slcr mapped to 5e804000
zynq_clock_init: clkc starts at 5e804100
Zynq clock init
sched_clock: 64 bits at 249MHz, resolution 4ns, wraps every 2199023255552ns
timer #0 at 5e806000, irq=43
Console: colour dummy device 80x30
Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x52d860 - 0x52d8b8
CPU1: Booted secondary processor
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Brought up 2 CPUs
SMP: Total of 2 processors activated.
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x5e880000
VCCPINT: 1000 mV
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@l
inux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
cfg80211: Calling CRDA to update world regulatory domain
Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 935
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Even
ts-16
xuartps e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 59, base_baud = 624999
9) is a xuartps
console [ttyPS0] enabled
xuartps e0001000.serial: ttyPS1 at MMIO 0xe0001000 (irq = 82, base_baud = 624999
9) is a xuartps
xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 5e86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
libphy: XEMACPS mii bus: probed
xemacps e000b000.ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
usbcore: registered new interface driver rt2800usb
usbcore: registered new interface driver rtl8192cu
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ULPI transceiver vendor/product ID 0x0424/0x0007
Found SMSC USB3320 ULPI transceiver.
ULPI integrity check: passed.
zynq-ehci zynq-ehci.0: Xilinx Zynq USB EHCI Host Controller
zynq-ehci zynq-ehci.0: new USB bus registered, assigned bus number 1
zynq-ehci zynq-ehci.0: irq 53, io mem 0x00000000
zynq-ehci zynq-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
at24 0-0050: 8192 byte 24c64 EEPROM, writable, 32 bytes/write
cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 57
zynq-edac f8006000.memory-controller: ecc not enabled
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-arasan e0100000.sdhci: No vmmc regulator found
sdhci-arasan e0100000.sdhci: No vqmmc regulator found
mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nf_conntrack version 0.5.0 (7485 buckets, 29940 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
Registering SWP/SWPB emulation handler
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
mmc0: new high speed SDHC card at address 0007
mmcblk0: mmc0:0007 SD4GB 3.67 GiB
mmcblk0: p1 p2
EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
EXT4-fs (mmcblk0p2): write access will be enabled during recovery
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 216K (40716000 - 4074c000)
systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSV
¡®^.]Y[²«LWDetected architecture 'arm'.COMP -APPARMOR)
Welcome to Debian GNU/Linux 8 (jessie)!

systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.
¡®^.]Y[²«LWCannot add dependency job for unit display-manager.service, ignorin
Expecting device dev-ttyPS0.device...e...Wall Directory Watch..y.
[ OK ] Reached target Remote File Systems (Pre).
¡®^.]Y[²«LWSet up automount Arbitrary Executable File Formats File System Auto
[ OK ] Reached target Encrypted Volumes.
[ OK ] Reached target Paths.Password Requests to Console Directory Watch..
[ OK ] Reached target Swap.ths.
Expecting device dev-mmcblk0p1.device...e...
[ OK ] Created slice Root Slice.
[ OK ] Created slice User and Session Slice.
[ OK ] Listening on Delayed Shutdown Socket.ce.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on Journal Socket (/dev/log).ity Named Pipe.
[ OK ] Listening on udev Control Socket.dev/log).
[ OK ] Listening on udev Kernel Socket.ket.
[ OK ] Listening on Journal Socket.Socket.
[ OK ] Created slice System Slice.ket.
Starting File System Check on Root Device...e...
[ OK ] Created slice system-getty.slice.
systemd[1]: Starting system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
systemd[1]: Created slice system-serial\x2dgetty.slice.
systemd[1]: Starting Increase datagram queue length...
Starting Increase datagram queue length...
systemd[1]: Starting Restore / save the current clock...
Starting Restore / save the current clock...
systemd[1]: Started Create list of required static device nodes for the current
kernel.
systemd[1]: Starting Create Static Device Nodes in /dev...
Starting Create Static Device Nodes in /dev...
systemd[1]: Starting udev Coldplug all Devices...
Starting udev Coldplug all Devices...
systemd[1]: Mounted Huge Pages File System.
systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
systemd[1]: Mounted POSIX Message Queue File System.
systemd[1]: Mounted Debug File System.
systemd[1]: Started Set Up Additional Binary Formats.
systemd[1]: Starting Slices.
[ OK ] Reached target Slices.
systemd[1]: Reached target Slices.
[ OK ] Started Increase datagram queue length.
systemd[1]: Started Increase datagram queue length.
[ OK ] Started Load Kernel Modules.
systemd[1]: Started Load Kernel Modules.
[ OK ] Started File System Check on Root Device.
[ OK ] Started Restore / save the current clock.ce.
[ OK ] Started Create Static Device Nodes in /dev..
[ OK ] Started udev Coldplug all Devices.des in /dev.
Starting udev Kernel Device Manager...r...
Starting Remount Root and Kernel File Systems......
systemd[1]: Mounted FUSE Control File System.
Starting Apply Kernel Variables...s...
[ OK ] Listening on Syslog Socket.le System.
EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ OK ] Reached target Sockets.Socket.
Starting Journal Service...e...
[ OK ] Started Journal Service.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Apply Kernel Variables.
[ OK ] Found device /dev/ttyPS0.
Starting Load/Save Random Seed...
[ OK ] Reached target Local File Systems (Pre).
Mounting /tmp/ram...
systemd-fsck[662]: /dev/mmcblk0p2: clean, 31577/216432 files, 206642/864768 bloc
ks
Starting Copy rules generated while the root was ro...
[ OK ] Mounted /tmp/ram.
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Copy rules generated while the root was ro.
[ OK ] Found device /dev/mmcblk0p1.
Mounting /opt/redpitaya...
Mounting /boot...
[ OK ] Mounted /boot.
[ OK ] Mounted /opt/redpitaya.
[ OK ] Reached target Local File Systems.
[ OK ] Reached target Remote File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting Create Volatile Files and Directories...
Starting LSB: Raise network interfaces....
[ OK ] Started Create Volatile Files and Directories.
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.rom PID 1
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started LSB: Raise network interfaces..
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Timers.
[ OK ] Reached target Basic System.
Starting Regular background program processing daemon...
[ OK ] Started Regular background program processing daemon.
Starting OpenBSD Secure Shell server...
[ OK ] Started OpenBSD Secure Shell server.
Starting Customized Nginx web server for Red Pitaya applications...
Starting Advanced key-value store...
Starting /etc/rc.local Compatibility...
Starting getty on tty2-tty6 if dbus and logind are not available...
Starting LSB: DHCP server...
Starting LSB: Start NTP daemon...
Starting LSB: Advanced IEEE 802.11 management daemon...
Starting LSB: Brings up/down network automatically...
Starting System Logging Service...
Starting Permit User Sessions...
[ OK ] Started getty on tty2-tty6 if dbus and logind are not available.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started Permit User Sessions.
Starting Getty on tty6...
[ OK ] Started Getty on tty6.
Starting Getty on tty5...
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt.
Please run fsck.
[ OK ] Started Getty on tty5.
Starting Getty on tty4...
[ OK ] Started Getty on tty4.
Starting Getty on tty3...
[ OK ] Started Getty on tty3.
Starting Getty on tty2...
[ OK ] Started Getty on tty2.
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
Starting Serial Getty on ttyPS0...
[ OK ] Started Serial Getty on ttyPS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started LSB: Start NTP daemon.
[ OK ] Started Advanced key-value store.
[ OK ] Started System Logging Service.
[ OK ] Started Customized Nginx web server for Red Pitaya applications.
Starting Lights up heartbeet LED...
[ OK ] Started LSB: Advanced IEEE 802.11 management daemon.
[ OK ] Started Lights up heartbeet LED.
[FAILED] Failed to start LSB: DHCP server.
See 'systemctl status isc-dhcp-server.service' for details.
(•µ…Á́*Á‚‚Á‚‚r*Ñ¡•É¹•Ñéb¥¹­ªÁBŠ‚‚‚z2UÅŠ*©Hz
Debian GNU/Linux 8 redpitaya ttyPS0

redpitaya login: root
Password:
Last login: Fri Jan 22 01:38:29 CET 2016 on ttyPS0
Linux redpitaya 3.18.0-xilinx #1 SMP PREEMPT Mon Dec 21 12:30:22 CET 2015 armv7l
##############################################################################
# Red Pitaya GNU/Linux Ecosystem
# Version: 0.94
# Branch: master
# Build: 558
# Commit: 2c11e5ef7cddfa305033253e2381c2571699c90f
##############################################################################
redpitaya>

User avatar
redpitaya
Site Admin
Posts: 387
Joined: Wed Mar 26, 2014 7:04 pm

Re: Bazaar

Post by redpitaya » Fri Jan 22, 2016 10:30 am

Hi,

If you have SDR radio installed the Bazaar will not work. The problem is somewhere in SDR radio app.
IF you have fresh SD card, it should work.
We had some problems with the latest build, so can you please try with
previous versions:
http://downloads.redpitaya.com/downloads/
red_pitaya_OS_v0.94-RC21_2-Dec-2015.img.zip
or
red_pitaya_OS_v0.94-RC22_21-Dec-2015.img.zip

All best, RP

DJ2NL
Posts: 5
Joined: Tue Jan 19, 2016 3:55 pm

Re: Bazaar

Post by DJ2NL » Fri Jan 22, 2016 11:01 am

I understand that something is wrong with the firmware of the last batches RP's

This is my MAC adress:
00:26:32:f0:19:08

Chris

pavel
Posts: 619
Joined: Sat May 23, 2015 5:22 pm

Re: Bazaar

Post by pavel » Fri Jan 22, 2016 11:14 am

If you have SDR radio installed the Bazaar will not work. The problem is somewhere in SDR radio app.
This is strange. I have both SDR applications installed and the Bazaar working without any problem.

Here is a link to the SD card image that I'm using:

http://downloads.redpitaya.com/download ... 15.img.zip

pavel
Posts: 619
Joined: Sat May 23, 2015 5:22 pm

Re: Bazaar

Post by pavel » Fri Jan 22, 2016 11:41 am

I think that I understand, what readpitaya wanted to explain about the SDR applications.

I've just discovered that the Bazaar system requires an identifier called DNA:
https://github.com/RedPitaya/RedPitaya/ ... n.cpp#L412
https://github.com/RedPitaya/RedPitaya/ ... a_hk.v#L59

The correct description of the problem would be the following:
"Bazaar stops working when the SDR applications are running"

A very simple workaround is to run any other application (Oscilloscope, Spectrum Analyzer , etc) after running the SDR applications.

I'll update the SDR application as soon as I find a solution to this problem.
Last edited by pavel on Fri Jan 22, 2016 12:03 pm, edited 1 time in total.

pa0hwb
Posts: 1
Joined: Thu Dec 17, 2015 12:23 pm

Re: Bazaar

Post by pa0hwb » Fri Jan 22, 2016 11:47 am

As Rien PA0TRT already wrote, we compared 2 Redpitayas in exactly the same network conditions. My RP could enter the bazaar and the other RP could not, resulting in a error message.
We use the same software package. Exchanging SD-cards still resulted in the fact that the RP from Rien could not enter the bazaar. So this problem has nothing to to with network problems or SD-card differences. The problem must be in the Redpitaya board itself and/or the firmware of the latest version of the Redpitaya.
Perhaps it is possible (it has to be done by Redpitaya themselves) to look at differences in the firmware from the earlier and latest version of the RP-board.
I see there are more people struggling with this issue, so i hope a quick analysis and solution of the error will be available.
Hans

Post Reply
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 4 guests