 Documentation about the Vampire hardware |
| What Are the Main Problems With Vampire4 Devel?!? | |
|---|
|
|---|
| | 
Szyk Cech
Posts 191
10 Jun 2018 16:22
| Hi
I know the team works hard on Vampire4. It was predicted at the VI quarter of 2017, but it is still not available. So I think that there is some serious problems with Vampire4. So if it is not secret may I ask:
What are the main problems with Vampire4 development?!?Apollo core seems to be (almost?) complete. So maybe:
Timings?!? Aga?!? Hdmi classic modes output?!? Hdmi sound output?!?
Please share this info with us! with best wishes
Szyk Cech
| |
| | 
Tim Trepanier
Posts 132
10 Jun 2018 16:57
| By far the biggest delay was addition of an FPU to the core. This wasn't originally planned, but the community wanted it, so they took the time to do it.
| |
| | 
Ian Parsons
Posts 230
10 Jun 2018 17:32
| I think it was mentioned that there was a timing issue that prevented it from working on some motherboards that took a while to solve, I could be wrong though.
| |
| | 
Vojin Vidanovic
(Needs Verification)
Posts 1916/ 1
10 Jun 2018 21:13
| Tim Trepanier wrote:
|
By far the biggest delay was addition of an FPU to the core. This wasn't originally planned, but the community wanted it, so they took the time to do it.
|
No, that was v2 "problem" that took time from v4 development.
v4 has even harder/better FPU with no soft codes and with full precision :-)
Jump is ~50MFLOPS to nearly 70MFLOPS with no optimized software (ApolloFPU would need a bit different optimization code).
Why v4 is not ready? Hardware is there, but core that makes it what it is, seems to be testing and updating as we speak.
- GOLD3 core is not yet ready (promised by end of summer 018)
- v4 specific core testing and brushing (512mb RAM, dual flash support)
- v4 needs a bit more drivers for SAGA pack (LAN, USB, Pamela AHI ...)
We will see the end result when ready
Ian Parsons wrote:
|
I think it was mentioned that there was a timing issue that prevented it from working on some motherboards that took a while to solve, I could be wrong though.
|
Yes, last "report" did mention "A500 timing issues" that seems to be resolved up to now, but surely have taken their toll, too.
Chasing the rabbits, wont change the waiting line. YES, developer models were presented 2017. Yes, there was a lucky guess of Q4 017/Q1 018, but that is past already.
| |
| | 
Renaud Schweingruber
(Apollo Team Member)
Posts 379
11 Jun 2018 13:31
| CLICK HERE
| |
|
|
|
