Bj?rn Mork wrote :
>
> That's the same experience as I did (except that I used ifconfig to
> load the module). The reason was that I had loaded the serial driver
> and let it grab the IrDA port first. Looks like smc-ircc/irport will
> fail, but force the serial driver away the first time you try to load
> it in this case. That's why it succeeds the second time. I guess this
> is a bug (is it fixed by ir247_drv_region-2.diff?), and that it may
> cause some problems since the serial driver probably still thinks it
> is controlling the port. A simple workaround is not to load serial.o
> first, or use setserial to avoid it detecting the IrDA port as a
> serial port.
ir247_drv_region-2.diff is a cosmetic change and won't help.
That's a know problem without any good solution. It's more
generic, you have other places where two drivers can claim the same
hardware (for example irda-usb and ir-usb). The only solution is to
remove the serial module or set uart to none.
That's also why I usually advise people to try first with
irtty...
> The attached patch will remove all functionality from the power
> management functions but keep them as dummies (in case someone wants
> to add a hardware check/reenable functionality, that probably belong
> here if there is hardware requiring it). The patch will hopefully also
> properly unregister the functions when closing the driver. Testing is
> as usual limited to "it works for me". It makes suspend/resume work as
> expected on the Armada M300, both when irda0 is up and when it's
> down. Without it, the driver fails when resuming if the interface is
> down and causes an oops when suspended if the interface is up.
I don't have any SMC hardware, and no maintainer for the SMC
driver, so I will need convincing before accepting the patch. One
question that come to mind is if the IrDA port is still working after
a resume.
I don't really understand all this Power Management stuff, but
it looks to me that in wakeup you would need to reset the chip (power
up, change speed, whatever). Also, you may want to investigate a bit
the cause of the crash (run oops through ksymoops)...
Regards,
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
