From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2A68521244A74 for ; Wed, 13 Jun 2018 09:16:51 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id EC25781663E0 for ; Wed, 13 Jun 2018 16:16:50 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-122-190.rdu2.redhat.com [10.10.122.190]) by smtp.corp.redhat.com (Postfix) with ESMTP id 782472026987; Wed, 13 Jun 2018 16:16:50 +0000 (UTC) To: Gerd Hoffmann Cc: edk2-devel@lists.01.org References: <20180608113942.17009-1-kraxel@redhat.com> <20180612092140.quczvb74jcmpxr3d@sirius.home.kraxel.org> <8d7c55c4-bf6f-0a31-bcf7-ba030203c51d@redhat.com> <20180613074006.pawpkylp5ok76qdz@sirius.home.kraxel.org> From: Laszlo Ersek Message-ID: <12d95558-f4cd-50a6-b873-965bdaebd331@redhat.com> Date: Wed, 13 Jun 2018 18:16:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180613074006.pawpkylp5ok76qdz@sirius.home.kraxel.org> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Wed, 13 Jun 2018 16:16:50 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Wed, 13 Jun 2018 16:16:50 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:'' Subject: Re: [PATCH 0/4] Add QemuRamfbDxe driver X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 16:16:52 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 06/13/18 09:40, Gerd Hoffmann wrote: > Hi, > >>>> - What happens if you locate the parent handle (with the VenHw node) >>>> and/or the child handle (with the GOP on it), and try to disconnect them? >>> >>> How can I do that? >> >> Run "dh -d -v -p GraphicsOutput". The listing will include all handles >> (represented by hex identifiers) that carry a GOP. Each handle will also >> have its device path protocol instance displayed, in textual >> representation, so if there are multiple GOPs, you'll be able to locate >> the one produced by QemuRamfbDxe. The listing should also reference the >> parent controller handle. >> >> Knowing the hex identifiers for parent and child, experiment with the >> "disconnect" command. (See "help disconnect" for syntax.) > > Shell> dh -p GraphicsOutput > Handle dump by protocol 'GraphicsOutput' > 44: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput) DevicePath(..C08C457)/AcpiAdr(0x80010300)) > 6D: GraphicsOutput(GraphicsOutput) SimpleTextOut > Shell> disconnect 6d > Disconnect - (6D,3E643560,3E5C3A03) Result Success. > Shell> disconnect 44 > Disconnect - (44,3E643560,3E5C3A03) Result Success. > Shell> > > The second disconnect makes ovmf stop using ramfb as console (serial continues > to work). I'll follow up under your v3 series: [edk2] [PATCH v3 0/4] Add QemuRamfbDxe driver http://mid.mail-archive.com/20180613072936.12480-1-kraxel@redhat.com Thanks, Laszlo