No, the other way around. I still subscribe to the old philosophy of "the recorder is the master", so I always use the Ghost as a slave. I have a pretty complex rig, but here's what I do- some of it may help.
The DAW is Cubase with a Hammerfall. I also use a Fostex D1624 mulltitrack. The Fostex is the system timecode master, in almost all cases. It is set up to listen to Sony 9-pin protocol machine control from the Ghost, so I can use the machine control on the Ghost to play, start, stop, and so on on the Fostex. The Fostex is set up to output MTC, which I then run to the DAW (via a Midex-8). The DAW is set up to chase the incoming timecode from the Fostex, and then output MTC of its own- which I then run to a JLCooper MTC-SMPTE converter to drive the Ghost's timecode display. I needed to go to SMPTE because the Fostex's 9-pin protocol has really lousy MTC sync behavior. It sends its timecode in bursts in play and record mode, so accurate mute automation is a lost cause. SMPTE derived from the unit's native MTC has proven to be more reliable.
This roundabout routing lets me use the DAW without the Fostex, and still get timecode to the Ghost for using the board's automation- I don't get machine control without the Fostex, but once I'm on the DAW and mixing with the mouse anyway, I can cope with that. I normally track to the Fostex, because of a native distrust of computer recording, and then later fly the tracks in for editing, archiving and so on.
When not using the Fostex, I suppose I could easily reconfigure the Ghost to do MMC (instead of 9-pin) to directly control the DAW and repatch the Ghost's midi out to drive a spare input on the DAW. But I haven't bothered much with this yet, other than to prove that it worked one time... I find it much more powerful to be able to work on the Fostex and DAW simultaneously, so just having the Ghost control the Fostex, and the DAW chasing it, works best for me...