On 2009-05-08, Alexander Shikoff <minot...@crete.org.ua> wrote: > On Fri, May 08, 2009 at 01:33:28PM +0100, Stuart Henderson wrote: >> On 2009/05/08 14:20, Alexander Shikoff wrote: >> > Hi Stuart, >> > >> > > cuaU# for USB serial ports, cua## for ns16x50-like devices. think those >> > > are the only choices for serial ports at the moment. >> > > >> > > for your puc(4) look at cua03..cua10 (dial-out devices) or tty03..tty10 >> > > (terminal devices; see "man 4 tty" for the difference between cua/tty). >> > There are no tty04..tty10 devices in /dev >> > There are only tty00..tty03. >> >> we don't have devfs, our devices nodes are static. use MAKEDEV or mknod >> to give you more. > > Thanks, guys! Your help is great. > > I see incoming calls. > > Now I have in /etc/gettytab: > std.38400|38400-baud:\ > :pp=/etc/ppp/ppplogin:\ > :sp#38400: > > # ps ax|grep getty > 25750 ?? I 0:00.01 /usr/libexec/getty std.38400 tty04 > 12105 ?? I 0:00.01 /usr/libexec/getty std.38400 tty05 > [...] > > But modem does not pick up. Is there a way to send initial configuration > commands to it with getty? I want to init modem with ATS0=1 command. > I've read gettytab(5) and not found anything that looks like chat capability. >
Not really with getty (unless the "im" initial banner is any good). Alternatives might be to use chat on the cua device after the system is running, or to use some other getty (mgetty is in ports and can either send init strings, or do manual answering with ATA). Or you probably have the option of setting S0=1 and writing to nvram, or maybe setting a dip switch.
