[Coco] NitrOS9 question

[L. Curtis Boyle]

I don’t know the current build of NitrOS9 as well as I did back in the 1.xx and 2.0x days, but I think VTIO (then CC3IO) was directly tied into the clock module, to help time keyboard / joystick / mouse reads on the clock 60 Hz IRQ’s, as well as palette changes (to prevent “snow”). Since a lot of those functions have been split into separate modules, I am wondering if VTIO is still kicking off the chain for where to go on the 60Hz IRQ, and if you don’t have it there, it never makes it right through. (Or doesn’t properly initialize clock, which is required for task switching, etc.).

L. Curtis Boyle
curtisboyle at sasktel.net

TRS-80 Color Computer Games website
http://www.lcurtisboyle.com/nitros9/coco_game_list.html



> On Oct 5, 2017, at 2:25 PM, Dave Philipsen <dave at davebiz.com> wrote:
> 
> Well, just for snicks I will try creating a Term descriptor for T2 and changing the default console in Init back to Term.  However, the 'external processing' that T2 would need should come from SC6551. If you think about it, T2 is already working without VTIO because the sign-on banners show up.  That means that the I$Write system call is sending data to IOMan who sends it to SCF who then determines that T2 is driven by SC6551 and sends it to SC6551.
> 
> In addition, T2 works when VTIO is present even though there is no Term descriptor.
> 
> 
> Dave
> 
> 
> On 10/5/2017 3:03 PM, Bill Pierce via Coco wrote:
>> I think it's looking for a terminal... I would think you would want to use "term_6551" or "term_6850" (whichever would be appropriate) instead of T2 as these are serial terminals meant to receive from the acia and print to the screen. And yes VTIO would most likely be needed. T2 would some sort of external processing to send the data to the screen... hence why the serial terminals are used.
>> I may be wrong or interpreting your method incorrectly, but that is how I'm reading this.
>> 
>>  
>>  
>> Bill Pierce
>> "Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull
>> 
>> My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> https://sites.google.com/site/dabarnstudio/
>> Co-Contributor, Co-Editor for CocoPedia
>> http://www.cocopedia.com/wiki/index.php/Main_Page
>> 
>> E-Mail: ooogalapasooo at aol.com
>> 
>>  
>>  
>> -----Original Message-----
>> From: Dave Philipsen <dave at davebiz.com>
>> To: coco <coco at maltedmedia.com>
>> Sent: Thu, Oct 5, 2017 2:17 pm
>> Subject: Re: [Coco] NitrOS9 question
>> 
>> Ok, so I've successfully eliminated CoWin, KeyDrv, SndDrv, JoyDrv, RBDW, DWIO, RAMD, R0, and Term from my bootfile and the CoCo3FPGA boots up with a shell on T2.  But, when I try to remove VTIO I get the signon message from Init on T2 but I don't get a shell.  To my knowledge VTIO is simply a device driver module for the SCF window devices.  If I have no window device descriptors in the bootfile, then, why is VTIO needed?  See output from 'mdir' below:KrnP2      Init        Clock       Clock2      IOMan       RBFSCF         PipeMan     RBSuper     LLCoCo3FPGA Piper SD1DD          SC6551      VTIO        T2         Pipe CCBKrnMDir        Shell       Date        DeIniz      Echo InizLink       Load        Save        UnlinkDaveOn 10/3/2017 11:12 PM, Dave Philipsen wrote:> Yep, it's an FPGA board so it's a synthesized 6809 running at 25 MHz.>> Dave>> On 10/3/2017 9:23 PM, Brett Gordon wrote:>> I take it your platform is also 6809 based? Cool.. Sounds like a neat>> idea.  Loads of fun.  kudos on the bootloader mod - submit patch!>>>> brett>>>>-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco
>> 
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>