Welcome!
Final Burn Neo => FBN Development => Topic started by: NoLifeEmu on March 04, 2017, 05:32:40 PM
-
Hello,
Just wanted to check if anyone here is already working on a Seibu SPI driver (for Raiden Fighters series).
If that's not the case I would be happy to have a look at it.
Are we allowed to port Intel 386 and Yamaha YMF 271-F cores to FBA ?
If not, what are the compatible licenses for FBA ?
No, I don't plan developing the i386 core from scratch :)
-
Hi, there isn't anyone doing this ATM, so you're all clear to begin :)
best regards,
- dink
Hello,
Just wanted to check if anyone here is already working on a Seibu SPI driver (for Raiden Fighters series).
If that's not the case I would be happy to have a look at it.
Are we allowed to port Intel 386 and Yamaha YMF 271-F cores to FBA ?
If not, what are the compatible licenses for FBA ?
No, I don't plan developing the i386 core from scratch :)
-
Hello,
Ok dink thanks for your answer.
I will post my progress on this thread (hopefully) :cool:.
-
Awesome, looking forward to it :D
-
I second this, cool stuff!. :cool:
-
Cool.
I have 3 main driver dependencies compiling fine :
- Intel 386
- DS2404 RTC / Backup RAM
- Intel Flash (nvram)
Working on a getting YMF271 core compiling in FBA then I should be able to start writing the driver itself.
-
Cool.
I have 3 main driver dependencies compiling fine :
- Intel 386
- DS2404 RTC / Backup RAM
- Intel Flash (nvram)
Working on a getting YMF271 core compiling in FBA then I should be able to start writing the driver itself.
Some nice progress there!!.
-
Rock on :D Nice work!
please check your pm :)
Cool.
I have 3 main driver dependencies compiling fine :
- Intel 386
- DS2404 RTC / Backup RAM
- Intel Flash (nvram)
Working on a getting YMF271 core compiling in FBA then I should be able to start writing the driver itself.
-
Cool.
I have 3 main driver dependencies compiling fine :
- Intel 386
- DS2404 RTC / Backup RAM
- Intel Flash (nvram)
Working on a getting YMF271 core compiling in FBA then I should be able to start writing the driver itself.
Holey moley! Nice work. :D Looking forward to seeing this up and running.
-
for the record, the cores you need from MAME are currently BSD-3 licensed.
since FBA is based off the previous MAME license (previous MAME license is basically BSD-3 + non-commercial clause) they should be license compatible so you should have no (lega) issue with using them.
if they were GPL that would be another matter entirely, as FBA is not GPL compatible (and would take a major re-licensing effort to get there requiring contacting every contributor just as MAME had to go through)
-
for the record, the cores you need from MAME are currently BSD-3 licensed.
since FBA is based off the previous MAME license (previous MAME license is basically BSD-3 + non-commercial clause) they should be license compatible so you should have no (lega) issue with using them.
if they were GPL that would be another matter entirely, as FBA is not GPL compatible (and would take a major re-licensing effort to get there requiring contacting every contributor just as MAME had to go through)
Thanks for the clarification !
-
Interesting topic, thanks for sharing! The tips are very helpful.
-
Quick update.
I've been focusing so far on getting (at least) rdft ROM loading properly and adding mandatory code for graphics decryption.
Next task is to hook up memory map and write most handlers, but before this I need to write an interface to the Intel 386 core ripped from MAME.
Any "name" suggestion for this ?
I've seen :
Zet is for Z80 (makes sense)
Vez is for NEC V30 family (don't get this one)
....
Which logic / How should I call the Intel 386 interface ?
Thanks !
-
Quick update.
I've been focusing so far on getting (at least) rdft ROM loading properly and adding mandatory code for graphics decryption.
Next task is to hook up memory map and write most handlers, but before this I need to write an interface to the Intel 386 core ripped from MAME.
Any "name" suggestion for this ?
I've seen :
Zet is for Z80 (makes sense)
Vez is for NEC V30 family (don't get this one)
....
Which logic / How should I call the Intel 386 interface ?
Thanks !
I386... is my suggestion. Zet, sek, and vez are confusing honestly (I386Open(INT32 num), I386Run(INT32 cycles), etc)
-
Nice!
Lately we've been calling things cpuname_, so i386_open,close,run,etc. would make the most sense - but this one is totally up to you :). I guess back in the day our ancestors were crafty with the namings of the cpu cores, hence Zet, Sek, etc.
-
Nice!
Lately we've been calling things cpuname_, so i386_open,close,run,etc. would make the most sense - but this one is totally up to you :). I guess back in the day our ancestors were crafty with the namings of the cpu cores, hence Zet, Sek, etc.
I can only agree with that !
-
Hi NoLifeEmu,
are there news about the Seibu SPI driver? :)