On Thu, Mar 04, 2010 at 08:15:27PM +0100, ext m...@felipebalbi.com wrote:
Hi,
On Thu, 4 Mar 2010 18:33:15 +0530, "Gadiyar, Anand"
wrote:
This patch fixes that for the ehci_hdc_omap_platform_data.
should be ehci_hcd_omap_platform_data ;)
BTW, this breaks compile for omap3-evm.
Could you ple
> -Original Message-
> From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
> Sent: Thursday, March 04, 2010 9:45 PM
> To: Hiremath, Vaibhav
> Cc: ext stanley.miao; linux-fbdev-de...@lists.sourceforge.net; linux-
> o...@vger.kernel.org
> Subject: RE: vdds_dsi doesn't exist on all omap343
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Thursday, March 04, 2010 11:03 PM
> To: Gupta, Ajay Kumar
> Cc: linux-omap@vger.kernel.org
> Subject: Re: usb_nop_xceiv_register() missing when OTG built as modules
>
> "Gupta, Ajay Kumar" writes:
>
>
>From 1d7f5d634176be558d5a60e26ee2bdeddffd7d3b Mon Sep 17 00:00:00 2001
From: Cris Jansson
Date: Thu, 25 Feb 2010 11:38:23 -0600
Subject: [PATCH] DSPBRIDGE: MMU-Fault debugging enhancements
These changes allow for DSP task information to be printed
by the MPU dspbridge when DSP MMU fault ocurrs.
Thursday 04 March 2010 07:49:57 Jarkko Nikula napisał(a):
> On Tue, 23 Feb 2010 16:50:38 +0100
>
> Janusz Krzysztofik wrote:
> > The MsBSP register cache will never have any error/status flags set,
> > since these flags are never written to the reg_cache. So it is kind of
> > not necessary to clea
Hi,
On Thu, 4 Mar 2010 18:33:15 +0530, "Gadiyar, Anand"
wrote:
>> This patch fixes that for the ehci_hdc_omap_platform_data.
>>
>
> should be ehci_hcd_omap_platform_data ;)
>
> BTW, this breaks compile for omap3-evm.
> Could you please build with omap3_defconfig and check.
will do first thing
"Gupta, Ajay Kumar" writes:
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Thursday, March 04, 2010 5:39 AM
>> To: linux-omap@vger.kernel.org
>> Subject: usb_nop_xceiv_register() missing when
The register DMA4_CDAC needs to be initialized to zero
before starting DMA transfer.
Cc: Tony Lindgren
Cc: Santosh Shilimkar
Cc: Govindraj R
Cc: Kevin Hilman
Reported-by:S, Venkatraman
Signed-off-by: Manjunatha GK
---
It was aligned to reset CDAC to zero in omap_start_dma(int lch)
instead of
On Thu, 2010-03-04 at 17:00 +0100, ext Hiremath, Vaibhav wrote:
> > -Original Message-
> > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > ow...@vger.kernel.org] On Behalf Of Tomi Valkeinen
> > Sent: Thursday, March 04, 2010 4:07 PM
> > To: ext stanley.miao
> > Cc: linux-fbde
For me also works, thanks
Best regards,
Enric
2010/3/4 Tomi Valkeinen :
> On Thu, 2010-03-04 at 16:25 +0100, ext Enric Balletbò i Serra wrote:
>> Hello,
>>
>> Testing the Linux Omap master branch on IGEP v2 board I get this feature
>>
>> [ 17.565155] omapfb omapfb: cannot parse default modes
>
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tomi Valkeinen
> Sent: Thursday, March 04, 2010 4:07 PM
> To: ext stanley.miao
> Cc: linux-fbdev-de...@lists.sourceforge.net; linux-omap@vger.kernel.org
> Subject: Re: vd
On Thu, 2010-03-04 at 16:25 +0100, ext Enric Balletbò i Serra wrote:
> Hello,
>
> Testing the Linux Omap master branch on IGEP v2 board I get this feature
>
> [ 17.565155] omapfb omapfb: cannot parse default modes
>
> My kernel command line is something like '..
> omapfb.mode=dvi:1280x720mr..
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Enric Balletbò i Serra
> Sent: Thursday, March 04, 2010 8:55 PM
> To: Tomi Valkeinen
> Cc: linux-omap@vger.kernel.org
> Subject: OMAPFB: cannot parse default modes
>
> H
Hello,
Testing the Linux Omap master branch on IGEP v2 board I get this feature
[ 17.565155] omapfb omapfb: cannot parse default modes
My kernel command line is something like '..
omapfb.mode=dvi:1280x720mr...@60' which works without problems with
latest 2.6.33-rc8. Any idea about this ? Ther
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of
> Gadiyar, Anand
> Sent: Thursday, March 04, 2010 7:37 PM
> To: Linux OMAP Mailing List; Tony Lindgren
> Subject: mainline - build breaks with omap3_defconfig
>
> Hi,
>
Hi,
Felipe already reported one issue with the board-omap3touchbook.c
causing a build break. After working around that, there's another
build break when compiling the 4430SDP board file.
CC arch/arm/mach-omap2/board-4430sdp.o
/tmp/cc7lJWsG.s: Assembler messages:
/tmp/cc7lJWsG.s:45: Error:
On Tue, Mar 02, 2010 at 07:36:59PM +0100, Syrjala Ville (Nokia-D/Helsinki)
wrote:
> From: Ville Syrjälä
>
> Separate the memory region from the framebuffer device a little bit.
> It's now possible to select the memory region used by the framebuffer
> device using the new source_idx parameter of
felipe.ba...@nokia.com wrote:
>
> From: Felipe Balbi
>
> the early_param() call in board-omap3touchbook.c expands to:
>
> static const char __setup_str_early_touchbook_revision[]
> __section(.init.rodata) _aligned(1) = tbr;
> [...]
>
> and we have a non-const variable being added to the
This time CC'ing Linux-serial and LKML too, forgot last time.
--
Govindraj.R
This patch adds driver support for OMAP3/4 high speed UART.
This driver is made separate from 8250 driver as we cannot
over load 8250 driver with omap platform specific configuration for
features like DMA, it makes eas
This patch adds driver support for OMAP3/4 high speed UART.
This driver is made separate from 8250 driver as we cannot
over load 8250 driver with omap platform specific configuration for
features like DMA, it makes easier to implement features like DMA and
hardware flow control and software flow c
Hi,
On Thu, 2010-03-04 at 11:29 +0100, ext stanley.miao wrote:
> Hi, Tomi,
>
> The commit below:
> http://www.gitorious.org/linux-omap-dss2/linux/commit/ec70668fa99b2dd0d305fbdb451a728f2e2a4c58
> doesn't apply to ti_omap_am3517. There is no "vdds_dsi" on am3517.
DSS hardware seems to require vdd
Hi, Tomi,
The commit below:
http://www.gitorious.org/linux-omap-dss2/linux/commit/ec70668fa99b2dd0d305fbdb451a728f2e2a4c58
doesn't apply to ti_omap_am3517. There is no "vdds_dsi" on am3517.
Stanley.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a messag
22 matches
Mail list logo
