Moving along


If you decide to go down the "2GB for now" route can the 24 of us who ordered 2GB go to the head of the queue?

jk
 
im all for a 2gb pyra now and update to the 4gb board later
 
Back when the pyra was being designed, myself and but a very few others encouraged ED to stick with 2gb when everybody was clamoring for 4 or more. Here we are with the 214521452 PCB mod with no idea why 4GB still isn't working and 3 years after preorders. While 2gb worked with the unoptimized board how many years ago?

Stop the scope creep. Get the product out, then improve it.
 
Last edited:
I know we've got quite a lot of OpenSource fans around here. Maybe some know some good kernel developers, who are able to include and improve hardware support and fix various issues.
We can provide a test unit as well as the needed datasheets - but it needs someone who is capable of debugging and fixing low-level things.

I've been an application developer for 10 years now and I was hoping to get my hands on a Pyra so I could start tinkering around with kernel and hardware development.
I'm currently building a low powered handheld based around the Feather M0 proto board (stuck on case details). I had a bit of fun with software setup to get the screen and input going.

I don't want to be considered first in line due to my lack of experience, but if you have a spare mainboard and cpu, I would love to dive in head first. I don't mind if it is an older revision that has terrible wifi or underclocked cpu. I don't need a full test unit with case and battery. Should help save on postage (which I'm happy to pay for).
If the TILER fixes are need only for the pyra screen and not hdmi, I would need one of those.

I'm currently on a hiatus from work so have heaps of time. I'm a pre-orderer and had the funds for a second unit so am all on board for the pyra train. I couldn't justify buying in on the prototype units you were offering during preorder and contemplating buying a dev board but thought the setup didn't feel close enough to provide useful value for the handheld.

Also, put my name down for a 4GB board knowing that it would only be 2GB if there were issues. Agree there should be some testing time but a 2GB model wouldn't be a let down.
 
Last edited:
I know I am going to get nailed for this but...

What if we just gave up on this CPU-GPU combo for the 4GB RAM option and went ahead with the new CPU-GPU upgrade that was going to happen at some point in the future anyways?

We could save those 4GB RAM chips for that new board.
 
I know I am going to get nailed for this but...

What if we just gave up on this CPU-GPU combo for the 4GB RAM option and went ahead with the new CPU-GPU upgrade that was going to happen at some point in the future anyways?

We could save those 4GB RAM chips for that new board.

I assume you mean while still releasing the 2GB OMAP5 version to those who preordered, because that would take a couple years...

I gotta admit, I like this idea a bit. Putting 4GB on an OMAP5 is like casting pearls before swine, from what I've heard. And it's not like 4GB on OMAP5 is the only thing that has been delaying the release of the Pyra until now, so there's no need for everyone to groan if we give up on it. Specifically, the case hasn't been ready until now.
 
This would limit what could be used, as you would be stuck looking for an SoC that uses that RAM, which I understand is not usually used for mobile devices.
 
Okay, what rygD said changed my mind. Thanks for the info.

It's hard enough to make RAM work on the SoCs that claim to support the type you have. (I'm looking at you, OMAP5.)
 
Back when the pyra was being designed, myself and but a very few others encouraged ED to stick with 2gb when everybody was clamoring for 4 or more. Here we are with the 214521452 PCB mod with no idea why 4GB still isn't working and 3 years after preorders. While 2gb worked with the unoptimized board how many years ago?
I certainly underestimated the complications for supporting 4GB. Though the cases are also still in the "maybe they are ok this time"-phase (spoiler: they aren't). The Pandora was also massively delayed by the case and it seems that switching production to Europe has not really helped either (at least not in terms of time).
Stop the scope creep. Get the product out, then improve it.
I find myself agreeing with this. The way this is going it will take at least two more years™.
 
Hi all :)
Now, here's a question for you:
I know we've got quite a lot of OpenSource fans around here. Maybe some know some good kernel developers, who are able to include and improve hardware support and fix various issues.
We can provide a test unit as well as the needed datasheets - but it needs someone who is capable of debugging and fixing low-level things.
I am fine paying for the work as well.

Any ideas or contacts? :)
@EvilDragon : what about Paul Kocialkowski, from the Replicant project ?

https://replicant.us/
https://redmine.replicant.us/projects/replicant/wiki/People#Active-developers

And enjoy your vacations, you deserved it !

Cheers, Magic Sam (also fine with a 2GB Pyra)
 
I don`t care about 4GB, but the lack of working 3D after more then 4 years of development is annoying.
 
Hello,

I'm not a developper, I'm not yet a Linux user, and pyra will be my first micro-computer-console-emulator-and-other-applications.
I trust in the awesome-quality-pyra-project.

Ok it takes a while, but I'm sure it will be very very good (that's why I never will order a GPD win)

Difficult project -> Unique product -> Impeccable quality and durability

You have my full confidence so make your best (as in the case !) and sure I will be happy.

Thanks for the news and bon courage at the Pyra team ! :)
 
Hmm, could the 4gb chips be saved for the next board upgrade? Then 4 gb could be the base and 8 gb be the uper level.

I don't know if this will work, having a different cpu might call for different memory entirely, I'm not sure.
 
I don`t care about 4GB, but the lack of working 3D after more then 4 years of development is annoying.
According to the fount of all knowledge, the IRC non-dev channel, that's mainly because the kernel is still getting tweaked, making maintaining the bit that plugs the binary blob into the kernel more frustrating. And don't forget Notaz had it working on the devboard well enough to run Ikarugu under dreamcast emulation years ago now, although I forget if that's more than 4 years ago now to be honest.
 
Back
Top