Search results

Has that ever been tested? :-) Although the HDMI chapter indeed mentions 2560x1600p60 with reduced blanking in the tables of standard timings supported, most of the DSS chapter never mentions standard resolutions above 1080p (including for HDMI). Some actual hardware limits I encountered in the...

Some prototype board I was once involved with had been examined by many pairs of eyes, yet all of them (including mine) managed to overlook that the RAS and CAS signals to the memory had been swapped. Stuff like that just happens. This is confused in so many ways... (BTW, 8GB has actually...

To add to the "hey look what I found" pile: firmware blobs and stuff for the Audio Engine in the Audio Back-End subsystem.

Well, that depends a bit on what you mean. It doesn't really work more or less okay than before. (Okay maybe slightly less since I need to fix ywrap support for tiler-allocated buffers, but that only affects the performance of fbcon) Well you could, just not via fbdev since omapdrm allocated a...

That was 5 days ago Yes, and it was celebrated 19 hours ago. You missed the party. There was cake. It was delicious. Also I posted that I fixed the problem on the pyra kernel mailing list and cc'd you. rootfs no idea, same as before I guess? kernel has already been uploaded by aTc, see my...

https://github.com/mvduin/linux/commits/patch/tiler-fbdev2 (Commits where I'm fully aware I'm doing horrible hacks just to "get it working first, do it properly later" have been marked with XXX.) They're mostly unrelated. So I don't know about x86, but on the ARM SoCs I'm familiar with you're...

To clarify, I wasn't being very serious. The necessary current measurement would already need to be implemented in the amplifier, and I have no reason to assume it is. The topic was however the concern of the large range in headphone impedance and its obvious impact on sensitivity. Of course it...

You mean "have a much higher impedance, requiring higher voltage (but less current) to be driven to acceptable volumes." Ideally a volume knob would scale the power delivered rather than voltage driven. Unfortunately that's easier said than done...

Weird, I haven't looked in detail but I think I've seen stuff for the omap3's rotation engine (VRFB) in kernel as well. But I guess maybe noone took the effort to make all the ingredients work together properly for the desired end result? Actually mostly my effort has been on fixing slowness...

No, all the colors are fine, the pixels are just being shuffled around. This was the result of my first attempt to force the legacy fbdev framebuffer into tiled memory to allow it to be rotated, since despite being legacy it still seems to be a dominant way of doing non-GL fullscreen stuff. My...

Working almost perfectly: At least TILER is clearly getting involved... you can see the tiles ;-)

Given the fair number of auxiliary cores present, you can probably do most of it even when the OS isn't running. Fancy led driver too... it can do fades / "breathing" on its own (datasheet)

I have absolutely no idea what you're trying to say here. The sealed enclosure around the rear side is tiny so I think you can safely ignore any wave-like effects there and just view it as the acoustic equivalent of a capacitor, storing energy by compressing or expanding the enclosed air.

Sealed enclosures are one of the most common types of speaker enclosure :-) Basically a driver in open air just stirs the air around from front side to back side, effectively radiating very little. An alternative way to look at it is that both front and back side radiate equally, but with...

OMAP3 has 3 layers, OMAP5 has 4. You only need those to show four buffers at the same time (three of which support scaling and color space transformation), with individual placement on the display, z-order, and alpha compositing. By default one layer is used, attached to the buffer belonging to...

That reminded me of this post :D (click image for high-res version)

It's actually not that complicated.... I think. The first thing you need to know is that DDR3 uses a burst length of 8 transfers. Since each DDR3 controller on the omap (it has two) has a 32-bit data bus, that means that every access results in an aligned 8 * 32-bit = 32-byte transfer. If you...

TILER is integrated in the memory controller and operates directly on accesses to the framebuffer. Yoyobuae's explanation is largely accurate: Actually the data also needs to be rearranged. Oh it works :) It has worked all along, the issue was that the performance was abysmal. It turned out...

Score! :D I wonder if anyone at TI even knows what is or isn't publicly released, there are soo many different repositories all over the place. How'd you stumble across this one?

Ah interesting, I hadn't realized that part was open. The big problem however is the HDVICP2 (synonym for IVA-HD) binary codecs package, which is a dependency and every link to it seems dead. See also this thread, and this. Maybe this firmware blob is what we need, but I don't have the energy...