Markus Biermaier wrote :
>
> Linux linuxpb 2.2.18 #1 Wed Dec 20 16:42:41 GMT 2000 ppc unknown
By any chance, did you tried 2.4.X ? No promise there, but I
don't remember much about 2.2.X.
> - "kernel: irlap_change_speed(), setting speed to 0"
That can't be right. I suspect there is an endianess issue in
qos.c. Check that the speed negociation is done properly.
> Q1 How does speed change work?
Like you describe.
> Q2 Where in the communication process is this?
In the LAP connection. It's called qos in the code.
> Q3 Is there a problem with my settings or the IrDA driver?
Don't think so, otherwise discovery would not work.
> Q4 What does "setting speed to 0" mean? This is normaly a "modem hangup" ?!?
Looks like a bug.
> Q5 How can I set the speed on the Linux side?
Speed is automatically negociated to the lowest common denominator.
> Q6 Why are the speed settings for IR in some applications disabled? This
> is for example in the "Comms" software on the MC218:
> If the port is "Serial 0" I can change baud, databits, stopbits, parity,
> flow control. When the port is "Infrared" I can adjust nothing.
IrDA automatically negociate that at IrLAP. The virtual serial
port that the app connect to (ircomm0) is only a virtual serial port.
Regards,
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
