Author Topic: Seibu SPI driver anyone ?  (Read 8500 times)

Offline NoLifeEmu

  • New Member
  • *
  • Posts: 7
  • Karma: +0/-0
Seibu SPI driver anyone ?
« 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 :)

Offline dink

  • Administrator
  • *****
  • Posts: 5014
  • Karma: +449/-1
  • pie? I nearly bought one!
Re: Seibu SPI driver anyone ?
« Reply #1 on: March 04, 2017, 05:55:29 PM »
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 :)

Offline NoLifeEmu

  • New Member
  • *
  • Posts: 7
  • Karma: +0/-0
Re: Seibu SPI driver anyone ?
« Reply #2 on: March 05, 2017, 05:51:25 AM »
Hello,

Ok dink thanks for your answer.
I will post my progress on this thread (hopefully) :cool:.

Offline dink

  • Administrator
  • *****
  • Posts: 5014
  • Karma: +449/-1
  • pie? I nearly bought one!
Re: Seibu SPI driver anyone ?
« Reply #3 on: March 05, 2017, 08:07:50 AM »
Awesome, looking forward to it :D

Offline Trick

  • Newbies
  • *
  • Posts: 24
  • Karma: +0/-0
Re: Seibu SPI driver anyone ?
« Reply #4 on: March 06, 2017, 12:08:23 AM »
I second this, cool stuff!. :cool:

Offline NoLifeEmu

  • New Member
  • *
  • Posts: 7
  • Karma: +0/-0
Re: Seibu SPI driver anyone ?
« Reply #5 on: March 06, 2017, 03:27:47 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.

Offline Arcadez

  • Expert
  • *****
  • Posts: 558
  • Karma: +15/-0
  • Arcade Addict
Re: Seibu SPI driver anyone ?
« Reply #6 on: March 06, 2017, 03:44:44 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.

Some nice progress there!!.

Offline dink

  • Administrator
  • *****
  • Posts: 5014
  • Karma: +449/-1
  • pie? I nearly bought one!
Re: Seibu SPI driver anyone ?
« Reply #7 on: March 06, 2017, 05:52:06 PM »
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.

Offline iq_132

  • Administrator
  • *****
  • Posts: 3728
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Seibu SPI driver anyone ?
« Reply #8 on: March 06, 2017, 06:25:34 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.

Holey moley! Nice work. :D Looking forward to seeing this up and running.


Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Seibu SPI driver anyone ?
« Reply #9 on: March 06, 2017, 08:12:13 PM »
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)
« Last Edit: March 06, 2017, 08:13:52 PM by Haze »

Offline NoLifeEmu

  • New Member
  • *
  • Posts: 7
  • Karma: +0/-0
Re: Seibu SPI driver anyone ?
« Reply #10 on: March 07, 2017, 05:06:05 AM »
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 !

Offline rita.barr

  • New Member
  • *
  • Posts: 2
  • Karma: +0/-1
Re: Seibu SPI driver anyone ?
« Reply #11 on: March 08, 2017, 12:28:30 PM »
Interesting topic, thanks for sharing! The tips are very helpful.
To want to, is to be able to.

Offline NoLifeEmu

  • New Member
  • *
  • Posts: 7
  • Karma: +0/-0
Re: Seibu SPI driver anyone ?
« Reply #12 on: March 12, 2017, 04:31:35 PM »
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 !

Offline iq_132

  • Administrator
  • *****
  • Posts: 3728
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Seibu SPI driver anyone ?
« Reply #13 on: March 12, 2017, 05:01:07 PM »
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)
« Last Edit: March 12, 2017, 05:40:13 PM by iq_132 »


Offline dink

  • Administrator
  • *****
  • Posts: 5014
  • Karma: +449/-1
  • pie? I nearly bought one!
Re: Seibu SPI driver anyone ?
« Reply #14 on: March 12, 2017, 05:12:57 PM »
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.