From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cC0wF-0006iG-4T for qemu-devel@nongnu.org; Wed, 30 Nov 2016 04:12:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cC0w9-0000pm-DV for qemu-devel@nongnu.org; Wed, 30 Nov 2016 04:12:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49300) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cC0w9-0000p3-5w for qemu-devel@nongnu.org; Wed, 30 Nov 2016 04:12:21 -0500 References: <20161130010151.GL2546@bill-the-cat> <20161130080232.whbjegirbddf5ned@aurel32.net> From: Thomas Huth Message-ID: <3bc775a3-6fdd-4ead-571e-2f316b0d969f@redhat.com> Date: Wed, 30 Nov 2016 10:12:09 +0100 MIME-Version: 1.0 In-Reply-To: <20161130080232.whbjegirbddf5ned@aurel32.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2t6Ml7olQtlrxvoE2dadmfTLGjJWfxI54" Subject: Re: [Qemu-devel] qemu-system-sh4 vs qemu-system-arm/i386 default behavior List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelien Jarno Cc: Tom Rini , qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2t6Ml7olQtlrxvoE2dadmfTLGjJWfxI54 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 30.11.2016 09:02, Aurelien Jarno wrote: > On 2016-11-30 08:33, Thomas Huth wrote: >> On 30.11.2016 02:01, Tom Rini wrote: >>> Hey all, >>> >>> I'm trying to make use of the r2d platform for U-Boot testing via QEM= U. >>> After applying a series[1] I can use the kernel.org sh4 toolchain to = get >>> a u-boot.bin that runs, mostly. I say mostly as first of all I have = to >>> pass "-monitor null -serial null -serial stdio -nographic" to >>> qemu-system-sh4 and in that order for me to get output from U-Boot on= >>> the prompt. On other platforms such as arm and vexpress or i386 and = the >>> 'pc' machine I do not need to do this. Does anyone have any idea why= >>> this might be and where to start poking in the code to fix this? >=20 > The reason is that u-boot and the linux kernel do not have the same way= > to number the serial port than the physical hardware. Therefore u-boot > and the Linux kernel use the second physical serial port .The question = is > whether we should number our ports from the software (or part of the > sofrware) or hardware point of view. OK, thanks for the explanation, that makes sense now. ... maybe we should put this information on a SH4 machine page under http://qemu-project.org/Documentation/Platforms so that users have a possibility to understand this serial port numbering? Thomas --2t6Ml7olQtlrxvoE2dadmfTLGjJWfxI54 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYPpfwAAoJEC7Z13T+cC21fcgQAJ8EXEuRJIuDOLQmUGaCXXcp 21b6jAsu36fSmB1/3tipeeax0Ovs4l4Gp2MBYz02TxnHeU8G3fWoC60uzCUePpt/ s0gANmj3aV4DcBHwZaQmZt7E+PX/y2rDpAPMd6GSBNXXMFwOGbCwNcQIzkzB/rEW yh3mJJkTcL53KXgQyiKOvbGJ2kkc9QlvMXmzPtNpETTZCVnE83/eV9tG489Onls4 jESO58GUqS7TMyFh567La+p2Wd24VqKPiLuxffiOGOb+hkzKGFyBuD5NDYvd7Ihv C3HWrI8ayYytzjeTDYCa9fwhoGJxFDmeWojYWws4/B8K+EDt9UejYM5w+xXQ3sWN Pgxemqbo5QXwUwZhrhlEdQI3rjKDdy6VAv/7wwI3IMXxI3DDtQXkLH6O65NFDUJj GHjZgUQbMwlZ4XyMvtCRPcJhb9iOqI+J6raZoRPNZJOPsfxTM3Ypl9yPsamFi+8h 3lMxMNgbLqQIkem7TA8YB9fTPBvWUNr50II/qGFtVvKFTpZ7JtPgyg6x7xw/XaYC pOK2wQW9/93SMBy5m+rOnJzj0uWRMBmScis5ETYV2Wq4TPPcFBKBVigoYUcnHlTz HTjosldNImurOAO30SWnwmWSZoNF7VKKm7sWdvcxS8VEqKg/FB684lSX78smtFwL l8bSxnEsY+jHCt//MD+k =Ran9 -----END PGP SIGNATURE----- --2t6Ml7olQtlrxvoE2dadmfTLGjJWfxI54--