Subject: Re: Boot Problem -- ttyflags lock it up - *solved*
To: greg walsh <gwalsh@artec.com>
From: Dr. Bill Studenmund <wrstuden@loki.stanford.edu>
List: port-mac68k
Date: 10/19/1998 13:35:24
On Mon, 19 Oct 1998, greg walsh wrote:
> At 12:55 PM -0700 on 10/19/98, you wrote:
>
> >On Sun, 18 Oct 1998, Henry B. Hotz wrote:
> >
> >Have youi tried setting clock rates on both pins on the printer port?
> >Without those, the changes (which I think are) in this kernel will do
> >nothing.
>
> Hey Bill
>
> I haven't tried setting the clock rates yet. I ran into a small
> problem (my ignorence) trying to install Henrys kernel. He posted me
> with the solution to that, and I'll give it a try later today.
Henry's kernel will do nothing different if you don't set the clock rates.
> I'll need to call epson to get the clock rates for the printer, I'm
> doing that today as well. I poured over all the tech specs that came
> with the printer, but that particular piece of info wasn't included.
> Guess they never planned on somone wanting to run it on a unix box
> without a network card.
"1" should be good enough to boot.
The clock's value does two things. One, if it's non-zero, then a lot of
hooks get turned on to ensure that we don't enable interupts on the
relevant pin. Second, if we are requesting a baud rate which can be better
generated using the clock on that pin and its division circuitry, we use
the pin instead of the internal BRG.
I bet it's something like 3.68 MHz.
> Once I get Henry's kernel running and the printer clock sync'd I'll
> report back.
One problem you might run into is that it might be running in HDLC mode,
which is more like LocalTalk. We don't support it yet. :-(
But a clock value of "1" will certainly get it to boot. I hope.
Take care,
Bil