Re: Benchmarking: POP flash vs. MMC?
Well, that's not what I would have expected - I would have thought reads on POP would have been faster than that, and cheaper - the SD being the same speed but less CPU is surprising. -- 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
Benchmarking: POP flash vs. MMC?
Has anybody done any benchmarking on POP flash read/write speeds (using JFFS2) vs. MMC/SDHC card access (using ext[234])? Or for that matter, has anybody done any playing around with using the execute in place function of JFFS2 to see if there is any over-all speed advantage (due to reduced pressure on the RAM) vs. loading into RAM? -- 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
Getting accelerated X server running
OK, I've managed to get the PowerVR driver compiled and loaded, created the appropriate /dev/ entry, and now when I try to run the Xsgx as supplied by the TI GFX SDK, I get the following: beagleboard:/usr/X11R6_SGX# bin/Xsgx PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4890, /USER/src/omap3-sgx/services4/srvkm/bridged/bridged_pvr_brid] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4890, /USER/src/omap3-sgx/services4/srvkm/bridged/bridged_pvr_brid] sgxScreenInit: ERROR - can't enumerate pvr2d devices Could not find the driver. Make sure that the powervr driver has been loaded Backtrace (1 deep): 0: bin/Xsgx [0x48038] Fatal server error: Segmentation fault caught Aborted beagleboard:/usr/X11R6_SGX# lsmod Module Size Used by omaplfb 8488 0 pvrsrvkm 292280 1 omaplfb ipv6 247228 24 beagleboard:/usr/X11R6_SGX# ls -la /dev/pvrsrvkm crw-r--r-- 1 root root 249, 0 2009-03-17 11:41 /dev/pvrsrvkm beagleboard:/usr/X11R6_SGX# - No other X server is running. This is all begin done as root, so I don't think there are permission issues. strace'ing the server shows that it opens the driver file, then attempts a couple of IOCTLs that fail. So, what am I missing? Is there some firmware/slushware/??? file that needs to be be made available to initialize the hardware? -- 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
OpenGL ES 2.0 support under DSS2 kernel?
Does anybody have any pointers on getting the kernel driver for the PowerVR OpenGL ES2.0 hardware working under the current Linux kernel with the DSS2 patches? I am trying to get accelerated X working in order to test if it will be able to do what I need to do. Currently the Xsgx X server won't work, as the drivers for the PowerVR graphics acceleration are missing from the DSS2 kernel, so that leaves me dead in the water. Just to be clear: I am *not* talking about power management, I am talking about the PowerVR graphic accelerator core for OpenGL support (yes, I am repeating my self redundantly, but I have had some people contact me who I think are confusing the two). -- 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
What did omap2_disp_get_dss morph into?
I am trying to get the TI accelerated video driver to build against the current DSS2 kernel image, and I think I am this close || to getting it to go, but I am missing a pair of functions: omap2_disp_get_dss and omap2_disp_put_dss. Obviously, they've changed into something else - what did they morph into? -- 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
DSS2 branch - what is the canonical server?
What GIT server is the canonical server for the DSS2 branch of the OMAP kernel? And are there any plans to bring those changes into the "main" OMAP kernel? -- 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
where is "struct constraint_id" defined?
I am trying to build the OMAP3 graphics kernel module against
2.6.29-rc7-omap1 (from GIT), and have been running into problems getting
it to build.
Two problems were pretty easy: the TI code was including "asm/resource.h"
and "asm/semaphore.h" rather than "linux/resource.h" and
"linux/semaphore.h".
Having made those changes, it builds all the way through to the TI
supplied "sysutils_linux.c", which barfs with :
In file included from
/space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils.c:28:
/space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:154:
error: variable 'cnstr_id_vdd2' has initializer but incomplete type
(and many other errors).
The problem line of the code is:
static struct constraint_id cnstr_id_vdd2 = {
and I cannot find a definition of "struct constraint_id" anywhere in the
kernel.
Has this been renamed, or moved, or am I looking in the wrong place?
--
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: Anyone built the kernel drivers for the PowerVR under linux-omap-2.6?
On Tue, 2009-03-03 at 13:30 +0100, Koen Kooi wrote: OK, I apologize in advance, but that statement has pricked the festering boil of my feelings about this matter, and I feel that I must address it. > Well, TI is using OE to build their new PSPs, your point is moot :) Not really - that assumes that OE becomes the new standard for all builds. The reason I don't use OE is that I could never get to where I could regenerate anything non-trivial (like Angstrom) due to errors in Bitbake and the various OE black magic^W^W"recipes". Attempting to work through the problems with the OE devs touched upon just about every pet peeve I have with Free Software projects: Me: "I cannot get this to build, here's what I am doing, here's the script I use to set the environment variables needed for OE, here's the errors I am getting." Them: "I don't like the fact that you are using this temporary environment variable to set these other variables." Me: "OOOKAAAY, but that variable is a temporary and has nothing to do with anything. It gets unset at the end of the script. As you can see, the variables OE needs are set correctly." Them: "I am going to fixate upon your use of this environment variable and not address the problem you are having, for I don't really understand how to fix your problem." Me: "GRRR. OK. Fine. I set all the variables BY HAND. Here is a transcript of my exact session. Here is THE SAME DAMN PROBLEM happening." Them #1: "I still don't like that you were using that temporary variable, and will ignore the fact that you aren't using it now." Them #2: "Oh, you are using the released version of Bitbake. Silly boy, that version is horribly busted. Go get the newest version from Subversion, because we feel that actually releasing fixed code is unnecessary if you have public access to your source code control system." Me: "OK, I removed the released version my distro vendor has, and installed the version from Subversion. Now it doesn't even run at all." Them: I am sorry, but I have tried, step by step, to follow the instructions on the OE site to reproduce Angstrom. They don't work for me. They are incomplete and incorrect, with many of the examples being demonstrably WRONG. I have tried to follow the instructions on the Angstrom site (which, BTW, are very different than the OE instructions). They, too, are incomplete and demonstrably wrong in many cases. Sorry, but I am NOT going to base MY project on something that I cannot get working after several WEEKS of effort to get working. Yes, I know "it works for me" for certain values of "me", but I cannot get it working under bog-standard Debian, so that doesn't help me. Don't get me wrong: I *love* Free Software. I've had far worse experiences with commercial software like pSOS, VxWorks, and Windows than this. But I do feel the "it's fixed in CVS, so it's FIXED: full stop" attitude is WRONG - if it isn't released it isn't fixed yet. I do feel that the various Rainman-like folks who will completely ignore the real problem to pick at an unrelated piece of lint (and thus lower the signal to noise ratio of the channel below usability) aren't helping. I feel the "this is broken in upstream, so we'll break out the duct tape here rather than trying to fix the upstream" mindset is antithetical to the idea of "Let's all SHARE the improvements". I am just trying to help improve things so that Free Software becomes better every day. The idea that I have to use a specific "vendor" for my project - be that vendor Microsoft or be that vendor OpenEmbedded - just because obvious issues aren't being fixed in a truly portable fashion is ABSURD. -- 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: Anyone built the kernel drivers for the PowerVR under linux-omap-2.6?
On Tue, 2009-03-03 at 08:32 +0100, Koen Kooi wrote: > In OpenEmbedded we have patches to a) get it to compile b) pick up > symbols so they actually insert and c) build against Tomi's DSS2 > > regards, For various reasons I am not using OpenEmbedded, and while I had looked at the OpenEmbedded pages I didn't immediately see how to apply what OE had done to my setup. It would be nice to have an explanation of what is needed that was a little less "apply this opaque magic" and more "these are the steps needed, in our environment this automates those steps." I would also assert that it would be better in the long term if the upstream maintainers (in this case TI) would correct the problems themselves rather than requiring somebody like OE to work around them. -- 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
Anyone built the kernel drivers for the PowerVR under linux-omap-2.6?
I'm trying to build the TI supplied Linux kernel driver modules for the PowerVR accelerator chip in the OMAP3. I have a GIT tree pulled from the linux-omap-2.6 tree, and a set of cross-compiler tools built and installed. I can build the kernel itself, but when I try to build the TI supplied code: 1) It references "asm/semaphore.h" rather than "linux/semaphore.h" - as asm/semaphore no longer exists in the code the build fails. I can work around that by creating a symlink to linux/semaphore.h. 2) It then references "asm/resources.h", which is ALSO gone. I'm guessing it needs "asm-generic/resources.h". 3) However, at that point the compile REALLY dies, with the code looking for "asm/arch/resources.h". If I link "arch/arm/include/asm" to "asm/arch", then I get a large number of errors: CC [M] /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysconfig.o CC [M] /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils.o In file included from /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils.c:28: /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:154: error: variable 'cnstr_id_vdd2' has initializer but incomplete type /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:155: error: unknown field 'type' specified in initializer /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:155: error: 'RES_OPP_CO' undeclared here (not in a function) So does anybody have an good advice on this? -- 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
Anyone get the TI/PowerVR stuff working?
Does anyone on the list have any experience getting the (unfortunately proprietary) PowerVR drivers for the OMAP3 working under Linux and X? I've registered with TI, and downloaded the SDKs for the ZOOM and SDP boards, and cannot work out how to integrate them into what I've built on my prototype. Also, I'm trying to get the DSP bridge stuff working. Any good advice would be appreciated. -- 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
Odd behavior in musb_hdrc OTG if gadget drivers are modules
I've spend the day tracking down a weird behavior on a Beagleboard with 2.6.29-rc2-omap1. If you select the mode for the musb to operate in OnTheGo mode (CONFIG_USB_MUSB_OTG), and if you compile the gadget drivers as modules, the the USB port will NOT be brought up at system boot, even if it has a USB mini-A cable plugged in (and thus should be in host mode, not gadget mode). If you then modprobe an appropriate gadget driver, then the interface will be brought up in host mode. If you DON'T modprobe a gadget driver, AND you attempt to force the port to host mode by echo host > /sys/devices/platform/musb_hdrc/mode Then we get a kernel page fault trying to change modes, even though we are changing to host mode, which should be valid. It seems to me that either the port should be brought up in host mode if no gadget drivers are loaded, and an attempt to switch to gadget mode should fail if no driver is loaded, OR there should be a config options to set what the default gadget driver is in the absence of one being loaded by the system. -- 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
Is anybody else having problems with SDHC cards on Beagleboard?
I have been trying to bring up a Beagleboard as a development platform for a project at work, but I am having a killer problem: any significant access of the memory card (a class 8 SDHC 8G card) will die with a transfer error, followed by about 10 failed sector accesses, followed by the system dying. I've tried 2 different Beagleboards and 3 different cards by 2 different manufacturers, and the problem is repeatable on all permutations. I've put the cards into a card reader on my workstation and done a "dd if=/dev/sdf of=/dev/null" to verify the cards aren't wedged. I've searched for this on Google and found no references, but I cannot believe I'm the only person seeing this - but am I? -- 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
