On Thu, Aug 27, 2009 at 7:36 PM, Maxime Petazzonimpetazz...@mvista.com wrote:
Hi,
* Pandita, Vikram vikram.pand...@ti.com [2009-08-27 19:16:27]:
Why?
I know of an implementation by Vimal Singh that introduces a common
flash file for Zoom1 and Zoom2.
There is reuse of code there.
Thanks
On 08/31/2009 06:55 PM, Tony Lindgren wrote:
* Hiremath, Vaibhavhvaib...@ti.com [090831 07:44]:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Syed Mohammed, Khasim
Sent: Monday, August 31, 2009 8:11 PM
To: Steve
* vimal singh vimal.neww...@gmail.com [2009-09-01 12:34:26]:
Yes, I am aware of the mtdparts command line arguments, which works
great. I think a default, sensible partition layout for the Zoom2
would be nice though.
I agree. Keeping it in the mind that mtdparts command line arguments
On Tue, Sep 1, 2009 at 12:42 PM, Maxime Petazzonimpetazz...@mvista.com wrote:
* vimal singh vimal.neww...@gmail.com [2009-09-01 12:34:26]:
Yes, I am aware of the mtdparts command line arguments, which works
great. I think a default, sensible partition layout for the Zoom2
would be nice
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Theoretically list could be deleted before we go into the for loop.
Additionally we could delete list immediately if it becomes empty.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
---
drivers/dsp/bridge/rmgr/drv.c |9
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Check list pointer at every itteration because it could be deleted before we go
into the for loop.
Reworked version of the previous attempts.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
---
drivers/dsp/bridge/rmgr/drv.c |
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
- Remove LST_Init() and LST_Exit() calls because they are doing nothing except
tracing, Thus, remove tracing as well.
- Remove DBC_* calls. It's internal kernel business whether to have those
assertions.
- Switch to list_head structure
This patch series adds flash support for NAND (in sdp, zoom2 and ldp),
OneNAND and NOR (in sdp).
[PATCH 1/2] OMAP2/3: Add support for flash on SDP boards
[PATCH 2/2] OMAP3: Add support for NAND on ZOOM2/LDP boards
These patches were submitted earlier too.. But putting them in a single
list now.
Add support for flash on SDP boards. NAND, NOR and OneNAND
are supported.
Only tested on 3430SDP (ES2 and ES3.1), somebody please test on
2430SDP and check the chips select for 2430SDP.
Also note that:
For OneNAND: in the earlier 2430SDP code the kernel partition
was set to only 1MB instead of
Adding NAND support for ZOOM2 and LDP board. I have tested it for ZOOM2
boards, someone can verify it for LDP, hopefully it should not have any
problem.
The size of the U-Boot environment partition was increased to 1.25MB.
Singned-off-by: Vimal Singh vimalsi...@ti.com
---
- Original Message -
From: S, Venkatraman svenk...@ti.com
To: linux-omap@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org; Shilimkar, Santosh
santosh.shilim...@ti.com
Sent: Thursday, August 27, 2009 4:41 PM
Subject: [PATCH v2][RFC] OMAP4: sDMA driver: descriptor autoloading
Hi all,
I've recently started to work on adding support for a custom OMAP3 board.
Several things in the arch/arm/mach-omap2/board-* caught my attention:
1) omap_xxx_map_io and omap_xxx_init_irq are mostly the same in all board-*
files, the only difference is omap_sdrc_params passed to
2009/8/27 Matthias Schwarz matthias.s...@googlemail.com:
Hi all,
i just wondered how the camera interface's, especially the previewer
module's CFA coefficients are setup on OMAP3530.
The TRM also does not give too much information about it:
In the generic mode, CFA interpolation is
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
* Use native list_empty() method instead of LST_IsEmpty() inside list.c. Remove
extra local variables.
* Move methods from list.c as inline functions in the list.h. Get rid of list.c
at all.
* Use list_head natively instead of LST_ELEM in
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
* Remove LST_Init() and LST_Exit() calls because they are doing nothing except
tracing, Thus, remove tracing as well.
* Remove DBC_* calls. It's internal kernel business whether to have those
assertions.
* Switch to list_head structure
Hello.
Here are two patches which change driver's own circular linked list
implementation to native one in linux kernel. The initial idea was come from
Hiroshi Doyu.
P.S. Please, ignore mail with 'Message-ID:
1251793647-14569-1-git-send-email-andy.shevche...@gmail.com'
--
With Best Regards,
What are the options to have USB Host support on the normal
USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I
upgraded to the latest kernel :-(
n.b. OTG host and gadget still work fine.
Thanks
--
On 09/01/2009 05:42 AM, Gary Thomas wrote:
What are the options to have USB Host support on the normal
USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I
upgraded to the latest kernel :-(
n.b. OTG host and gadget still work fine.
Thanks
Santosh,
-Original Message-
From: Shilimkar, Santosh
Sent: Monday, August 31, 2009 11:41 PM
To: S, Venkatraman; linux-omap@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Subject: RE: [PATCH v2][RFC] OMAP4: sDMA driver: descriptor
autoloading feature
2) Pause /
Hi,
Current DSPBridge MPU side API provides following IOCTLs which are related to
reserving and mapping DSP address space:
1. DSPProcessor_ReserveMemory(): Reserve a virtually contiguous region of DSP
address space.
2. DSPProcessor_Map(): Maps an MPU buffer to the DSP virtual address space.
On Fri, Aug 28, 2009 at 7:35 PM, Alan Coxa...@lxorguk.ukuu.org.uk wrote:
+#define UART_BASE(uart_no) (uart_no == UART1) ? OMAP_UART1_BASE :\
+ (uart_no == UART2) ? OMAP_UART2_BASE :\
+ OMAP_UART3_BASE
Would be
Govindraj
From: Govindraj R govindraj.r...@ti.com
This patch adds support for OMAP3430-HIGH SPEED UART Controller.
It currently adds support for the following features.
1. Supports Interrupt Mode for all three UARTs on SDP/ZOOM2.
2. Supports DMA Mode for all three UARTs on
govindraj
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of
Govindraj
Sent: Tuesday, September 01, 2009 2:14 AM
To: HU TAO-TGHK48
Cc: vimal singh; linux-omap@vger.kernel.org; LKML;
linux-ser...@vger.kernel.org; Ye
On 09/01/2009 04:35 PM, Ameya Palande wrote:
Current approach has following problems:
0. It is brain-dead.
1. Caller has to perform 4 system calls in order to map and unmap a buffer.
2. Kernel has no idea about the type of buffer (input/output). So depending
on buffer type caller has to
* Artem Bityutskiy dedeki...@gmail.com [090901 00:11]:
On 08/31/2009 06:55 PM, Tony Lindgren wrote:
* Hiremath, Vaibhavhvaib...@ti.com [090831 07:44]:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Syed Mohammed,
On Tue, Sep 01, 2009 at 02:20:13PM +0200, ext Gary Thomas wrote:
Following up on this, I made sure that CONFIG_USB_EHCI_HCD was defined.
Now I see these messages:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Clock usbhost_48m_fck didn't enable in 10 tries
On Tue, Sep 1, 2009 at 4:42 AM, Gary Thomasg...@mlbassoc.com wrote:
What are the options to have USB Host support on the normal
USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I
upgraded to the latest kernel :-(
I had the same experience with
On 09/01/2009 12:14 PM, Steve Sakoman wrote:
On Tue, Sep 1, 2009 at 4:42 AM, Gary Thomasg...@mlbassoc.com wrote:
What are the options to have USB Host support on the normal
USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I
upgraded to the latest
Enable USB power, use correct gpio for usb_ehci_init
Signed-off-by: Steve Sakoman st...@sakoman.com
---
arch/arm/mach-omap2/board-omap3beagle.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of
Sripathy, Vishwanath
Subject: RE: [PATCH][RFC] OMAP3: PM: Adding OSWR support
OSWR stands for Open Switch With Retention.
This is one of the target power states
Sripathy, Vishwanath wrote:
OSWR stands for Open Switch With Retention.
Not to split hairs, but the OMAP3430 Technical Reference Manual states
that OSwR means Open Switch Retention. So no with. This W always
bother me too!
Cheers
Jon
--
To unsubscribe from this list: send the line
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Felipe Balbi
Sent: Tuesday, September 01, 2009 9:58 PM
To: ext Gary Thomas
Cc: linux-omap@vger.kernel.org; Paul Walmsley
Subject: Re: USB confusion
On Tue, Sep 01,
Hi,
I am working on omap3430,linux 2.6.29 kernel.I am using USB3320
transceiver.I have configured the ehci module. My problem is the USB1
clk is not generating.The mux configuration has done properly. can
anyone guide me the steps i have to look.
Regards and Thanks
Thomas Scariah
--
To
33 matches
Mail list logo