News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - macfly

#1
Yes, that really worked.

Now what was going on? My "old" nfs-root was build with kernel 2.4.17. Sadly, i do not have the old build-environment. Do you have the old files? is the kernelconfig for the NFS-Kernel identical to the current kernel?

regards,
Friedhelm.
#2
*sight*

I'm hopping from one Problem to the next.

I managed to compile a new kernel with nfs-root support, but the mvp doesn't manage to go up with this kernel.

according to the logfile, the mvp gets an IP, requests the nfs-kernel, rerequests an IP and is quiet until reboot:
Mar  4 17:39:13 master dnsmasq[28653]: DHCPDISCOVER(eth1) 00:0d:fe:00:42:65
Mar  4 17:39:13 master dnsmasq[28653]: DHCPOFFER(eth1) 192.168.42.31 00:0d:fe:00:42:65
Mar  4 17:39:13 master in.tftpd[28995]: RRQ from 192.168.42.31 filename mvp-kernelimage-nfsroot
Mar  4 17:39:28 master dnsmasq[28653]: DHCPDISCOVER(eth1) 00:0d:fe:00:42:65
Mar  4 17:39:28 master dnsmasq[28653]: DHCPOFFER(eth1) 192.168.42.31 00:0d:fe:00:42:65
Mar  4 17:39:28 master dnsmasq[28653]: DHCPREQUEST(eth1) 192.168.42.31 00:0d:fe:00:42:65
Mar  4 17:39:28 master dnsmasq[28653]: DHCPACK(eth1) 192.168.42.31 00:0d:fe:00:42:65 mvp.4t.to


What's missing is a logentry, that the MVP is mounting the nfs-share. I configured dnsmasq to give the MVP all Information it needs:

dhcp-host=00:0d:fe:00:42:65,net:mvpnet,mvp.4t.to,mvp.4t.to,24h
dhcp-option=mvpnet,17,"/tftpboot/root/vomp"
dhcp-boot=net:mvpnet,mvp-kernelimage-nfsroot,server,192.168.42.4


so the MVp should try to mount "/tftpboot/root/vomp" on nfs-server 192.168.42.4 - but this request doesn't occur. the NFS-server is up as i have other clients (headless VDR) which uses nfs from this machine.

anyone an idea?
#3
OK, seems there were some inconsistency in my system. I deinstalled everything about gcc 3.3, 3.4 and 4.0, leaving 4.1 alone.

right now, crosstool is compiling.

thank you for your tipp.
#4
no one with this error? What gcc are you using?

I found this error here: http://sources.redhat.com/ml/crossgcc/2002-05/msg00100.html, but there is no real solution to this. Why do only i run into this error?

regards,
Friedhelm.
#5
thank you for this hint, this worked, but:

when compiling the crosstool, i get an error with gcc-3.4.5-glibc-2.2.5:

cc1: error: unrecognized command line option "-mnew-mnemonics"

Does anyone know this problem?
#6
hm, looks like the makedev-4 script is unhappy with my system. I started it in a clean environment, it downloaded some files, compiled everything until binutils, and then:

+ cd ..
+ logresult binutils /opt/vdr/vomp_new/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-ld
+ test -x /opt/vdr/vomp_new/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-ld
+ echo crosstool: binutils built ok
crosstool: binutils built ok
+ echo 'Install glibc headers needed to build bootstrap compiler -- but only if gcc-3.x'
Install glibc headers needed to build bootstrap compiler -- but only if gcc-3.x
+ grep -q 'gcc-[34]' /opt/vdr/vomp_new/crosstool/crosstool-0.43/build/powerpc-405-linux-gnu/gcc-3.4.5-glibc-2.2.5/gcc-3.4.5/ChangeLog
+ test '!' -f /opt/vdr/vomp_new/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/powerpc-405-linux-gnu/include/features.h
+ mkdir -p build-glibc-headers
+ cd build-glibc-headers
+ test '!' -f Makefile
+ libc_cv_ppc_machine=yes
+ CC=gcc
+ /opt/vdr/vomp_new/crosstool/crosstool-0.43/build/powerpc-405-linux-gnu/gcc-3.4.5-glibc-2.2.5/glibc-2.2.5/configure --prefix=/usr --build=i686-pc-linux-gnu --host=powerpc-405-linux-gnu --without-cvs --disable-sanity-checks --with-headers=/opt/vdr/vomp_new/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/powerpc-405-linux-gnu/include --enable-hacker-mode
creating cache ./config.cache
checking host system type... powerpc-405-linux-gnu
checking sysdep dirs... sysdeps/powerpc/elf sysdeps/unix/sysv/linux/powerpc sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv sysdeps/unix/powerpc sysdeps/unix sysdeps/posix sysdeps/powerpc/fpu sysdeps/powerpc sysdeps/wordsize-32 sysdeps/ieee754/flt-32 sysdeps/ieee754/dbl-64 sysdeps/powerpc/soft-fp sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for pwd... /bin/pwd
checking build system type... i686-pc-linux-gnu
checking for powerpc-405-linux-gnu-gcc... gcc
checking version of gcc... 4.1.2, bad
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 3.81, ok
configure: error:
*** These critical programs are missing or too old:gcc
*** Check the INSTALL file for required versions.


I don't think, that the script does mean *my* gcc (since its 4.1.2). I guess, it does mean the gcc in crosstolls, right?

#7
OK, I think i found the Problem. My NFS-kernel-Image was 2.4.17 - i think, this is too old. I'll rebuild the kernel with 2.4.31 and try again.

thank you!
#8
Hello all.

I'm  trying to do some stuff to the current CVS (marks), but i have difficulties running the compiled vompclient. When i use the actual precompiled 0.2.6-dongle, everything works. If i use the CVS-Tag 0.2.6 (or HEAD), recompiles everything and copy this vompclient to the nfs-environment for my MVP, starting the client looks like:

00:03:16.586273 [info]   Core - Starting up...
00:03:16.601776 [info]   Core - Signal handlers set up successfully
00:03:16.614572 [info]   Core - Remote module initialised
00:03:16.615384 [info]   Core - LED module initialised
00:03:16.616923 [debug]  MTD - Failed to find correct /dev/mtdX device
00:03:16.617718 [EMERG]  Core - Mtd module failed to initialise
00:03:16.618493 [notice] Core - ViewMan module shut down
00:03:16.619288 [notice] Core - Command module shut down
00:03:16.620100 [notice] Core - VDR module shut down
00:03:16.620869 [notice] Core - OSD module shut down
00:03:16.621634 [notice] Core - Audio module shut down
00:03:16.622403 [notice] Core - Video module shut down
00:03:16.623183 [notice] Core - Timers module shut down
00:03:16.623949 [notice] Core - MTD module shut down
00:03:16.624712 [notice] Core - LED module shut down
00:03:16.625512 [notice] Core - Remote module shut down
00:03:16.626271 [notice] Core - Log module shutting down... bye!


any idea?
#9
Hey Chris, one more question.

what do you think about what buttons should be used for cutting marks? I know, that you want the colorbuttons for skipping back and forward, and that ok. The numbers are reserved for jumping to 10%, 20%, ... 90%. OK, too.

But for cuttingmarks to work, i need buttons for:

  • toggle a mark
  • moving mark to left
  • moving mark to right
  • jumping to next mark
  • jumping to previous mark
  • opening a menu (for recording commands, defined on server)

My first idea was: when playing, use the normal buttons, when in pause-mode, redefine numberbuttons for mark-editing.
But i think, this is not very usefull.
My next idea was, using a button for toggleing playback and editing-mode. Maybe indicated by a sticky progressbar with different colors.

What do you think about this?

regards,
Friedhelm.
#10
 :D

I'll look & learn.

thank you very much!


update: I just collapsed. thank you for your comment. I had to read it three times to believe it :)
#11
Hello again,

i did not made any advance in this issue. Chris, do you have a idea, why my threadFeedPause does not display the correct still image?
#12
OK, i'm stuck.  ???

i modified switchState, so that one can jump into S_PAUSE_I-Mode. The Implementation of this part calls threadFeedPause() (a new implementation similar to threadFeedScan, but without scanning).

threadFeedPause looks like this:

void Player::threadFeedPause()
{
  ULONG baseFrameNumber = 0;
  ULONG nextiframeNumber = 0;
  ULONG iframeNumber = 0;
  ULONG iframeLength = 0;
  ULLONG filePos;
  UINT amountReceived;
  UINT videoLength;
  baseFrameNumber = currentFrameNumber;
  if (!vdr->getNextIFrame(baseFrameNumber, 1, &filePos, &nextiframeNumber, &iframeLength))
    return;

  vdr->getNextIFrame(nextiframeNumber, 0, &filePos, &iframeNumber, &iframeLength);

  baseFrameNumber = iframeNumber;
  threadBuffer = vdr->getBlock(filePos, iframeLength, &amountReceived);
  videoLength = demuxer->stripAudio(threadBuffer, amountReceived);
  video->displayIFrame(threadBuffer, videoLength);

  currentFrameNumber = iframeNumber;
  free(threadBuffer);
  threadBuffer = NULL;
}

but this damn video->displayIFrame simply does not update the screen!
I guess, i did not understand some essentials in playback. Could one please assist me in this issue?

regards,
Friedhelm.
#13
thank you both for your answers. I'll try to figure out for myself, how to implement this.
I'll ask for help if i'm stuck.

Friedhelm.
#14
Hi Chris,

right now i'm surfing the code to get an idea of implementing the full cutting marks support.

For this feature, i need the following behaviour:
from any state,

  • jump to a specific location in the recording (no problem, using switchState(S_JUMP, newFrame))
  • switch to pause mode (no problem, either with switchState(S_PAUSE_P))
  • and then update the video on screen <- there is my problem

something stupid like player->jumpToMark(nextMark); player->play(); player->pause(); does not work.

could you give me some hints on how to make this work?

btw: could you tell me the difference between S_PAUSE_P and S_PAUSE_I ?

thank you (oh, and happy new year),
Friedhelm.
#15
VOMP General / MVP / Re: cutting marks for 0.2.5
December 13, 2006, 16:57:31
Quote from: Chris on December 13, 2006, 16:14:50
Cut marks support is now in CVS, thanks to macfly. It will be part of the next dongle release. If marks are found then yellow and blue will nagivate the marks, otherwise they will perform the regular 10s skip functions. Also, on new remotes the star and hash keys will now always be -10s and +10s skip also.

Cool!

in my next sparetime, i'll try to implement the discussed new features on marks (moving, set/unset, commands on recording, etc).

I really appreciate your Work!