On Thu, 2008-05-01 at 17:21 -0700, BJ Opp wrote:
> Hi there. Did you ever resolve your frame buffer issues? I'm having
> what seems to be a very similar problem working with the dm355 and a
> 240x400 LCD. Looking at all the video lines on a scope shows that I'm
> only getting about a 3rd of the
I am getting the following error when I try to build my just checked out
kernel.
drivers/net/b44.c: in function `b44_sync_dma_desc_for_device':
drivers/net/b44.c:151: error: implicit declaration of function
`dma_sync_single_range_for_device':
drivers/net/b44.c: in function `b44_sync_dma_desc_for_c
[EMAIL PROTECTED] wrote:
I am getting the following error when I try to build my just checked out
kernel.
drivers/net/b44.c: in function `b44_sync_dma_desc_for_device':
drivers/net/b44.c:151: error: implicit declaration of function
`dma_sync_single_range_for_device':
drivers/net/b44.c: in functi
Jon,
Thanks for the ideas. I had the same thoughts when I first saw the
problem pop up. I don't think it's a progressive/interlaced problem
though since the data dropping occurs every 3rd line. Nonetheless, I'll
check into that front one more time just to put it to bed.
Keep the thoughts com
FYI... DaVinci git now updated to 2.6.5, and in sync w/OMAP git as of
today.
Kevin
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Hi,
I am trying to compile davinci resizer driver as a module in montavista
kernel uImage.
what i am getting is (.o) file instead of (.ko) when i try to do insmod it
says not recognizable format.
I tried to compile the driver as static but when i boot the uImage there is
specific char device in /