From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id F339BDDEA0 for ; Tue, 7 Aug 2007 05:15:49 +1000 (EST) In-Reply-To: <200708051841.17471.arnd@arndb.de> References: <200708050135.07753.arnd@arndb.de> <200708051841.17471.arnd@arndb.de> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: 8250.c::autoconfig() fails loopback test on MPC824[15] Date: Mon, 6 Aug 2007 21:15:34 +0200 To: Arnd Bergmann Cc: linuxppc-dev@ozlabs.org, Guennadi Liakhovetski , linux-serial@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > Another option altogether would be to allow the device node to > specify the linux specific serial port flags in a separate property, > like "linux,uart-port-flags" that contains the same flags that > setserial can set from user space. That would also be useful > if you want to specify UPF_MAGIC_MULTIPLIER on certain high-speed > ports, because it cannot be autoprobed. Such high-speed ports should simply use a proper "compatible" entry. Similarly with the problem at hand. Segher