Are you saying the bug was fixed by modifying speakup to open the serial port the right way? That problem is gone? On 05/01/13 13:13, Samuel Thibault wrote: > John G. Heim, le Wed 01 May 2013 13:05:23 -0500, a ?crit : >> But that's no answer. This is the same problem I had with the responses I >> got on the linux-kernel list. I asked extremely specific questions below >> and just saying no isn't enough. > > That's an XYZ problem. People won't answer Y because the actual issue is > X, whose answer is Z. > >> Specifically, what is wrong with my patch? > > It's dealing with Y, not X. > >> Does speakup need to call request_reggion at all? > > It shouldn't have to. > >> If so, why,? What does request_region do? > > Try to circumvent the kernel. > >> It looks as if request_region always fails if you request >> a region at the address of the serial port even if the serial port is not in >> use? Why is that? If this behaviour is by design, what is the speakup code >> supposed to do instead? > > It is supposed to open the serial code a correct way. > > Samuel > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >
