Tuxbox auch für x86 / x64 ?

[prodigy7]

Hallo,

mal eine ganz laienhafte Frage: Ihr seit ja momentan dabei, das ganze Tuxbox Zeug für die verschiedenen Boxen fit zu machen - wäre es theoretisch auch möglich, dann zB Neutrino für die x86 Architektur zu bauen, oder gibts hier noch zuviel "spezielles" Zeug was das verhindern würde?
Zum einem denke ich daran, das es gerade für die Entwicklung ja so einfacher sein könnte, es gibt ja aber auch mittlerweile dank Atom & Co Stromsparende Settop Boxen die ja auch was taugen würden.

prodigy7

[seife]

Bauen ist kein Problem, das ist mein configurescript:

Code: Alles auswählen

#!/bin/sh
TOPDIR=/local/seife/src/tuxbox-native
TARGETPREFIX=$TOPDIR/root/cdkroot
export PKG_CONFIG_PATH=$TARGETPREFIX/lib/pkgconfig
export PATH=$TARGETPREFIX/bin:$TARGETPREFIX/sbin:$PATH
# CFLAGS="-funsigned-char -Wshadow -Werror" CXXFLAGS="$CFLAGS" # for the brave
# CFLAGS="-funsigned-char -Wshadow" CXXFLAGS="$CFLAGS" \
CFLAGS="-funsigned-char -O0 -g -W -Wall" CXXFLAGS="$CFLAGS" \
        ./configure     --oldincludedir=$TARGETPREFIX/include \
                --prefix=$TARGETPREFIX \
                --exec-prefix=$TARGETPREFIX \
                --enable-maintainer-mode \
                --with-dvbincludes=/usr/include \
                --with-driver=/local/seife/src/tuxbox-native/driver \
                --with-boxtype=generic \
                --with-datadir=$TARGETPREFIX/share/tuxbox \
                --with-fontdir=$TARGETPREFIX/share/fonts \
                $@

Das Problem ist eher, dass dir der code bei aktuellen Compilern um die Ohren fliegt (weil die etwas penibler sind, was Pfusch angeht ), allerdings habe ich das Meiste davon schon gefixt und dass du es evtl. für die DVB-FF Karten patchen musst, wenn du denn noch eine bekommst, wegen OSD und so.
Ansonsten läuft es bei mir, aber halt ohne display etc, ist also nicht wirklich hilfreich

[prodigy7]

Und wie würde es ausschauen, wenn ich das Zeug nur bauen wollte, um die Funktionalität zu testen? Also wenn man kein TV-Bild bräuchte?

[seife]

siehe oben. Aber du hast ja nicht nur kein Bild sondern auch keine Framebuffer.
Ausser du hast ne grafikkarte, die 720x576 im Framebuffer kann.
Ausserdem würde ich neutrino nie als root auf einem PC laufen lassen, den ich nochmal für was anderes verwenden will Ohne root geht aber vermutlich nicht viel im FB.

[mohousch]

habe das ganz Neutrino-Zeug für eine Samsung SMT 7020S (i386), da ich nicht viel für den dem Frambuffer Ahnung habe habe ein blau/green Neutrino auf dem Bildschirm, (zapit) zappt auch aber kein Bild da der Mpeg-Decoder einen V4l API Treiber hat und keinen Nativ Linux-DVB-API, mindestens kann über das webif im PC was schauen.

[seife]

was ist denn ein "v4l api treiber"? Heisst das, man müsste den stream aus /dev/dvb/.../dvr rausholen und in /dev/vide0 wieder reinpusten? Das sollte ja machbar sein. Der Framebuffer auch.

Wenn die smt7020 nicht hardwaremässig so unter aller Sau wäre, was die Bildqualität und den Stromerbrauch angeht, dann... aber so kauf ich mir keine.

[prodigy7]

Es gibt da auch noch die IP1101, die mal eine Zeit lang mit Maxdome vertickert wurde ... wenn man n DVB-T Stick zB dran hängt, ist das auch eine nette Settop-Box.

Mohousch: Was genau hast du dafür gemacht, gepatcht? Könntest du das dokumentieren?

[mohousch]

@seife: Sorry die gegen Frage: heisst es wenn es wie bei der zapit der TS an den Mpeg Decoder geleitet ist wird es an /dev/video0 und /dev/sound nicht weiter geleitet (gefiltert)

prodigy7?An Neutrino (Inkl. Deamons) habe noch nichts gepacht, nutze eine kleine oldmake file daß das rootfs wie bei der Box baut (busybox, ftpd, depmod, kernel-26 + Driver passend zu SMT) alles auf dem Flash-DOM (32 MB) der DOM ist 50% delegt, kann Dir das makefile zukommen lassen wenn Du willst

[seife]

Bei den dvb-Treibern (dbox und z.b. FF DVB-Karte) sage ich einfach dem Treiber "leite diese Audio-PID und diese Video-PID an den dekoder weiter", den Rest macht die Hardware (oder besser: die Firmware auf der Hardware ). Wie funktioniert das bei der "V4L API"?

[mohousch]

das weiß ich auch nicht ;( wollte mich aus dem VDR SRC schlau machen hab es aber nicht geschafft;( .

Die SMT hat einen Conexant Chip (cx23882-19 MPEG) der schon im Kernel ist und mit noch einen zusätlichen DVB Patch für die SMT und das laden des Frontend und cx2388 Modul ergibt folgenden devices:
dev/dvb/adapter0/frontend0, dev/dvb/adapter0/demux0, dev/dvb/adapter0/dvr0, dev/dvb/adapter0/net0 registred als DVB /dev/video0 und /dev/vbi0 registred als v4l2 .

hier ist das syslog:

Apr 30 23:13:26 Samsung SMT 7020S syslog.info syslogd started: BusyBox v1.7.2
Apr 30 23:13:26 Samsung SMT 7020S user.notice kernel: klogd started: BusyBox v1.7.2 (2009-04-24 16:17:05 CEST)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: .000000] ACPI: BOOT 07EFBFD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 0.000000] Allocating PCI resources starting at 10000000 (gap: 08000000:f7800000)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 0.000000] Built 1 zonelists in Zone order. Total pages: 32243
Apr 30 23:13:26 Samsung SMT 7020S user.notice kernel: [ 0.000000] Kernel command line: root=/dev/hda1 rw
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 0.000000] mapped APIC to ffffb000 (01101000)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 0.000000] Enabling fast FPU save and restore... .
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 0.000000] Enabling unmasked SIMD FPU exception support... .
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 0.000000] Initializing CPU#0
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 0.000000] Detected 731.279 MHz processor.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.767575] Console: colour VGA+ 80x25
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.767587] console [tty0] enabled
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.769488] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.769798] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.778596] Memory: 124112k/129984k available (2599k kernel code, 5404k reserved, 1314k data, 152k init, 0k highmem)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778688] virtual kernel memory layout:
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778692] fixmap : 0xffff5000 - 0xfffff000 ( 40 kB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778696] vmalloc : 0xc8800000 - 0xffff3000 ( 887 MB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778699] lowmem : 0xc0000000 - 0xc7ef0000 ( 126 MB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778703] .init : 0xc04d6000 - 0xc04fc000 ( 152 kB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778707] .data : 0xc0389e81 - 0xc04d29d8 (1314 kB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.778710] .text : 0xc0100000 - 0xc0389e81 (2599 kB)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.779059] Checking if this processor honours the WP bit even in supervisor mode... Ok.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.929411] Calibrating delay using timer specific routine.. 1463.51 BogoMIPS (lpj=7317597)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.929622] Mount-cache hash table entries: 512
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 22.929898] CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.929926] CPU: L1 I cache: 16K, L1 D cache: 16K
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.930009] CPU: L2 cache: 256K
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 22.930061] CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000 00000000
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.930082] Compat vDSO mapped to ffffe000.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.930151] CPU: Intel Mobile Intel(R) Celeron(TM) CPU 733MHz stepping 04
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.930313] Checking 'hlt' instruction... OK.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.970063] ACPI: Core revision 20070126
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.973540] ACPI: setting ELCR to 0200 (from 1ea0)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.975538] NET: Registered protocol family 16
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.976055] ACPI: bus type pci registered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.988932] PCI: PCI BIOS revision 2.10 entry at 0xfd994, last bus=1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 22.988992] PCI: Using configuration type 1
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 22.989043] Setting up standard PCI resources
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.000362] ACPI: EC: Look up EC in DSDT
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.004558] ACPI: Interpreter enabled
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.004622] ACPI: (supports S0 S1 S3 S5)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.004812] ACPI: Using PIC for interrupt routing
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.014621] ACPI: PCI Root Bridge [PCI0] (0000:00)
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.015004] PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.015065] PCI quirk: region 1180-11bf claimed by ICH4 GPIO
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.015906] PCI: Transparent bridge - 0000:00:1e.0
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.015998] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.016131] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB_._PRT]
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.020957] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.021557] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 7 9 10 11 12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.022143] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *9 10 11 12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.022730] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 *10 11 12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.023318] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 *7 9 10 11 12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.023904] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.024561] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.025218] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 11 *12 14 15)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.025905] Linux Plug and Play Support v0.97 (c) Adam Belay
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.026038] pnp: PnP ACPI init
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.026108] ACPI: bus type pnp registered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.033239] pnp: PnP ACPI: found 11 devices
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.033304] ACPI: ACPI bus type pnp unregistered
Apr 30 23:13:26 Samsung SMT 7020S user.notice kernel: [ 23.033846] SCSI subsystem initialized
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.034157] usbcore: registered new interface driver usbfs
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.034361] usbcore: registered new interface driver hub
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.034526] usbcore: registered new device driver usb
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.035013] PCI: Using ACPI for IRQ routing
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.035071] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.069379] Time: tsc clocksource has been installed.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.089476] pnp: 00:01: iomem range 0x7f00000-0x807ffff could not be reserved
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.089547] pnp: 00:02: iomem range 0xff800000-0xffffffff could not be reserved
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.120389] PCI: Bridge: 0000:00:1e.0
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.120447] IO window: 3000-3fff
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.120502] MEM window: f4100000-f6ffffff
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.120556] PREFETCH window: disabled.
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.120623] PCI: Setting latency timer of device 0000:00:1e.0 to 64
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.120683] NET: Registered protocol family 2
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.219406] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.219593] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.219741] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.219842] TCP: Hash tables configured (established 4096 bind 4096)
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.219898] TCP reno registered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.249570] Simple Boot Flag at 0x36 set to 0x1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.250580] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.251072] NTFS driver 2.1.28 [Flags: R/O].
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.251291] io scheduler noop registered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.251344] io scheduler deadline registered (default)
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.251413] Boot video device is 0000:00:02.0
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.251507] PCI: Firmware left 0000:01:08.0 e100 interrupts enabled, disabling
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.251962] input: Power Button (FF) as /class/input/input0
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.252020] ACPI: Power Button (FF) [PWRF]
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.252305] input: Sleep Button (CM) as /class/input/input1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.252362] ACPI: Sleep Button (CM) [SLPB]
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.258568] Real Time Clock Driver v1.12ac
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.258636] Linux agpgart interface v0.102
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.258797] agpgart: Detected an Intel i815 Chipset.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.268935] agpgart: AGP aperture is 64M @ 0xf8000000
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.269601] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 23.269661] PCI: setting IRQ 11 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 23.269668] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.272218] i810-i2c: Probe DDC1 Bus
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.410295] i2c-adapter i2c-0: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.630242] i2c-adapter i2c-0: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.850191] i2c-adapter i2c-0: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 23.929184] i810-i2c: Probe DDC2 Bus
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.070141] i2c-adapter i2c-1: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.290090] i2c-adapter i2c-1: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.510040] i2c-adapter i2c-1: unable to read EDID block.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589033] i810-i2c: Probe DDC3 Bus
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589083] i810-i2c: Getting EDID from BIOS
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589135] i810fb_init_pci: DDC probe successful
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589189] i810fb_init_pci: Unable to get Mode Database
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589685] I810FB: fb0 : Intel(R) 815 (Internal Graphics with AGP) Framebuffer Device v0.9.0
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589691] I810FB: Video RAM : 4096K
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589695] I810FB: Monitor : H: 29-30 KHz V: 60-60 Hz
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.589698] I810FB: Mode : 640x480-8bpp@60Hz
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.589954] FS453/4 driver, (c) 2005 Freescale Semiconductor, Inc.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.590012] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.590195] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.590437] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.591417] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.591768] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.592420] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 24.592479] PCI: setting IRQ 5 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: 24.592486] ACPI: PCI Interrupt 0000:00:1f.6 -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.592624] ACPI: PCI interrupt for device 0000:00:1f.6 disabled
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.593439] loop: module loaded
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.593802] nbd: registered device at major 43
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.595550] e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.595612] e100: Copyright(c) 1999-2006 Intel Corporation
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.596223] ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 7
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 24.596286] PCI: setting IRQ 7 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.596293] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [LNKE] -> GSI 7 (level, low) -> IRQ 7
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 24.596500] PCI: Setting latency timer of device 0000:01:08.0 to 64
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.619490] e100: eth0: e100_probe: addr 0xf4100000, irq 7, MAC addr 00:00:F0:20:C5:0A
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.619787] Linux video capture interface: v2.00
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.619926] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.619988] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.620183] ICH2: IDE controller at PCI slot 0000:00:1f.1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.620255] ICH2: chipset revision 5
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.620306] ICH2: not 100% native mode: will probe irqs later
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.620374] ide0: BM-DMA at 0x1800-0x1807, BIOS settings: hda:pio, hdb:pio
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 24.620518] ide1: BM-DMA at 0x1808-0x180f, BIOS settings: hdc:pio, hdd:pio
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 24.620655] Probing IDE interface ide0...
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 24.929090] hda: DMSTORAGE FDM032MAA, ATA DISK drive
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 25.288882] hda: tPIO > 2, assuming tPIO = 2
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 25.288935] hda: applying conservative PIO "downgrade"
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 25.289190] hda: tPIO > 2, assuming tPIO = 2
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 25.289241] hda: applying conservative PIO "downgrade"
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 25.289520] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 25.289754] Probing IDE interface ide1...
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 25.888935] Probing IDE interface ide1...
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.488696] hda: max request size: 128KiB
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.488753] hda: 63488 sectors (32 MB) w/2KiB Cache, CHS=496/4/32
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.488962] hda: hda1
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 26.492281] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 26.492346] PCI: setting IRQ 10 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.492354] ACPI: PCI Interrupt 0000:01:05.2[C] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.492502] ehci_hcd 0000:01:05.2: EHCI Host Controller
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.492724] ehci_hcd 0000:01:05.2: new USB bus registered, assigned bus number 1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.493805] ehci_hcd 0000:01:05.2: irq 10, io mem 0xf4101000
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.493867] ehci_hcd 0000:01:05.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.494361] usb usb1: configuration #1 chosen from 1 choice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.494531] hub 1-0:1.0: USB hub found
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.494598] hub 1-0:1.0: 4 ports detected
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.598875] USB Universal Host Controller Interface driver v3.0
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.599067] ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 26.599212] PCI: Setting latency timer of device 0000:00:1f.2 to 64
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.599220] uhci_hcd 0000:00:1f.2: UHCI Host Controller
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.599373] uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 2
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.599473] uhci_hcd 0000:00:1f.2: irq 10, io base 0x00001820
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.599914] usb usb2: configuration #1 chosen from 1 choice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.600080] hub 2-0:1.0: USB hub found
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.600148] hub 2-0:1.0: 2 ports detected
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 26.709255] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 12
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 26.709317] PCI: setting IRQ 12 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.709324] ACPI: PCI Interrupt 0000:00:1f.4[C] -> Link [LNKH] -> GSI 12 (level, low) -> IRQ 12
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 26.709466] PCI: Setting latency timer of device 0000:00:1f.4 to 64
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.709475] uhci_hcd 0000:00:1f.4: UHCI Host Controller
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.709658] uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 3
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.709759] uhci_hcd 0000:00:1f.4: irq 12, io base 0x00001840
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.710209] usb usb3: configuration #1 chosen from 1 choice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.710376] hub 3-0:1.0: USB hub found
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.710441] hub 3-0:1.0: 2 ports detected
Apr 30 23:13:26 Samsung SMT 7020S user.err kernel: [ 26.818786] hub 3-0:1.0: over-current change on port 1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.818907] ACPI: PCI Interrupt 0000:01:05.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.819053] uhci_hcd 0000:01:05.0: UHCI Host Controller
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.819215] uhci_hcd 0000:01:05.0: new USB bus registered, assigned bus number 4
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.819316] uhci_hcd 0000:01:05.0: irq 5, io base 0x00003040
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.819764] usb usb4: configuration #1 chosen from 1 choice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.819935] hub 4-0:1.0: USB hub found
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.820005] hub 4-0:1.0: 2 ports detected
Apr 30 23:13:26 Samsung SMT 7020S user.err kernel: [ 26.928507] hub 3-0:1.0: over-current change on port 2
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 26.929261] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 9
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 26.929322] PCI: setting IRQ 9 as level-triggered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.929329] ACPI: PCI Interrupt 0000:01:05.1 -> Link [LNKC] -> GSI 9 (level, low) -> IRQ 9
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.929473] uhci_hcd 0000:01:05.1: UHCI Host Controller
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.929648] uhci_hcd 0000:01:05.1: new USB bus registered, assigned bus number 5
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.929747] uhci_hcd 0000:01:05.1: irq 9, io base 0x00003060
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.930204] usb usb5: configuration #1 chosen from 1 choice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.930373] hub 5-0:1.0: USB hub found
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 26.930441] hub 5-0:1.0: 2 ports detected
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.038796] Initializing USB Mass Storage driver...
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.678353] usbcore: registered new interface driver usb-storage
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.678413] USB Mass Storage support registered.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.678535] usbcore: registered new interface driver usblcd
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.678780] PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.928670] serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.929015] mice: PS/2 mouse device common for all mice
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.929181] i2c /dev entries driver
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 27.929662] w83627hf: Found W83627HF chip at 0x290
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.176931] usbcore: registered new interface driver usbhid
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.176995] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.177102] TCP cubic registered
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.177169] NET: Registered protocol family 1
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.177226] NET: Registered protocol family 17
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.177425] ieee80211: 802.11 data/management/control stack, git-1.1.13
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.177511] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 28.177585] ieee80211_crypt: registered algorithm 'NULL'
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 28.177592] ieee80211_crypt: registered algorithm 'WEP'
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 28.177599] Using IPI Shortcut mode
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.334912] kjournald starting. Commit interval 5 seconds
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.354481] EXT3 FS on hda1, internal journal
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.354567] EXT3-fs: recovery complete.
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.361486] EXT3-fs: mounted filesystem with ordered data mode.
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 28.361578] VFS: Mounted root (ext3 filesystem).
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 28.362781] Freeing unused kernel memory: 152k freed
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 29.919583] ACPI: PCI Interrupt 0000:00:1f.5 -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
Apr 30 23:13:26 Samsung SMT 7020S user.debug kernel: [ 29.919752] PCI: Setting latency timer of device 0000:00:1f.5 to 64
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.237745] intel8x0_measure_ac97_clock: measured 51019 usecs
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.237814] intel8x0: clocking to 48000
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.482354] cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.484180] CORE cx88[0]: subsystem: 18ac:dc00, board: Samsung SMT 7020 DVB-S [card=58,insmod option]
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.484271] TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 30.650411] !!Samsung RESET .
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 30.650483] cx88[0]/2: cx2388x 8802 Driver Manager
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.650565] ACPI: PCI Interrupt 0000:01:04.2[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.650706] cx88[0]/2: found at 0000:01:04.2, rev: 5, irq: 11, latency: 64, mmio: 0xf6000000
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.695114] cx2388x v4l2 driver version 0.0.6 loaded
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.696838] ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.696992] cx88[0]/0: found at 0000:01:04.0, rev: 5, irq: 11, latency: 165, mmio: 0xf5000000
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.698787] cx88[0]/0: registered device video0 [v4l2]
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.700489] cx88[0]/0: registered device vbi0
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.844478] cx2388x dvb driver version 0.0.6 loaded
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.844762] cx8802_register_driver() ->registering driver type=dvb access=shared
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 30.845050] CORE cx88[0]: subsystem: 18ac:dc00, board: Samsung SMT 7020 DVB-S [card=58]
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 30.845548] cx88[0]/2: cx2388x based dvb car
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: d
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 31.009211] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Apr 30 23:13:26 Samsung SMT 7020S user.info kernel: [ 31.579054] DVB: registering new adapter (cx88[0])
Apr 30 23:13:26 Samsung SMT 7020S user.warn kernel: [ 31.579296] DVB: registering frontend 0 (ST STV0299 DVB-S)...

[seife]

Wie spielst du auf dem Device mpegs oder Transportstreams ab? Wird der mpeg-dekoder überhaupt benutzt oder läuft VDR mit vdr-xine im Framebuffer oder X?

[mohousch]

vdr mit xine-vdr im X oder framebuffer + DirectfFB läuft auf diese Box, hab es jetzt aber nicht drauf.

Dachte gründsichtlich wenn man bei setPIDs in dem Demux das output an dem Mpeg Decoder (DMX_OUT_DECODER) denn ist es einfach wie du oben geschrieben hast das Video/Audio PID weiter an die HW zu leiten und bei der DVB-API sind mir die ioctl() auch bekannt und einfacher aber bei dem /dev/video0 komme nicht weiter glaube in der xineliboutput() ist das gemacht ob das aus dem dvr und den zu HW weiter geleleitet ist oder direkt aus /dev/video0 weiß ich noch nicht.

PS: bei der Dbox in dem avia ist auch ein v4l Device; welche apps den nutzt mir ist unbekannt, lade auch nicht .

[seife]

vdr-xine dekodiert in software, nicht in Hardware.
Neutrino kannst du darauf wohl vergessen.

[mohousch]

vdr-xine dekodiert in software, nicht in Hardware.
Neutrino kannst du darauf wohl vergessen.

