bush-hacking digest, Vol 1 #44 - 6 msgs

[Andrew Flegg]

On Wed, Jun 26, 2002 at 11:57:26AM +0100, Matt Evans wrote:
> 
> I had a fiddle with this last month and it was a pain in the
> arse.  Peculiarly, *TYPE devicefs:$.serial1 returned /nothing/ when I sent
> data down serial port 1, but returned gibberish (as expected) from the IR
> remote via serial2.

Did you solder the port directly onto the SerialIO lines, might a MAX232 
be needed?

    http://216.239.39.100/search?q=cache:vKeU3u2R-7kC:www.kmitl.ac.th/~kswichit/MAX232/MAX232.htm+MAX232&hl=en&ie=UTF-8
(http://www.kmitl.ac.th/~kswichit/MAX232/MAX232.htm if the server's back)

> (The port physically works, in non-RISC OS land.)

What other checks did you do?

> This would've been the perfect solution for me, nevermind all this
> modem-modem leased-line stuff :)

:)

There's <modem$path> which, by default, points to devices:$.modem - if
the serial port could be got working then pointing this at 
devices:$.serial1 might just magically change what the dialler uses.

> PPPconnect seems sort-of easy to point to the right serial port, but 
> again nothing goes over it. 

:-(

> ps: Lucent modem chip sits on the EASCS chip-select (asserted for
> 0x08000000 -> 0x08ffffff).  It's a 16550-alike, but think it is
> plug-and-pray so ...

On the leased line bit, hopefully something like the following might work:

    http://www.epanorama.net/documents/telecom/fax_to_modem.html

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/