[Coco] Disto 4-in-1 clock2 with CocoSDC

[Kip Koon]

Hi NitrOS-9 Developers,
I too have tried making very minor changes in a few of the RBF descriptors in my local copy of the NitrOS-9 repo, but when I rebuild it to get my changes included in my local distribution dsk files, the changes are not present.  In fact, nothing I change gets included anywhere.  Somehow they are totally ignored.  This is the reason why I have not even tried to play around with the repo yet beyond keeping my local copy up-to-date.  What am I doing wrong?  
It seems a lot of people are making wonderful changes to the NitrOS-9 Distribution disks and getting them included in the master repo files, but I can't ever build in one little change in a simple descriptor.  So this is the reason I keep making this little change in EVERY SINGLE boot disk I use.  I've been doing this for 4 years now and it's a minor annoyance, but I can deal with it.  Still though, I would like to contribute to our wonderful OS, but I can't.  What can I read to figure this all out.  Please point me in the right direction.  Thank you in advance.  

Kip Koon
computerdoc at sc.rr.com
http://www.cocopedia.com/wiki/index.php/Kip_Koon



-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Bob Devries
Sent: Wednesday, January 21, 2015 6:22 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] Disto 4-in-1 clock2 with CocoSDC

Hmm, let me correct my mis-statement here. I changed the makefile to insert the -DMPIFlag and -DMPI.Slot=4, but the build seems to have ignored those two flags. The conditional code does not get included, hence the clock2 module does not access the correct MPI slot.

Regards, Bob Devries
Dalby, QLD, Australia



On 22/01/2015 8:53 AM, Robert Gault wrote:
> Bob Devries wrote:
>> Hi Robert,
>>
>> I also notice that there's no entry in the makefile to actually
>> *build* the
>> clock2_disto4 module. The makefile has an entry for two software 
>> clocks (50 and 60Hz), the cloud9 and the BNB clock2 modules.
>>
>> I notice that the other clock2 entries have something like -DCLOUD9=1 
>> or -DBNB=1. However, I can't see where this is used. Should I set the
>> clock2_disto4
>> to -DDISTO or -DDISTO4.
>>
>> And yet, it appears that there is a clock2 module in the 
>> NITROS9/6309L2/CLOCKS directory on the created disk image. That image 
>> doesn't read the clock since I suspect that the default clock2 module 
>> is the 60Hz software clock.
>>
>> You would be forgiven if you think I'm floundering here. :)
>>
>> Regards, Bob Devries
>> Dalby, QLD, Australia
>>
>
> These makefiles give me headaches as well. :)
>
> While there are no entries at the end of the file # Clocks
> clock_60hz: clock.asm
>      $(AS) $(AFLAGS) $(ASOUT)$@ $< -DPwrLnFrq=60
>
> clock_50hz: clock.asm
>      $(AS) $(AFLAGS) $(ASOUT)$@ $< -DPwrLnFrq=50
>
> clock2_cloud9: clock2_ds1315.asm
>      $(AS) $(AFLAGS) $(ASOUT)$@ $< -DCLOUD9=1
>
> clock2_bnb: clock2_ds1315.asm
>      $(AS) $(AFLAGS) $(ASOUT)$@ $< -DBNB=1 for some of the clocks, 
> there are entries towards the beginning of the makefile.
>
> CLOCKELIM       = -DRTCElim=1
> CLOCKDISTO2     = -DRTCDsto2=1
> CLOCKDISTO4     = -DRTCDsto4=1
> CLOCKBNB        = -DRTCBB=1
> CLOCKSMART      = -DRTCSmart=1 -DMPIFlag=1
> CLOCKHARRIS     = -DRTCHarrs=1
> CLOCKCLOUD9     = -DRTCCloud9=1
> CLOCKSOFT       = -DRTCSoft=1
> CLOCKMESSEMU    = -DRTCMessEmu=1
> CLOCKJVEMU      = -DRTCJVEmu=1
>
> CLOCKS          = clock_60hz clock_50hz \
>          clock2_elim clock2_disto2 clock2_disto4 clock2_bnb \
>          clock2_smart clock2_harris clock2_cloud9 clock2_soft \
>          clock2_jvemu clock2_messemu clock2_dw
>
> So, all the necessary clocks will be built. What has not been done or 
> needed in CLOCKSMART is a conditional based on the MPIFlag. That 
> clock2 will always search as if an MPI were present.
>
> Robert
>
>
>

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco