Hi,
as the shop is making profit and I don't have any Pyra development related costs at the moment, I'd like to spend some money to fix the remaining software issues for the Pyra.
That would be:
* Fixing SDL1 so it does properly display in fullscreen (TILER issue at the moment) as well as use hardware acceleration for scaling, etc. (otherwise, it's dog slow).
* Getting ABE / AESS for the audio driver back to work (so all the rate conversion is happening with hardware acceleration. And maybe this also fixes the "breaking the stream" issue I mentioned in the other mail)
* Fixing USB issues (more on that in another eMail)
There surely are some more, but these are the most annoying ones at the moment.
I know there are some devs here who are experienced with OMAP stuff - and maybe they can spare some of their time and get paid for some fixes. I can't throw unlimited money out, so I can't pay a few thousand EUR per month, but at least 1000 EUR per month should be possible.
Also, a calculation based on work hours would be a bit hard. We had that issue with the Pandora where we hired a dev who got paid 20k USD to fix the Wifi driver - and in the end, it didn't work out but the money was gone. It would be better for me if someone estimates "I can fix audio for 3000 EUR" and I'll agree to that. Fixed prices is something I can calculate with - unknown prices are something I cannot afford.
So if someone here is interested in doing some paid work, let me know and we can set something up.
Otherwise, I'd like to open Bounties on the Pyra boards where devs can choose to work on that and get the bounty once the work has been done.
Before doing that, I would like to know if anyone here has any objections. I know some of you already laid the base work for the audio driver, for example, and I don't want to step on anyones toes if I open a bounty on the website for something you laid the ground work for free.
So please let me know any objections (or interests for taking the job). If I don't hear something back until middle of next week, I'll start with the bounties on the boards.
Am 24.02.2021 um 20:07 schrieb Michael Mrozek EvilDragon@openpandora.org:
Hi,
as the shop is making profit and I don't have any Pyra development related costs at the moment, I'd like to spend some money to fix the remaining software issues for the Pyra.
That would be:
- Fixing SDL1 so it does properly display in fullscreen (TILER issue at
the moment) as well as use hardware acceleration for scaling, etc. (otherwise, it's dog slow).
- Getting ABE / AESS for the audio driver back to work (so all the rate
conversion is happening with hardware acceleration. And maybe this also fixes the "breaking the stream" issue I mentioned in the other mail)
There is good initial work, see my other mail.
- Fixing USB issues (more on that in another eMail)
There surely are some more, but these are the most annoying ones at the moment.
I know there are some devs here who are experienced with OMAP stuff - and maybe they can spare some of their time and get paid for some fixes. I can't throw unlimited money out, so I can't pay a few thousand EUR per month, but at least 1000 EUR per month should be possible.
Also, a calculation based on work hours would be a bit hard. We had that issue with the Pandora where we hired a dev who got paid 20k USD to fix the Wifi driver - and in the end, it didn't work out but the money was gone. It would be better for me if someone estimates "I can fix audio for 3000 EUR" and I'll agree to that. Fixed prices is something I can calculate with - unknown prices are something I cannot afford.
Well, for me the opposite is true. I can't afford unknown efforts.
If I ever agreed to fixed prices it did take much more time than I had planned... Not because I am too slow (I was working like in a treadmill :) but because we all underestimated the complexity of the issues before really starting. And since I am not a guy who is giving up when the problem isn't solved I spent much more time than I was paid for...
So if someone here is interested in doing some paid work, let me know and we can set something up.
The AESS thing is tempting (because I have invested a lot of time to get it compile again), but I can't really estimate how much time it would need (since I am not an expert for the Linux sound system and have to study documentation and code first).
And, there is an open issue: the AESS firmware. AFAIR the last almost working version did have a working driver, but firmware file format modern Linux kernels do accept have changed. There had been attempts by Peter Ujfalusi and Marek Belisko (who is much more experienced with Audio than me) to recompile it from source but they did not succeed completely.
So it is too much risk to work on a fixed price basis.
Otherwise, I'd like to open Bounties on the Pyra boards where devs can choose to work on that and get the bounty once the work has been done.
Before doing that, I would like to know if anyone here has any objections. I know some of you already laid the base work for the audio driver, for example, and I don't want to step on anyones toes if I open
AES/AESS integration is available in the latest Letux kernels. But incomplete. It compiles, does not harm but does not have the expected functionalities (because I don't know how to set up the DAI links and widgets correctly).
And as said above, the AES firmware is not in a good shape.
If you take letux-5.10 as the basis it should work.
Otherwise the latest AESS patch set is here:
https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux/...
a bounty on the website for something you laid the ground work for free.
So please let me know any objections (or interests for taking the job). If I don't hear something back until middle of next week, I'll start with the bounties on the boards.
-- Greetings,
Michael Mrozek
OpenPandora GmbH CEO: Michael Mrozek
Schäffbräustr. 11 85049 Ingolstadt Germany Tel.: +49 841 990 5548 http://www.openpandora.de/ HRB 4879, Amtsgericht Ingolstadt
eMail: mrozek@openpandora.org
Kernel mailing list Kernel@pyra-handheld.com http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel