how to implement and use the Software Booting Configuration Structure in OMAP3530

0x48002910 supposed to be a pointer to the SW Booting Config Structure or the start of the structure itself? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.

MMC retry after DATA CRC error

MMC. I'm using OMAP 3530 silicon rev 3.1 so it shouldn't be the old errata that TI has published - though it seems very similar. Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org Mor

Re: how to configure android-2.6.27 kernel for an LCD display other than Zoom2 display

On Tue, May 19, 2009 at 8:17 AM, twebb wrote: > On Fri, May 15, 2009 at 3:18 PM, twebb wrote: >> I'm using the L25.6/android-2.6.27 kernel and am adapting it as >> necessary to OMAP3530-based hardware.  However, I don't see how to >> configure the kernel for an

Re: how to configure android-2.6.27 kernel for an LCD display other than Zoom2 display

On Fri, May 15, 2009 at 3:18 PM, twebb wrote: > I'm using the L25.6/android-2.6.27 kernel and am adapting it as > necessary to OMAP3530-based hardware.  However, I don't see how to > configure the kernel for an LCD display other than the NEC display > defined for ZOOM2

how to configure android-2.6.27 kernel for an LCD display other than Zoom2 display

rking on it for now. How can I configure the kernel to support a non-SPI-based LCD panel? How does this DSS differ with what appears in android-2.6.29/drivers/video/omap2 ? Any help here would be appreciated. Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-oma

OMAP MMC1/2/3, PM, DSS support

would a kernel from the linux-omap git (http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary) be better? The MMC implementations between the two seem quite different. Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the

Re: usb-to-eth dongle on usb ehci host port

d > Here are portions of output from kernel startup. It does look like it recognizes it ("REALTEK USB 10/100 LAN"), but how to tell if it recognizes it specifically as a eth adaptor? twebb ... usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_e

usb-to-eth dongle on usb ehci host port

I'm missing. Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

trouble with alsa, wolfson, and TI OMAP35xx McBSP

ideas what might be going wrong here? Traces for codec reg dump and mcbsp are attached. Thanks, twebb omap2_dma_handle_ch: new DMA IRQ for lch 0 WM8978 registers 0:0 1: 1fd 2: 1bf 3: 1ef 4: 10 5:0 6: 16d 7:0 8:0 9:0 a: 40 b: ff c: ff d:0 e: 100

Re: lcd rotation in omapfb_main.c

> > The L-O tree is already about 2.6.30, so you're essentially 3 > revisions out and you're just setting yourself up for a bunch of work > to port numerous changes into your Kernel. > > And as Greg KH would probably say, 5 months in Kernel development land > is a really long period of time. :) > >

Re: lcd rotation in omapfb_main.c

On Tue, Apr 21, 2009 at 6:29 PM, Marek Vasut wrote: > On Wednesday 22 of April 2009 00:18:54 twebb wrote: >> I'm trying to start up the LCD panel on a new omap35xx-based platform >> in portrait mode, though the native orientation of the display is >> landscape.  I&#x

lcd rotation in omapfb_main.c

erence in the orientation of the display. Any ideas why this might be happening? Could there be outstanding fixes/patches I need? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majord

LCD display orientation on omap

I'm working on an omap platform that has an LCD display which is native landscape. What can I do to make the application come up initially in portrait mode? Is this something that can be done in the omap FB driver, or is there some other preferred mechanism? Thanks, twebb -- To unsubscribe

omap3530 usb host problems follow-up

TL bit clearing as expected (according to the TRM), so your comment and suggested code change are puzzling. twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: ehci problem on OMAP35xx

On Thu, Apr 16, 2009 at 9:41 AM, Pandita, Vikram wrote: > >>> From: linux-omap-ow...@vger.kernel.org >>> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of twebb >>> Sent: Wednesday, April 15, 2009 9:35 PM >>> To: linux-omap@vger.kernel.org Mailing Lis

ehci problem on OMAP35xx

ity, so a few questions... 1. Any ideas why we'd see PORTSC_1[PO] = 1? 2. Any suggestions on debugging basic connectivity between 35xx EHCI controller and transceiver + hub? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a mess

Re: MMC2 support in linux-omap-2.6.27 (omap1)

On Thu, Mar 26, 2009 at 6:13 AM, Shankar Ganesh wrote: > > On Thu, Mar 26, 2009 at 2:16 PM, Adrian Hunter > wrote: >> >> twebb wrote: >>> >>> On Wed, Mar 25, 2009 at 10:13 AM, twebb wrote: >>>> >>>> I'm currently using linu

Re: MMC2 support in linux-omap-2.6.27 (omap1)

On Wed, Mar 25, 2009 at 10:13 AM, twebb wrote: > I'm currently using linux-omap-2.6.27 (tag=omap1) and trying to add > MMC2 support.  I've back ported what I think I need from various files > inn l-o-2.6.28-omap1.  I will eventually move to 2.6.28-omap1 but for > now am tr

8-bit mode for OMAP MMC2

just can't find it? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

MMC2 support in linux-omap-2.6.27 (omap1)

K are enabled. Any ideas? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: mmc0 detection timing at kernel startup, linux-omap-2.6.27-omap1

On Fri, Mar 20, 2009 at 9:53 AM, Ashwin Bihari wrote: > On Fri, Mar 20, 2009 at 9:44 AM, Koen Kooi wrote: >> >> Op 20 mrt 2009, om 14:34 heeft Ashwin Bihari het volgende geschreven: >> >>> You need to add the Kernel option "rootdelay=1" to basically delay the >>> Kernel for a moment while attempt

mmc0 detection timing at kernel startup, linux-omap-2.6.27-omap1

deas? I'm including the good and bad kernel startup logs below... Thanks, twebb * Good * Linux version 2.6.27-omap1 (j...@jb) (gcc version 4.2.1 (CodeSourcery Source ry G++ Lite 2007q3-51)) #16 Thu Mar 19 16:59:31 EDT 2009 CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f Mac

Re: omap35x mmc support

> > For MMC3 this patch: > >   http://lkml.org/lkml/2009/1/27/101 > > seems to be missing. > Thanks. Would this patch be applicable whether MMC3 is functioning as SD or MMC or SDIO interface? And on a bit of a tangent (but relevant to the link you provided), what's the logic behind so many OMAP2

Re: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63

> > Well l-o tree is short for the linux-omap tree. Then I have various > queues of stuff going into the mainline kernel: > > omap-fixes > omap-upstream > omap1-upstream > omap2-upstream > omap3-upstream > ... > > Out of these queues omap-fixes will be sent out as needed during the > -rc cycle, whi

Re: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63

> > Sorry for the long delay with this. Pushing to l-o tree and > added to omap-fixes queue. > Probably understood by most of you, but what is the difference between "pushing to l-o tree" and "adding to omap-fixes queue"? What are the omap-fixes queued for if not the l-o tree? I'm trying to unde

MLC NAND support on OMAP35xx

Can anyone comment on the existence or status of MLC NAND support in the linux-omap kernel or even the mainline kernel? And would this support be built into YAFFS or into an mtd driver where other NAND (SLC) support resides? Thanks. -- To unsubscribe from this list: send the line "unsubscribe lin

Re: DVI output support for OMAP35x EVM

s link... http://lists-archives.org/video4linux/23648-omap3-display-driver-v4l2.html the best description of where TI is headed? And is code based on this only available in omapzoom git? Also, I don't see mention of the DVI support in the RFC - am I missing something? Thanks, twebb -- To un

DVI output support for OMAP35x EVM

6.27-omap1). Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

suggestions for latest code that offers best support of OMAP35x EVM

Not being very familiar with the kernel development process and git, I'm hoping someone can suggest which code from the l-o git offers the best support of the OMAP35x EVM. I'm guessing it would be the code tagged "v2.6.27-omap1" but I'm not sure. What's the general difference between tags "v2.6.2

android on omap, yaffs2 or init problem

