On Mon, 13 Aug 2001, Lennart Augustsson wrote:
> I don't know why ucom0 only works in one direction, but I can
> explain the `strange...' message.  After the hub driver turns on power
> on a port it then checks the status bits for the port to check that it
> is powered, if it isn't you get the message.  But since the umct driver
> seems to attach fine anyway I would worry about that message.

Um, you mean "wouldn't"? :->

Anyways, I=E4ve turned on ucom and umct debugging. Sending it a stream of
"at\n"s, i just see a sequence of messages from ucomstart and ucomwritecb,
but nothing indicating a read.

Just for kicks I also connected a printer (HP DeskJet 720C) to the ulpt
port, and sending stuff (text, output from gs' deskjet driver) didn't
reault in anything. I wonder if the umct driver needs a swift kick...
(then again ulpt gets attached directly, not via umct)

Clueless.


 - Hubert

--=20
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.htm=
l
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.htm=
l=20
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org=
/