changes

digidude

digidude

Sheep worrier.
VIP Member
Joined
Aug 8, 2001
Messages
24,754
Reaction score
3,741
Location
The edge.
spoke to TM today, and informed them that something has changed thats stopped the wifi from working, between the 28/10 image and saturday. just got home now and updated SVN here, and these are the files that have changed

Checked out revision 41.
digitalworldz@digitalworldz:~/tm800$ svn co svn://urfreelinux.homelinux.org/LinuxHD/trunk
U trunk/enigma2-pli-7260/lib/dvb/sec.cpp
U trunk/cdk/flashtools/files/auImage.stb225-nand-20100429-17-09-10-Debug
U trunk/cdk/flashtools/files/auImage.stb225-nand-20100429-17-09-10
U trunk/rootfs-overlay/default/etc/tuxbox/satellites.xml
U trunk/rootfs-overlay/default/var.tar.gz
U trunk/rootfs-overlay/install-20100429.sh
Checked out revision 46.
digitalworldz@digitalworldz:~/tm800$
 
Dude something id like to bring up about changes
the last few changes Ive made to bouquets,when I transfer them back to box I have to transfer the sat XML again as it get corrupt somewhere along the lines,then you have to config the tuner again
not a major hassle as such but a annoyance coz it never used to happen

any ideas about this anyone ?
 
I have reported the FTP in/out corruption to TM months ago, and again recently. No idea if anyone is taking it seriously.
 
todays changes have fixed the wifi, ive just compiled and this one sorted it out

@ fdlsys

if you email TM at [email protected] and put the subject something like DWteam SVN fix, itll get noticed and forwarded to be fixed at core level within the SVN, if its something you can fix, we may all be able to update out SVN files with it and have something unique ;)
 
doing my fkin nut in trying to checkout the dw svn

digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: Could not open the requested SVN filesystem
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: Could not open the requested SVN filesystem
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: OPTIONS of 'https://dwteam.svn.cvsdude.com/dwteam': authorisation failed: Could not authenticate to server: rejected Basic challenge (https://dwteam.svn.cvsdude.com)
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: OPTIONS of 'https://dwteam.svn.cvsdude.com/dwteam': authorisation failed: Could not authenticate to server: rejected Basic challenge (https://dwteam.svn.cvsdude.com)
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: Could not open the requested SVN filesystem
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: OPTIONS of 'https://dwteam.svn.cvsdude.com/dwteam': authorisation failed: Could not authenticate to server: rejected Basic challenge (https://dwteam.svn.cvsdude.com)
digitalworldz@digitalworldz:~/dwsvn$ svn co https://dwteam.svn.cvsdude.com/dwteam
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Password for 'digitalworldz':
Authentication realm: <https://dwteam.svn.cvsdude.com:443> dwteam login
Username: craigdigidude
Password for 'craigdigidude':
svn: Could not open the requested SVN filesystem
digitalworldz@digitalworldz:~/dwsvn$
 
After speaking with tm yesterday, theres now an update.log text file in the trunk folder, that lists changes, heres yesterdays changes, from the new log file

2010-11-08
frontend.cpp forntend.h idvb.h sec.cpp sec.h dvb.cpp dvb.h scan.cpp
1. update Latest OpenPli Code
2. DiSeQc Commad parameter bug fix(sec.cpp)
3. Etheret Up/Down Hangup bug fix(cdk/flashtools/files/auImage.stb225-nand-20100429-17-09-10)
4. Scan Speed Improved ( rootfs-overlayfiles-20100429-14-10-10.tar.gz)
5. USB Auto Mount bug fixed


and here from the actual SVN log

------------------------------------------------------------------------
r47 | miky | 2010-11-08 20:32:38 +0000 (Mon, 08 Nov 2010) | 1 line


------------------------------------------------------------------------
r46 | miky | 2010-11-08 16:19:29 +0000 (Mon, 08 Nov 2010) | 1 line


------------------------------------------------------------------------
r45 | mercury | 2010-11-08 15:09:26 +0000 (Mon, 08 Nov 2010) | 2 lines

update tp info

------------------------------------------------------------------------
r44 | mercury | 2010-11-08 15:08:00 +0000 (Mon, 08 Nov 2010) | 2 lines

update tp info

------------------------------------------------------------------------
r43 | theone | 2010-11-08 14:39:46 +0000 (Mon, 08 Nov 2010) | 1 line


------------------------------------------------------------------------
r42 | mercury | 2010-11-08 13:34:35 +0000 (Mon, 08 Nov 2010) | 2 lines

fixed scan bug




but AT LEAST NOW WITH THE TEXT FILE, WE WILL KNOW WHATS BEEN WORKED ON, AND WHAT TO LOOK AT FIRST AFTER DOWMLOADING UPDATES AND COMPILING

(EXCUSE CAPS, KEUBOARDS JUST DECIDED TO THROW A FIT???)
 
in my trunk folder, ive added a text file called digidude_changes, and started listing things as ive shown below, is this the right way to do it? is there a right way? or is it just for information

09-11-2010

1. added DW graphics to trunk/enigma1-pli-7260/data/skin_default/icons
2. replaced logo.jpg trunk/rootfs/boot & trunk/rootfs-overlay/boot
3. customised issue.net_TM800 trunk/rootfs-overlay/etc
4. customised issue.net trunk/rootfs/etc
5. trimmed all hashed lines out CCcam.cfg trunk/rootfs/etc

there is quite a bit more that ive done, mainly DW customisations, as when i try updating other things, i break it all and have to start again lol
 
Those comments that you see occasionally from milky, mercury, etc. are the ones that you provide at the time when you do a "commit" into the SVN repo.

You can do it one file at the time if you want to provide a specific comment per-file, or the whole bunch at the time with common comment.

Once committed, your comments appear for everyone that draws a "log" from SVN.

Personally, I think that the best is to provide a brief comment that identifies the type/reason for change, and then put detailed in-line comments inside the actual file(s) so that diff tools will display it together with code difference.
 
fdlsys said:
Those comments that you see occasionally from milky, mercury, etc. are the ones that you provide at the time when you do a "commit" into the SVN repo.

You can do it one file at the time if you want to provide a specific comment per-file, or the whole bunch at the time with common comment.

Once committed, your comments appear for everyone that draws a "log" from SVN.

Personally, I think that the best is to provide a brief comment that identifies the type/reason for change, and then put detailed in-line comments inside the actual file(s) so that diff tools will display it together with code difference.
Click to expand...


so if i edited a file that contained a single line, to customise the telnet login screen for example, how would i insert that into the file, as the file outputs everything within it onto the screen (i think), if it doesnt, would i put inside the file something like

#edited for DW customisation

as well as update the small text file ive created?
 
No, you can't put comments into all types of files, of course. But you can always provide the meaningfull "log-entry" comment on commit.
 
------------------------------------------------------------------------
r66 | mercury | 2010-11-09 19:26:30 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r65 | mercury | 2010-11-09 18:54:30 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r64 | mercury | 2010-11-09 18:52:37 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r63 | mercury | 2010-11-09 18:50:39 +0000 (Tue, 09 Nov 2010) | 2 lines

for tgs500, added new bootloader

------------------------------------------------------------------------
r62 | theone | 2010-11-09 18:40:47 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r61 | theone | 2010-11-09 18:39:51 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r60 | mercury | 2010-11-09 18:39:19 +0000 (Tue, 09 Nov 2010) | 2 lines

for only tgs400 and tgs500, added AVL2108 tunner

------------------------------------------------------------------------
r59 | theone | 2010-11-09 18:37:06 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r58 | theone | 2010-11-09 18:35:45 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r57 | mercury | 2010-11-09 18:32:26 +0000 (Tue, 09 Nov 2010) | 2 lines

remove space.. and fixed bug

------------------------------------------------------------------------
r56 | mercury | 2010-11-09 18:19:57 +0000 (Tue, 09 Nov 2010) | 2 lines

bugs

------------------------------------------------------------------------
r55 | mercury | 2010-11-09 18:10:49 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r54 | mercury | 2010-11-09 18:07:22 +0000 (Tue, 09 Nov 2010) | 2 lines

added tgs400 and tgs500 rcu

------------------------------------------------------------------------
r53 | mercury | 2010-11-09 18:05:55 +0000 (Tue, 09 Nov 2010) | 2 lines

for tgs400 and tgs500, added rcu type and rcu change funtion

------------------------------------------------------------------------
r52 | mercury | 2010-11-09 18:04:40 +0000 (Tue, 09 Nov 2010) | 2 lines

for tgs400 and tgs500 usb

------------------------------------------------------------------------
r51 | miky | 2010-11-09 17:28:56 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r50 | miky | 2010-11-09 17:26:23 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r49 | theone | 2010-11-09 15:59:11 +0000 (Tue, 09 Nov 2010) | 1 line


------------------------------------------------------------------------
r48 | theone | 2010-11-09 15:30:51 +0000 (Tue, 09 Nov 2010) | 1 line

these files were updated

U trunk/enigma2-pli-7260/lib/python/Screens/About.py
U trunk/enigma2-pli-7260/lib/python/Components/Harddisk.py
U trunk/enigma2-pli-7260/lib/gdi/dfb.cpp
U trunk/enigma2-pli-7260/lib/gdi/keymap.h
U trunk/enigma2-pli-7260/lib/dvb/sec.cpp
U trunk/enigma2-pli-7260/lib/dvb/dvb.h
U trunk/enigma2-pli-7260/lib/dvb/scan.cpp
U trunk/enigma2-pli-7260/lib/dvb/frontend.h
U trunk/enigma2-pli-7260/lib/dvb/idvb.h
U trunk/enigma2-pli-7260/lib/dvb/dvb.cpp
U trunk/enigma2-pli-7260/lib/dvb/frontend.cpp
U trunk/enigma2-pli-7260/lib/dvb/sec.h
U trunk/cdk/flashtools/maketgs500
A trunk/cdk/flashtools/files/u-boot-800.bin
A trunk/cdk/flashtools/files/nandbootloader-new.bin
A trunk/cdk/flashtools/files/u-boot-500.bin
U trunk/cdk/flashtools/maketm800
U trunk/update_log.txt
U trunk/rootfs-overlay/rootfs-overlayfiles-20100429-14-10-10.tar.gz
U trunk/rootfs-overlay/maketgs500
U trunk/rootfs-overlay/maketm800
U trunk/rootfs-overlay/usr/bin/enigma2.sh
U trunk/rootfs-overlay/etc/init.d/S91dvb.sh
U trunk/rootfs-overlay/etc/init.d/rcS
A trunk/rootfs-overlay/etc/init.d/S33fs.sh
U trunk/rootfs-overlay/etc/automount.sh
A trunk/rootfs-overlay/etc/automount_TGS500.sh
U trunk/rootfs-overlay/install-20100429.sh
Checked out revision 66.
digitalworldz@digitalworldz:~/tm800$

heres is the update log text file, ignore the date, its already tomorrow in korea ;)

2010-11-10
for tgs500 rcu
U rootfs-overlay/etc/init.d/S91dvb.sh
U enigma2-pli-7260/lib/python/Screens/About.py
U enigma2-pli-7260/lib/gdi/dfb.cpp
U enigma2-pli-7260/lib/gdi/keymap.h

for tgs500 new bootloader
Adding (bin) files/nandbootloader-new.bin
Adding (bin) files/u-boot-500.bin
Adding (bin) files/u-boot-800.bin
Sending maketgs500
Sending maketm800

2010-11-10
rootfs-overlay/maketgs500
rootfs-overlay/maketm800
rootfs-overlay/usr/bin/enigma2.sh
rootfs-overlay/etc/init.d/S91dvb.sh
rootfs-overlay/etc/init.d/rcS
rootfs-overlay/etc/init.d/S33fs.sh
rootfs-overlay/etc/automount.sh
rootfs-overlay/etc/automount_TGS500.sh
rootfs-overlay/install-20100429.sh
1. Modified usb function according to hardware type

------------------------------------------------------------------------------------------------------------------
2010-11-08
frontend.cpp forntend.h idvb.h sec.cpp sec.h dvb.cpp dvb.h scan.cpp
1. update Latest OpenPli Code
2. DiSeQc Commad parameter bug fix(sec.cpp)
3. Etheret Up/Down Hangup bug fix(cdk/flashtools/files/auImage.stb225-nand-20100429-17-09-10)
4. Scan Speed Improved ( rootfs-overlayfiles-20100429-14-10-10.tar.gz)
5. USB Auto Mount bug fixed

------------------------------------------------------------------------------------------------------------------
2010-11-09
code rollback -> rotor moving msg bug workground
we will next update
fntend.cpp frontend.h idvb.h sec.cpp sec.h scan.cpp idvb.h
 
Last edited:
I noticed... boyz are working hard on preparing the deployment of the same non-working image code to 2 new box models... ;)
 
fdlsys said:
I noticed... boyz are working hard on preparing the deployment of the same non-working image code to 2 new box models... ;)
Click to expand...