id startup when mounting rootfs via NFS or JFFS2. And, when creating the android filesystem (per elinux.org's 'android on omap') should ramdisk.img instead be left in file form and used as an initrd image? I'm not very familiar with booting linux via initrd/initramfs. Thanks, tweb

Re: android on omap

has to do with permissions or the filesystem. One difference is that the emulator uses three different yaffs2 partitions (userdata, system, and cache) while I currently have all of these on a single partition. Any other ideas as to what might cause the ... E/dalvikvm-gc( 483): Could no

Re: android on omap

see this problem (though I do have other issues). Does the error E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack indicate a specific problem? Might there be a way to dump more specific/verbose output at startup to get a better understanding of what's wrong? Thanks, tw

Re: android on omap

le > configuring the kernel? > I've now moved filesystem to target (jffs2). Things are a little better, and different. Using logcat, I'm now seeing dalvikvm errors and warnings as shown below. Particularly odd since I wasn't seeing this error when rootfs was mounted via NFS

Re: [PATCH 0/0] Add minimal omap34xx support

ng for OMAP35x EVM support in mainline, but in l-o git. And it seems like that's where it's not often mentioned/tested against - but beagle, zoom, overo are. In looking for 35x support, is it wrong to focus on l-o git instead of mainline? Won't support always be in l-o first? Thank

Re: [PATCH 0/0] Add minimal omap34xx support

he beagle, overo, or omap3 sdp boards. Do TI and/or Mistal (maker of OMAP35x EVM) do any testing/verification of patches on the 35x EVM? Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

android on omap

ss 'zygote' restarts. When started with strace, I see the error output below. Can anyone make any sense of this error/exception? By the way, the target does not have network connectivity via USB, but does have it via ethernet. Might this be an issue? Thanks, twebb java.lang.Runtim

Re: OMAP34xx vs OMAP 35xx

but others say that linux-omap.git is the better place. Since neither works straight out of the git it's difficult for me to judge which is further along in it's support of 35x EVM. Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the bo

OMAP34xx vs OMAP 35xx

I'm relatively new to the list and hoping someone can clarify a few things. Does "OMAP3" imply support of both 34xx and 35xx? When the term "OMAP3 EVM" is used, does this mean OMAP3430 SDP only or does it include OMAP35x EVM? Thanks. twebb -- To unsubscribe from

Re: getting 2.6.25 from git to run on omap35x evm

v/mtdblock 4 rw rootfstype=jffs2 ip=192.168.1.200:192.168.1.123:192.168.1.2:255.255.255.0:: eth0:on Thanks, twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: getting 2.6.25 from git to run on omap35x evm

but can't be masked! TWL4030 module irq 369 is disabled but can't be masked! ... Though it sounds like no one is testing this code against a 35x EVM, I'm still hoping someone may have a clue about what is going wrong here. Thanks, twebb -- To unsubscribe from this list: send the

Re: getting 2.6.25 from git to run on omap35x evm

step is to get more towards the official L-O > tree.. > > Regards > ~ Ashwin > Great, that's helpful. Do you know omapzoom linux-2.6.25 to be somewhat functional with OMAP 35x EVM, or would you suggest going with something newer like v2.6.26-ti-07252008? Or must I go to 2.6.2

Re: getting 2.6.25 from git to run on omap35x evm

linux-2.6.22.18 (SDK 1.0.0) is from the linux-omap-2.6.git and when they might converge? Along these lines, which defconfig to use for OMAP35x EVM: SDK = omap3evm_defconfig or linux-omap-2.6.25 = omap3_evm_defconfig (different names and different contents)? Thanks. twebb -- To unsubscribe fro

getting 2.6.25 from git to run on omap35x evm

The OMAP35x EVM (from TI/Mistral) runs their SDK 1.0.0 which is based on linux-2.6.22.18. I'm trying to get linux-2.6.25 (tag = v2.6.25-omap1 from linux-omap-2.6.git) running on the 35x EVM but having difficulties. The linux-2.6.22.18 including support for OMAP 35x EVM appears quite different fro