Re: Alignment trap problem

and the software seems to be too much. You should try post-mortem debugging with core dumps instead. regards, matthias -- * Matthias Welwarsky Project Manager Software Germany * This email and any files

Re: dma_alloc_coherent() failed in davincifb.c

(), but this is only allocating sized 2^n blocks of memory. So dma_alloc_coherent() allocates the next bigger 2^n block and then free's the excess pages one by one. That isn't really helping with keeping the memory pool in shape. -- * Matthias Welwarsky Project Manager Software Germany

Re: DC5 output level?

://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- * Matthias Welwarsky Project Manager Software Germany * This email and any files transmitted with it are confidential and are intended solely

Re: List Admins: please set correct Reply-To: header

if everyone is disciplined enough, my inbox will fill with mails I already received from the list. regards, matthias ps. If you intend to reply to this email, please make sure that it goes to the list and not to my address. I like my inbox nice and tidy. -- * Matthias Welwarsky Project Manager

Re: resizer demo output

. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- * Matthias Welwarsky Project Manager

Re: Translating kernel virtual address to physical address

://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- * Matthias Welwarsky Project Manager Software Germany * This email and any files transmitted with it are confidential and are intended

Re: DM6446 Resizer problem

Anthony P. Lannutti wrote: So, I have: RegisterValue --- - RSZ_CNT.HRSZ (hrsz) 256 RSZ_CNT.VRSZ (vrsz) 256 That should be: RSZ_CNT.HRSZ = 256-1 RSZ_CNT.VRSZ = 256-1 I think you need to subtract 1 from the computed resize factors. -- * Matthias

Re: mmap issue

of bytes I intend to write out? Yes. The page size doesn't have an influence on this anyway. It's an MMU thing, not a cache thing. Thanks. Regards, Andy - Original Message From: Matthias Welwarsky [EMAIL PROTECTED] To: Andy Ngo [EMAIL PROTECTED] Cc: davinci-linux-open-source

Re: mmap issue

Andy, opening /dev/mem O_RDWR|O_SYNC should be enough to map the region uncached and with the write buffer disabled. In that case, every read and write into the memory mapped region directly translates into a CPU access to the respective physical address. No need to call msync before or after.

Re: mmap issue

___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- * Matthias Welwarsky Project Manager Software Germany

Re: mmap issue

; return 0; } have a look at the function uncached_access in the same file. You'll see that it returns 1 for O_SYNC, so it should work as is suggested. regards, matthias Matthias Welwarsky wrote: Andy Ngo wrote: Thanks, but how do I set the range uncacheable? I don't see such an option

Re: GPIO interrupts in kernel 2.6.10

___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- * Matthias Welwarsky Project Manager Software Germany