why fook up one thing, if you can use the same files to fook up even more lol

could it be worked out what files are needed for ONLY the TM800, and remove the rest? ive been deleting loads of stuff from my copy of the files, and looking back at the list of updated files i posted earlier, when i updated, after deleting loads of DM7025 files, it hasnt re downloaded them, and ive also sucessfully compiled an image, after deleting loads of files, and downloading URs updates

the resulting bin image files is still 60035136 bytes (57.3M) though, so im thinking theres multiple copies of the DMM files its calling, im still trying to learn the process of what it actually does while compiling, i see it takes files from an input folder, and then puts them into an output folder, and from these output folders, creates the image files

but deleting some files from the input folders corrupts the compiling process, as its calling on the missing files, from make files somewhere

its like trying to untangle a web, that keeps on moving and changing lol

theres default files for all of the DMM boxes that can run E2, and now also files being added for TGS receivers, we dont need any of that, but cant just find and delete it, as if its called on during the compiling, itll fail to create the image

so its back to the start again lol
 
2 more files added by ur for the tgs models, or one file replaced (i think)

anyway

ill upload a daily (or whenever i change something) image that consists of UR changes and the few DW mods im trying to implement for if anyone wants to have a try of things

Index of /Linux based receivers/Digitalworldz images/Beta

this is a hidden folder (or hidden from the main site anyway) and ill upload an image done this morning into there
 
------------------------------------------------------------------------
r76 | mercury | 2010-11-11 00:19:26 +0000 (Thu, 11 Nov 2010) | 2 lines

add rcu

------------------------------------------------------------------------
r75 | mercury | 2010-11-10 23:18:37 +0000 (Wed, 10 Nov 2010) | 1 line


------------------------------------------------------------------------
r74 | mercury | 2010-11-10 21:39:27 +0000 (Wed, 10 Nov 2010) | 1 line


------------------------------------------------------------------------
r73 | mercury | 2010-11-10 21:36:13 +0000 (Wed, 10 Nov 2010) | 1 line


------------------------------------------------------------------------
r72 | theone | 2010-11-10 17:56:31 +0000 (Wed, 10 Nov 2010) | 1 line


------------------------------------------------------------------------
r71 | theone | 2010-11-10 17:54:05 +0000 (Wed, 10 Nov 2010) | 1 line


------------------------------------------------------------------------
r70 | mercury | 2010-11-10 11:35:06 +0000 (Wed, 10 Nov 2010) | 1 line


U trunk/update_log.txt
U trunk/rootfs-overlay/bin/restore.sh
U trunk/rootfs-overlay/bin/backup.sh
U trunk/rootfs-overlay/etc/init.d/S91dvb.sh
U trunk/rootfs-overlay/etc/automount.sh
U trunk/rootfs-overlay/etc/automount_TGS500.sh
A trunk/rootfs-overlay/first_install
A trunk/rootfs-overlay/first_install/enigma2-plugin-channel.motorized-vhannibal09nov-motor_100707_all.ipk
A trunk/rootfs-overlay/first_install/install


2010-11-11
rootfs-overlay/etc/automount.sh
rootfs-overlay/etc/automount_TGS500.sh
1. fixed usb recognition bug when boot up

U rootfs-overlay/oin/restore.sh
U rootfs-overlay/bin/backup.sh
=> password and settings backup and restore , when firmware update(update_pr)
 
You must log in or register to reply here.

Similar threads

jammoboss
VU+ Duo Cant get MGcamd to work
Replies
3
Views
2K
jammoboss
jammoboss
digidude
Nfs and debug mode?
Replies
0
Views
70
digidude
digidude
V
VectorZ - report on setup and 29/03/2012 test
Replies
4
Views
2K
VectorZ
V
digidude
rebuilding linux kernels and more tutorials
Replies
12
Views
158
digidude
digidude
digidude
TM800-DWiQ-03-07-11 v2
Replies
14
Views
2K
Rat
Rat
Back
Top