WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Shall we put open source firmware source in XEN/IA6

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] Shall we put open source firmware source in XEN/IA64 tree
From: Aron Griffis <aron@xxxxxx>
Date: Mon, 17 Sep 2007 08:41:47 -0400
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 17 Sep 2007 05:41:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1189999524.4188.66.camel@bling>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Alex Williamson <alex.williamson@xxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
References: <823A93EED437D048963A3697DB0E35DEB586DC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1189688329.46e93409af340@xxxxxxxxxxx> <1189686743.4188.43.camel@bling> <20070916192325.GB18952@xxxxxxxxx> <1189999524.4188.66.camel@bling>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-11)
Alex Williamson wrote:  [Sun Sep 16 2007, 11:25:24PM EDT]
>    I'm not sure we want to add a 2MB binary into the tree that the
> majority of users (x86) don't need.

Oh right.  I forget sometimes that we merge with x86 xen-unstable.hg
:-)

>    Would a distro really want to pull a binary blob out of mercurial for
> a GFW, or would they want to package up efi-vfirmware.hg so they can
> make modification and add bug fixes w/o being dependent on upstream?

Good point.  RHEL packages the Intel GFW as a binary blob, so I was
basing my thoughts on that, but clearly the situation is different.

> > If you'd rather keep it out of the repo, maybe it could be downloaded
> > via another make target, which would then be integrated to the
> > top-level make default target.  That way a "make install" doesn't have
> > further network dependencies.
> 
>    Another make target would be fine.  Seems like it would logically fit
> somewhere under the tools make hierarchy.  Thanks,

Works for me, thanks

Aron

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel