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=kraxel@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 B7C3A212ABF66 for ; Wed, 13 Jun 2018 00:40:07 -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 03518401EF08 for ; Wed, 13 Jun 2018 07:40:07 +0000 (UTC) Received: from sirius.home.kraxel.org (ovpn-116-109.ams2.redhat.com [10.36.116.109]) by smtp.corp.redhat.com (Postfix) with ESMTP id C21E22024CA2; Wed, 13 Jun 2018 07:40:06 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 1E1ED204B7; Wed, 13 Jun 2018 09:40:06 +0200 (CEST) Date: Wed, 13 Jun 2018 09:40:06 +0200 From: Gerd Hoffmann To: Laszlo Ersek Cc: edk2-devel@lists.01.org Message-ID: <20180613074006.pawpkylp5ok76qdz@sirius.home.kraxel.org> References: <20180608113942.17009-1-kraxel@redhat.com> <20180612092140.quczvb74jcmpxr3d@sirius.home.kraxel.org> <8d7c55c4-bf6f-0a31-bcf7-ba030203c51d@redhat.com> MIME-Version: 1.0 In-Reply-To: <8d7c55c4-bf6f-0a31-bcf7-ba030203c51d@redhat.com> User-Agent: NeoMutt/20180512 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.5]); Wed, 13 Jun 2018 07:40:07 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Wed, 13 Jun 2018 07:40:07 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'kraxel@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 07:40:08 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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). cheers, Gerd