From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id CDAC7B6F90 for ; Fri, 26 Aug 2011 02:06:23 +1000 (EST) Date: Thu, 25 Aug 2011 08:50:50 -0700 From: Greg KH To: Timur Tabi Subject: Re: [PATCH] [v4] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver Message-ID: <20110825155050.GA10084@kroah.com> References: <1314286345-27056-1-git-send-email-timur@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1314286345-27056-1-git-send-email-timur@freescale.com> Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Aug 25, 2011 at 10:32:25AM -0500, Timur Tabi wrote: > The ePAPR embedded hypervisor specification provides an API for "byte > channels", which are serial-like virtual devices for sending and receiving > streams of bytes. This driver provides Linux kernel support for byte > channels via three distinct interfaces: > > 1) An early-console (udbg) driver. This provides early console output > through a byte channel. The byte channel handle must be specified in a > Kconfig option. > > 2) A normal console driver. Output is sent to the byte channel designated > for stdout in the device tree. The console driver is for handling kernel > printk calls. > > 3) A tty driver, which is used to handle user-space input and output. The > byte channel used for the console is designated as the default tty. > > Signed-off-by: Timur Tabi No, this doesn't work, I need just a fix, as I took your previous patch already. greg k-h