> Stephan von Krawczynski <firstname.lastname@example.org> writes:
> Seems I got somewhat closer now.
> After reading the documentation again, I realised that I was
> the wrong device.
> I belive I read in another file, that the second board started at
> device 32. However device 8 is the first port on the second board.
> And actually that seems to work. (I cant confirm this 100% before
> I get to work tomorrow and actually attach something to the port)
Well, this driver does only support 32 Ports. everyone more crashes
definitely. I haven't seen such a broken source in years. I urge you
to delete the device nodes above 31 to overcome any chance to crash
Most interestingly the moxa-driver is better by far than the mxser. It
seems to me the mxser is _really_ old. If you want to help us all,
please try to contact moxa support and tell them it is high time to
submit a _new_ mxser.c to the kernel tree, because the old (currently
used) one is such a mess. They can do better (proven in moxa.c).
At least a multiboard setup is completely broken. My patch fixes this
but this does not help the main kernel tree.
I cannot submit a patch to marcelo, because I am not the maintainer,
and we all don't want to fork a new mxser-driver apart from the
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:21 EST