Post deleted by Toxic[Q]

[Ronaldd]

Citaat:

The transfer via ethernet works with BOOTP and TFTP. The BOOTP server must indicate the filename of the "os" file and the TFTP server must serve this file to the bootloader. I did not get this to work because all the BOOTP servers I tried failed on my Windows2000. Ok, back to Linux...

With Linux it is very simple to boot over network, I have a working configuration with 'ISC DHCP server' and an TFTP server which are part of my suse linux installation(8.0). If you want settings for 'ISC DHCP server' let me know, it needs only a few settings.

On this moment I only tried to boot the 'os' file from orignal images I did not yet try to compile mu own kernel.

Ronald

[Gast]

@Ronaldd

 

I got it working now. Damn nice <img src="/ubbthreads/images/graemlins/smile.gif" alt="" /> I use Mandrake on my PC and for tftp you need to install an extra tftp-server package. This server is integrated in xinetd. For bootp I used a bootpd package from another distro that I found via rpmfind.net.

 

Soon I will try compiling a new kernel. But since I'm missing a lot of patches this approach will not get me far at this time. I'm thinking of patching the existing kernel image. Patching a kernel image is not a trivial procedure since the build of a kernel image is quite complex: some tricky linker script adding all stuff together. With all stuff being: the compressed kernel itself, the kernel loader code, ... .

 

I already managed to decompress part from the os file to get the original decompressed kernel. So that kernel is ready to be patched. But putting it back into an "os" file ready to be used, is not easy. I'm thinking of "injecting" it in the correct place of the kernel image build process to achieve this. And at the same time hope dream didn't need to patch anything at that level <img src="/ubbthreads/images/graemlins/wink.gif" alt="" />

 

I'm probably not the only one that didn't find the "redwood5" option in the 2.4 kernel source. But I did find it in the latest 2.5 sources. So I will be using that one.

 

If dream is ever planning on releasing its patches, now would be a good time... I can already name one thing that would be interesting for other users on this forum: register the flash card on another ide device than the HD.

 

Greetz

[Ronaldd]

@mcduff

 

With a hex-editor id did cut the 'os' file into 3 parts a header, compressed kernel, trailer. The header is everything before the compressed kernel the trailer is everything after the compressed kernel.

 

I did a recompress (compress level 9) of the compressed kernel with a smaller name I used k.gz as kernel name dream used vmlinux.gz as kernel name and concatonated the three files again. The result was a 5 byte smaller os file. When I boot this file I have a working DB and enigma. When I recompress with compress level 8 I get a 'kernel oops'. (os file 79 bytes longer)

 

I think if you want to boot a custom 'os' file you need the 'os' packager program that dream uses to create this file.

 

Ronald

[Gast]

@Ronaldd

 

Citaat:

I think if you want to boot a custom 'os' file you need the 'os' packager program that dream uses to create this file.

 

I think this 'os' packager program is simply part of the kernel build process and can be found in the makefiles. I have seen several makefiles in the ./arch/ppc directory that generate zImage files. I just need the right one. Probably the one used when you select 40x CPU and redwood5.

 

Greetz

[Gast]

@all *kernel* developers,

 

I can confirm what I said in my previous message to Ronaldd. After some serious fiddling I finally got my own bootable "os" file. It contains the same kernel as the original "os" file from dream but it is packaged with a kernel image build process on my own PC.

 

What did I do?

1) Got kernel 2.5.52, set architecture to PPC

2) make config and set CPU 4xx and redwood5, for the rest of the options I didn't care. Why? I'm going to use the kernel from dream for now. I'm only interested in the "os" file generation process.

3) continue to do "make zImage" and adapt the config options until I finally got it to build with success

4) extract the kernel vmlinux from the original "os" file

5) gzip it again, but with compress level 4, giving a bigger compressed kernel. For fun and test.

6) insert it into the build process at the correct location:

./arch/ppc/boot/images/vmlinux.gz

7) make zImage again and voila I got myself a zImage.treeboot which can be used as the "os" file

 

The resulting "os" file was about 30 Kbyte bigger and it worked <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />

 

For the moment I had to disable CONFIG_SERIAL_CONSOLE because I did not yet figure out which serial port is used. So I can not yet see "uncompressing linux..." message and I cannot change the boot params.

 

Another important thing: see that you enable CONFIG_IBM_OPENBIOS. I had to enable it "manually" in all relevant files. I also needed to build mktree in ./arch/ppc/boot/utils manually. This tool is used in the final step of the "os" file generation process.

 

Greetz

[Romeo_]

why are you using a developerversion of the kernel and not the 2.4.x versions (STABLE) ??

[Gast]

@Romeo_

 

I use 2.5.x because I didn't find the redwood5 config option in the 2.4.x. Perhaps the dream guys use some patch? I have not looked around much for an answer. I just tried 2.5.x and it had redwood5 support. So it was good enough for me (for the moment).

 

Greetz

[Ronaldd]

@mcduff

 

Good work, I am goiing to try your procedure tonight or tommorow night.

 

Ronald

[Gast]

@Ronaldd

 

I've looked around for the linuxppc 2.4 devel version tmbinc was talking about. I found it at bitkeeper. This kernel version seems to have the redwood5 option. I will try this version soon.

 

Some info pointers:

You have to install bitkeeper in order to get the source.

 

Once it was installed I executed this command on my Mandrake system to get the kernel source:

bk clone http://ppc.bkbits.net/linuxppc_2_4_devel

It creates a copy of the whole repository on your system. Then you also need to execute this command in the root directory of the copied repository:

bk -r edit

Now you're ready to do the usual kernel build stuff.

 

For novices and interested people:

make xconfig

make dep

make zImage

... and probably a lot of kernel hacking...

 

