From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from av.mvista.com (gateway-1237.mvista.com [12.44.186.158]) by ozlabs.org (Postfix) with ESMTP id BD76368246 for ; Sat, 10 Sep 2005 07:31:33 +1000 (EST) Date: Fri, 9 Sep 2005 14:32:20 -0700 From: "Mark A. Greer" To: goog long Message-ID: <20050909213220.GC5034@mag.az.mvista.com> References: <20050909151714.68070.qmail@web33410.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20050909151714.68070.qmail@web33410.mail.mud.yahoo.com> Cc: linuxppc-dev@ozlabs.org Subject: Re: Serial driver problem from 2.6.12 kernel List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Sep 09, 2005 at 08:17:14AM -0700, goog long wrote: > Hi all, > > I backported MPSC driver from 2.6.12 to my kernel > 2.6.10. However, the driver can send characters, but > cannot receive any characters. Have anyone seen this > before? > > Please also send your feedback to cecolong@yahoo.com Hmm, a little sparse on info here so its hard to guess. The mpsc driver is very much influenced by the platform_data that you pass to it (since there are so many options). One possibility is that you have the max_idle platform_data field set to 0 which means that the mpsc reciever will not timeout and therefore the mpsc will not pass to the driver whatever you've typed until your receive buffer fills up (which you may not have done in your testing). Try a max_idle value of 40 which seems to work fine for me. Another possibility, of course, is that you passed in the wrong irq in the platform_data and therefore are not getting recieving interrupts. Mark