Search found 264 matches

by DeadBeef
Tue Aug 12, 2008 7:09 pm
Forum: TAPs
Topic: TF5000 Display TAP
Replies: 834
Views: 208370

Since I don't even have enough time to add support for new system IDs I decided to remove the check. The updated version 1.53a is available here .

Regards,
DeadBeef
by DeadBeef
Mon Apr 21, 2008 7:24 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

tom3q wrote:I think that Gigaset modules were compiled with GCC 2.9.5, so you won't be able to succesfully load them under a kernel compiled with GCC 3.x, because of structure alignment problems. This will usually just cause a page fault.
It seems to have been compiled with egcs-1.1.2(2.91.66).
by DeadBeef
Sun Apr 20, 2008 6:13 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

You can try to set emma2_mpeg_mem to EMMA_LOWMEM_START and emma2_mpeg_mem_size to (EMMA_LOWMEM_END - EMMA_LOWMEM_START). You probably meant emma2_mpeg_mem_size = EMMA_LOWMEM_END - EMMA_MPEG_BASE; emma2_mpeg_mem = EMMA_MPEG_BASE; Loading Gigaset modules only worked for emma_rtos, emma_bios, emma_osd...
by DeadBeef
Sun Apr 20, 2008 2:34 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

Hmm, we already have some memory allocated for MPEG/DMA/etc. and it's done with a macro defining low memory (EMMA_LOW_MEM_START or something similar). And also i don't think that alloc_bootmem should be used in _setup() routine, because it's too late for it. It should be used rather in prom.c. I ju...
by DeadBeef
Sun Apr 20, 2008 11:10 am
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

I've got a very strange behavior when adding the following lines to the end of emma_setup(): emma2_mpeg_mem = alloc_bootmem(16*1024*1024); emma2_mpeg_mem_size = 16*1024*1024; printk("emma2_mpeg_mem = %08x\n",emma2_mpeg_mem); The kernel does not output anythi...
by DeadBeef
Sat Apr 12, 2008 10:58 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

SUCCESS!!! I found the root cause of the problem - the Linux loader TAP we all have used did not load the BSS: Once I removed the check if(s->sh_type == SHT_PROGBITS) in load_elf() transfers from disk stopped crashing the Toppy! I have to apologize. I made wrong conclusions. It is indeed the embedd...
by DeadBeef
Sat Apr 12, 2008 10:12 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

The .bss section should actually be not loaded but zeroed, but this is what you probably mean by "loading". At the time of writing I meant loading. But you are right - there is not data in .bss not even zeros. That is, the sections behind .bss have been copied to the specified location. A...
by DeadBeef
Sat Apr 12, 2008 2:45 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

SUCCESS!!! I found the root cause of the problem - the Linux loader TAP we all have used did not load the BSS: loading : vmlinux Discarding : 00000000+ 0 type=0 flags=0 .text : 00000800+16f0b8 bytes to mem: 80b00000+16f0b8 .fixup : 0016f8b8+ e78 bytes to mem&...
by DeadBeef
Sat Apr 12, 2008 2:18 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

Could you provide me a copy of your directory tree with busybox binaries? I would like to see whether it is more stable than mine.
by DeadBeef
Sat Apr 12, 2008 2:02 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

Maybe the Toppy firmware stores the data in wrong byte order? I don't see how it should be possible. The Toppy is configured for big endian. For performance reasons the firmware does not changes byte order of received DVB data. So the data must have been stored in big endian. Is it correct when rea...
by DeadBeef
Sat Apr 12, 2008 1:27 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

Maybe you have hda=bswap in the command line? There is no data corruption when using DMA so it seems that the endianess must be correct. I am not saying that the data is corrupted. It is just read with the wrong byte order. CPU does not perform any byte swapping (I checked on completion of DMA). Fo...
by DeadBeef
Sat Apr 12, 2008 1:13 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

The |= operation gets the value of EMMA_ZPIO_INT_STATUS_X, ORs it with the irq bit and writes that to the register. Shouldn't it just write the single bit to the register? They probably attempt to acknowledge the specified IRQ plus all bits set in the register. In the worst case some interrupts mig...
by DeadBeef
Sat Apr 12, 2008 12:35 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

There may be a problem with GPIO IRQ handling. arch/mips/emma/irq-emma.c contains some related code, but it seems unreliable to me: Why do you think it is unreliable? I found a way to run your kernel. The required changes are as follows: comment out *EMMA_ATA_IDE_CONTROL32 = 0x00000000; in emma_ide...
by DeadBeef
Fri Apr 11, 2008 10:57 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

I have tried a couple of values in the strap2 register - to no avail. The IDE interface/interrupt disappears as soon as any of the bits 0x20005 is set. I have also tried to change the IRQ source - no reaction. Another thing I've forgotten to test before was the byte order when reading user data from...
by DeadBeef
Fri Apr 11, 2008 7:17 pm
Forum: TAP and patch development
Topic: linux
Replies: 335
Views: 93092

Kaon's straps: NEC EMMA2 Version 4.1.0.3.0 Strap settings 0x00002d33 0x0020014b 0x00002d33 0x0020014f Bit 21 (bitmask 0x200000) means that the IDE controller is using SEP2 mode. I think that the IDE problem on Toppies is related to MPX mode, but i still don't know what exactly it is. There must be ...