This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Thu Apr 25 09:10:05 2024 Delivery-date: Tue, 08 Feb 2005 16:43:55 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261542AbVBHPji (ORCPT ); Tue, 8 Feb 2005 10:39:38 -0500 Received: from lon-del-02.spheriq.net ([195.46.50.98]:56716 "EHLO lon-del-02.spheriq.net") by vger.kernel.org with ESMTP id S261543AbVBHPh4 (ORCPT ); Tue, 8 Feb 2005 10:37:56 -0500 Received: from lon-inc-06.spheriq.net ([195.46.50.70]) by lon-del-02.spheriq.net with ESMTP id j18FbqDW019347 for ; Tue, 8 Feb 2005 15:37:52 GMT Received: from lon-out-03.spheriq.net (lon-out-03.spheriq.net [195.46.50.131]) by lon-inc-06.spheriq.net with ESMTP id j18FbqIJ013148 for ; Tue, 8 Feb 2005 15:37:52 GMT Received: from lon-cus-01.spheriq.net (lon-cus-01.spheriq.net [195.46.50.37]) by lon-out-03.spheriq.net with ESMTP id j18Fbq38000338 for ; Tue, 8 Feb 2005 15:37:52 GMT Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by lon-cus-01.spheriq.net with ESMTP id j18Fbn7X030378 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Tue, 8 Feb 20 Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 65F69DA49 for ; Tue, 8 Feb 2005 15:37:42 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 60012) id 389AA4734C; Tue, 8 Feb 2005 15:38:39 +0000 (GMT) Received: from zeta.dmz-eu.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id ED3A975995 for ; Tue, 8 Feb 2005 15:38:38 +0000 (UTC) Received: from mail1.ctn.st.com (mail1.ctn.st.com [164.130.116.128]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 4FF83475B1 for ; Tue, 8 Feb 2005 15:38:38 +0000 (GMT) Received: from st.com ([164.130.130.51]) by mail1.ctn.st.com (MOS 3.4.4-GR) with ESMTP id AWB00733 (AUTH "orazio privitera"); Tue, 8 Feb 2005 16:37:44 +0100 (CET) Message-Id: <4208DB49.D5E29AB1@st.com> Date: Tue, 08 Feb 2005 16:31:21 +0100 From: Orazio PRIVITERA X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.kernel.org Cc: Orazio Privitera Subject: Information about Multiple independent framebuffer console on different fb devices Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-O-Virus-Status: No X-O-URL-Status: Not Scanned X-O-CSpam-Status: Not Scanned X-O-Spam-Status: Not scanned X-O-Image-Status: Not Scanned X-O-Att-Status: No X-SpheriQ-Ver: 1.8.3 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org Hello, I would like to get some information about multiple independent framebuffer consoles on different fb devices. Basically I'm working with a scenario of two independent video decoding pipeline which allows to get two video displayed on two TV. In this context, I would like to manage two independent framebuffers on each video decoding. So, is it possible to have 2 concurrent virtual consoles running on the two monitors simultaneously (for example two independent console on the /dev/fb0 and /dev/fb1 framebuffers at the same time) ? Looking at the register_framebuffer function, when the first frame buffer device /dev/fb0 is registered, it calls the take_over_console function (exported by drivers/char/console.c) in order to actually set up the current frame buffer as the system console. But, when the second framebuffer (/dev/fb1) is registered, the register_framebuffer function doesn't set any system console for the /dev/fb1 device. Is there some linux kernel version (or patch) which allows to manage the described scenario? Thanks a lot for any feedback, Best regards OP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/