RE: Mainpine IQ Express Rev3 problems beginning 2.6.36
From: Lee Howard <hidden>
Date: 2011-01-25 15:58:11
-----Original Message----- From: Greg KH [mailto:greg@kroah.com] Sent: Tuesday, January 11, 2011 3:03 PM To: Lee Howard Cc: linux-serial@vger.kernel.org Subject: Re: Mainpine IQ Express Rev3 problems beginning 2.6.36 On Tue, Jan 11, 2011 at 11:16:06AM -0800, Lee Howard wrote:quoted
quoted
-----Original Message----- From: Greg KH [mailto:greg@kroah.com] Sent: Monday, January 10, 2011 4:03 PM To: Lee Howard Cc: linux-serial@vger.kernel.org Subject: Re: Mainpine IQ Express Rev3 problems beginning 2.6.36 On Fri, Dec 17, 2010 at 05:25:19AM -0800, Lee Howard wrote:quoted
quoted
-----Original Message----- From: linux-serial-owner@vger.kernel.org [mailto:linux-serial-owner@vger.kernel.org] On Behalf OfLee Howardquoted
quoted
Sent: Tuesday, December 14, 2010 11:50 AM To: 'Greg KH' Cc: linux-serial@vger.kernel.org Subject: RE: Mainpine IQ Express Rev3 problemsbeginning 2.6.36quoted
quoted
quoted
quoted
quoted
-----Original Message----- From: Greg KH [mailto:greg@kroah.com] Sent: Sunday, December 12, 2010 8:52 AMquoted
As for build issues, try to make a minimal workingconfig for yourquoted
quoted
quoted
system, using 'make localmodconfig'. That willspeed up yourquoted
quoted
quoted
quoted
quoted
build time immensely as well as reduce your chances ofbuild andquoted
quoted
quoted
runtime problems with the intermediate kernels.Thank-you, that did help immensely. Here's the 'git bisect' result... -------------- 7a56aa45982bb87bfca98a2832b5ae782c03364a is the firstbad commitquoted
quoted
quoted
quoted
commit 7a56aa45982bb87bfca98a2832b5ae782c03364a Author: Yegor Yefremov [off-list ref] Date: Wed Jun 16 16:29:55 2010 +0200 serial: add UART_CAP_EFR and UART_CAP_SLEEP flagsto 16C950quoted
quoted
quoted
quoted
UARTs definition Adding UART_CAP_EFR and UART_CAP_SLEEP flags willenable sleepquoted
quoted
mode and automatic CTS flow control for 16C950 UARTs. It will also avoid capabilities detection warning like this: "ttyS0: detected caps 00000700 should be 00000100" Signed-off-by: Yegor Yefremov [off-list ref] Signed-off-by: Greg Kroah-Hartman [off-list ref] :040000 040000 1776ca8d5c653834363c0778b5b404ee52bd2d69 b81cfe4f302a674935181bd248641873820517e5 M drivers -------------- Indeed, if I remove the UART_CAP_EFR flag from later kernel revisions there is no problem.Greg, What's to be done?Sorry for the delay, I think Pavel's posted patch will solve this issue for you, right?I've looked in the linux-serial archives for posts by Pavel for the last month, but I don't see a patch. Please tell me whereI can find this patch. I've attached it below.
Thank you. Sorry for my delay in responding. Yes, the posted patch will solve the issue for me. I was going to look into whether UART_CAP_SLEEP was meaningful without UART_CAP_EFR because I thought I had read somewhere that it was not. But I just haven't managed to make time to do that. Thanks, Lee.