From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ZxB0Z-000187-2z
	for mharc-grub-devel@gnu.org; Fri, 13 Nov 2015 04:51:03 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52563)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <prvs=7522a583b=Ian.Campbell@citrix.com>)
	id 1ZxB0W-000130-V0
	for grub-devel@gnu.org; Fri, 13 Nov 2015 04:51:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <prvs=7522a583b=Ian.Campbell@citrix.com>)
	id 1ZxB0R-000452-UD
	for grub-devel@gnu.org; Fri, 13 Nov 2015 04:51:00 -0500
Received: from smtp.citrix.com ([66.165.176.89]:54586)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <prvs=7522a583b=Ian.Campbell@citrix.com>)
	id 1ZxB0R-00044y-PO
	for grub-devel@gnu.org; Fri, 13 Nov 2015 04:50:55 -0500
X-IronPort-AV: E=Sophos;i="5.20,286,1444694400"; d="scan'208";a="312036188"
Message-ID: <1447408236.18450.117.camel@citrix.com>
Subject: Re: [Xen-devel] Uniform commands for booting xen
From: Ian Campbell <ian.campbell@citrix.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>, The development of GNU GRUB
	<grub-devel@gnu.org>
Date: Fri, 13 Nov 2015 09:50:36 +0000
In-Reply-To: <CAA91j0Wz++uchzCDwDEPBSf+k2kYy7iMEuPJfWBSap-ZQq_X2A@mail.gmail.com>
References: <56449726.8090707@gmail.com>
	<5644C1F502000078000B455F@prv-mh.provo.novell.com>
	<1447348140.18450.92.camel@citrix.com>
	<5645A3E802000078000B495A@prv-mh.provo.novell.com>
	<CAA91j0Wz++uchzCDwDEPBSf+k2kYy7iMEuPJfWBSap-ZQq_X2A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.18.1-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-DLP: MIA1
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 66.165.176.89
Cc: Vladimir Serbinenko <phcoder@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: The development of GNU GRUB <grub-devel@gnu.org>
List-Id: The development of GNU GRUB <grub-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 09:51:01 -0000

On Fri, 2015-11-13 at 12:04 +0300, Andrei Borzenkov wrote:
> > How do you express modules other than kernel+initrd in that
> > scheme, without grub needing to be aware of any new addition we
> > may find necessary going forward?
> > 
> 
> Are modules used by Xen self-identifying? Is it enough to simply pass
> Xen kernel list of binary blobs or Xen kernel must be told what these
> binary blobs are? If they are self identifying, why arm needs to be
> passed module type in the first place?

At first Xen/ARM required the bootloader to identify, but that was since
identified as causing madness and fixed by having Xen/ARM do as Xen/x86
does and figure things out for itself, but I failed to communicate this
clearly and things got implemented on the grub side under the old
assumptions.

I just replied in more detail about that to Jan's mail, so I won't repeat
myself further here.

Ian.