It has been some time since I looked at the code butI don't think the 32 bit code was different from the 64 bit code. I think they both had the same bug. I wrote a patch for the 2.6 kernel code. But I think it got fixed for real for kernel 3.2. I could probably dig up my 2.6 patch if someone needs it but I don't even use it myself any more. I just use either a 2.6.32 kernel or a 3.2 kernel. PS: some of the earlier 3.2 kernels also had the bug. But the stock debian, ubuntu, and grml kernels do not have it any more. On 05/28/13 05:48, covici at ccs.covici.com wrote: > Because they made some changes which causes a particular return code > when trying to get the serial port, but if you make the change it still > will work. Its a workaround because it does not really solve the > problem, but it gets us by till we can really fix things. > > Tony Baechler <tony at baechler.net> wrote: > >> No, I haven't. Why should I? It works great on my 64-bit Linux with the >> 2.6.32 kernel. I used it a couple of times today. I must say that Linux >> is much faster at copying files to my SD cards. If you can give me some >> idea why 32-bit kernel 3.2 wouldn't find the serial ports when 64-bit >> kernel 2.6.32 does, I'm most interested. >> >> On 5/27/2013 6:40 PM, acollins at icsmail.net wrote: >>> HiTony. Have you looked at /proc/ports to see if your serial ports >>> are being registered? If not, have you looked to make sure you don't >>> have a serial port module that needs to be loaded? Just a couple of >>> thoughts. >> _______________________________________________ >> Speakup mailing list >> Speakup at linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > -- --- John G. Heim, 608-263-4189, jheim at math.wisc.edu
