I'm trying. Understanding the Kernel for the first time was a much bigger task than I thought it was going to be. I finally got through the 6000 page TRM for the OMAP5432 and it was exciting to see how detailed the TILER information was. How to apply it seemed conceptually easy. Write to memory X, tell the memory manager that memory X is special. Read from Y. How to make that work in Linux, I'm working on.It depends on what you consider fixed... 3D acceleration works, Rotation works... At the same time, not so much. Unless I've missed anything over the past few months. Seems like everyone who wants to tackle the issue disappears after some time.
https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues I thought was a good spot for development issues.Though I am not a programmer, is there a to-do list somewhere?
Ah, well, there's still some low-level stuff to do, for example a proper working heat / limit clock setup and more.What kind of devs do you mean in particular, low level kernal devs or emulator devs etc?
I'm not sure how the Pandora did that, whether it was a special touchscreen or driver, but these days, it's not easy to find a resistive touchscreen at all for a reasonable price... so if the hardware can't do it, it won't work :/Sorry if this question belongs somewhere else, but does the Pyra report stylus pressure levels to programs like Gimp or Mypaint? If not, maybe that is something a couple of us could fix together...
I'm sure they're wired in as a single stereo system to the SoC.So speakers directly connects with PCB but are not connected with each other, that is probably the reason they show up as two different outputs in pulse. I think it will need some software hack for them to work as a single stereo speaker instead of two mono speakers.
Yes, but that's just a software issue. The things being on different channels I think is just a configuration problem. I don't think it's how it's wired up that's the problem. But I could be wrong.
Please someone correct me if I've got this wrong, but my understanding is that the first production run is to be only 500 units. (600 minus a big margin for rejects, so likely closer to 600 units than to 500.)with >1100 preorders, production will take about 1 months ( @ 250/wk)
Don't forget to add in a month for Easter and a month for the summer holidays!Case is not complete yet, new company is making changes so this may take a month or two,
My reading of that [am I an incurable pessimist?] is that this is because no one is working on it; that everyone with hardware is waiting for... I don't know... newer hardware... someone else (TM) to fix stuff so they can resume testing/developing... I don't know. (Except for hns, or course, who seems to be fighting a constant battle against the entropy of ill-disciplined upstream Linux-kernel developers who seem to be incapable of refraining from making breaking changes, while keeping Letux up-to-date on many more platforms than just Pyra.)From reading the pyra kernel list, it feels like an awfully long time since anyone found anything that required a revision
You're correct. The chip supports all different kinds of configuration, and it's all setup in the driver of the audio chip.Yes, but that's just a software issue. The things being on different channels I think is just a configuration problem. I don't think it's how it's wired up that's the problem. But I could be wrong.
Yes, the issue is not related to Pulseaudio, ALSA has the same.I'd guess this is some quirk of the sound chip driver and how it exposes the hardware to alsa.