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
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
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
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
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
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.
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
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
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:
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
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
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
12 matches
Mail list logo
