From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id CBD80B6F29 for ; Fri, 25 Jun 2010 07:21:00 +1000 (EST) Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id o5OLKvZs015719 for ; Thu, 24 Jun 2010 14:20:57 -0700 (MST) Received: from az33exm25.fsl.freescale.net (az33exm25.am.freescale.net [10.64.32.16]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id o5OLV4AN021502 for ; Thu, 24 Jun 2010 16:31:04 -0500 (CDT) Message-ID: <4C23CC38.9040108@freescale.com> Date: Thu, 24 Jun 2010 16:20:56 -0500 From: Timur Tabi MIME-Version: 1.0 To: Gary Thomas Subject: Re: UCC UART References: <4C20CECB.9050609@mlbassoc.com> <4C20D162.2020302@freescale.com> In-Reply-To: <4C20D162.2020302@freescale.com> Content-Type: text/plain; charset=ISO-8859-1 Cc: Linux PPC Development List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Timur Tabi wrote: > I'd say that there are plenty of unknown issues with this driver/hardware. > For some reason, QE UART is just unreliable. I've had several people try to > use the QE for UART, and almost everyone has problems with it. I finally got in touch with one of the other development teams, and they said that they got QE UART working with the 8569 and the P1021. The reference board we make with the 8568 does not have QE pinned to the UART, so they didn't try to support that.