Also interesting: here you can see the latest changes to the 2.4 devel kernel.

 

Greetz

 

It's getting pretty interesting...

 

[Gast]

@all kernel developers,

 

tmbinc has mailed me the diffs necessary to compile a working kernel plus a some other (kernel) information! Thanks dude <img src="/ubbthreads/images/graemlins/xyxthumbs.gif" alt="" />

 

Anyone interested in this information PM me with your email address. Please do not PM me when you are not planning on using the info or if you don't know anything about kernel development. I don't want my PM box to overflow for nothing <img src="/ubbthreads/images/graemlins/wink.gif" alt="" />

 

I've had a quick look and applied the patches to my bitkeeper checkout of the linuxppc 2_4_devel kernel. It compiled great and it also booted great <img src="/ubbthreads/images/graemlins/smile.gif" alt="" /> I only have a problem with the I2C driver. For some reason two files required by the patch (and required by the kernel and dream.o) are not present in my 2_4_devel kernel. I'll check this out later.

 

Thanks again tmbinc, I appreciate you releasing this information <img src="/ubbthreads/images/graemlins/xyxthumbs.gif" alt="" />

 

Greetz

 

[Gast]

@people interested in the kernel,

 

See here the mail (without attachments) from tmbinc.

===================

 

 

Please forward this mail to ronaldd and other interested developers.

 

 

The RAM Question: It's right that the box contains 64MB of ram. 32MB are available to Linux at this time. 16MB are used for the drivers, and 16 MB are unused yet. It's not enabled right now, because currently the drivers assume they have mem at 0x20000000, but the main Ram (used by

linux) starts at 0x00000000. We'll change that soon, but it requires major changes.

 

Enigma is running in 8bit mode because it doesn't need to be in 32bit and it's much faster that way. Historical reasons are the d-box2, which offers only 8bit at a reasonable performance.

 

I attached you some kernel diff (i hope they apply, i'm still a bit uncomfortable with bk). dreambox.c is for drivers/mtd/maps/.

 

I also attached a .config.

 

I also attached sourcecode for the old, RC-5 based dreambox rc (which isn't available in stores <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />, but together with ir-hw.h you should be able to receive arbitrary IR commands.

 

Feel free to share this code with anyone. (OK, they're GPLed, so you have to <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />).

Please note that drivers are closed source, however we can talk about anything not directly hardware related. We just can't open sources for parts speaking with the ibm parts of the chip. sorry.

 

 

'bout the IR code: should be self explaining, youre registering thehandler, getting "ir_event"s with timediff, they are falling-edge to falling-edge (or was it raising-to-raising?) please note that it's not possible to capture both edges, and modifying WHICH edge you capture would break the other driver. If this is REALLY a problem, there's of course a way to solve it (switch the capture mode

on every trigger...), but i'd like to keep it that way.

 

clockbase is the usual 27MHz/2, in case you wonder.

 

about booting via network: right now you can't change the default boot (it's always flash, if flash is empty (no cramfs found), it's network), but you can change it using a serial console.. (press '2', '2', '0'), and have a bootp server. you can supply the name of the kernel using

bootp. a sample entry in the bootptab would be:

 

dream:bf=/dbox2/tftpboot/dreamkernel:ha=00093400004b:ip=10.0.0.82:sa=10.0.0.77

 

you can use dhcp, too.

 

the kernel file has a "treeboot" header, and is generated by the

"mktreeboot" util, which is part of linux. with the correct

configuration, "make zImage" and have an

arch/ppc/boot/image/zImage.treeboot which is a valid "os" file.

 

I like the idea of establishing some sort of development website. Maybe we start either in a new forum (english only, please) or we might start collecting information in my wiki:

http://www.dream-multimedia-tv.de/tmbinc/phpwiki/index.php/Dreambox

(feel free to add, edit or remove stuff using the "edit" button <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />

 

hope this helps.

 

bye,

felix

 

[Gast]

Hoi McDuff,

 

Ik ken jammer genoeg zelf niks van programmeren, maar als ik deze info zo lees, denk ik dat hier nog leuke dingen gaan uit voortvloeien... <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />

 

Ik denk nu aan die RC5 IR code. Hier zou bvb een programma mee kunnen gemaakt worden dat "alternatieve" IR codes ontvangt (In de Pronto kan je die rechtstreeks ingeven) en via een cfg file commandos of scripts kan uitvoeren.

Als iemand zich geroepen voelt voor een nieuwe uitdaging... <img src="/ubbthreads/images/graemlins/wink.gif" alt="" />

[Ronaldd]

mcduff,

 

I applied diff, also 2 file missing. Kernel build went fine. I can also boots over the network only the new kernel is version 2.4.21pre4 and drivers are compiled for version 2.4.19rc3 so these driver are refused to load into kernel. I also tried a force load (insmod -f) but that gives a kernel oops.

 

Wat did you do? Did you checkout an older release of the kernel (2.14.19rc3??) or did you binary patch dream.o( and other drivers)?

 

In the mean time I only repackaged the original 'os' file with parameters so it can boot via network without have to use serial console. so new images are easyer to test (repackage kernel and uncram into filesystem)

 

Ronald

[Gast]

@Ronaldd,

 

I have the same problem i.e. I also get the kernel oops. About those two files: it seems that a new file (i2c-ibm_iic.c) has replaced the two files in question. I guess you need to apply the (two) patches "manually" to the new unified driver and hope that it works. I do not have enough time now to try it out. I'll probably check it out in the weekend.

 

Greetz

[Romeo_]

just a question : is there a vss plugin or something to use m$ VSS on windows instead of CVS on linux for check in/outs ??

(I know CVS + vi rocks allways.. the question is just meant to get my windows friends behind dreambox patching/development)