OK aber nochmal die Frage, wenn das TS an dem Mpeg Dekoder geleitet ist also wird es an dem /dev/video0 weiter geleitet (wie es bei DVB an /dev/.../video0 und /dev/.../audio0) oder nicht? eigentlich schon oder?

PS: in Fall der Dbox kann man aus dem avia_gt_v4l2 (dev/v4l/video0) die Audio/Video PIDs zapfen?

[seife]

Sorry, ich kann nicht dekodieren was du schreibst.

Bei einer Fullfeatured-Karte oder der dbox wird eben nichts abgezapft sondern intern direkt durchgeleitet. Siehe die entsprechenden ioctls mit DMX_OUT_DECODER oder so ähnlich im zapit.

Ich vermute, dass der mpeg dekoder in der smt7020 eben nicht benutzbar ist und deswegen in software dekodiert wird.

[mohousch]

OK nochmal zu deiner erste Idee, werde das Mpeg Decoder vergessen und den TS nach dvr leiten (das habe ich schon) und den zu der A/V HW leiten , kannst mir bitte paar Helpline zu diesem Konzept geben?

PS: bei der Dbox in dem v4l Driver Teil die write-routine function gibt es nicht, ausser driver name card name kann man nicht viel rausholen.

[seife]

DAS DING HAT KEINE BENUTZBARE A/V-HARDWARE! KEINEN BENUTZBAREN MPEG-DEKODER!

Zumindest sieht es aus deinen Beschreibungen so aus. Und ich schreib das nicht noch 10x.

[mohousch]

DAS DING HAT KEINE BENUTZBARE A/V-HARDWARE! KEINEN BENUTZBAREN MPEG-DEKODER!

Zumindest sieht es aus deinen Beschreibungen so aus. Und ich schreib das nicht noch 10x.

Sorry! für meine ganzen OT hier

[seife]

DAs ist nicht böse gemeint, aber ich habe es mindestens 5x geschrieben, dass es ohne mpeg-dekoder schwer wird. Und wenn xine-vdr verwendet wird, ist das ein ganz starkes indiz, dass es eben keinen dekoder oder keinen Treiber dafür gibt

[mohousch]

OK

just for fun kann man jetzt für die dbox das Video/Audio aus dem /dev/v4l/video0 leiten?

[seife]

nein, wenn ich das recht verstanden habe ist /dev/v4l/* dazu da, um z.B. frames zu capturen, Carjay hatte da früher glaub mal mit experimentiert, aber für live-video geht das imho nicht, nur für overlay.
Den mpeg-TS bekommst du aus /dev/dvb/.../dvr0