All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
	<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: vgabios and other guest related firmware
Date: Wed, 02 Jan 2008 11:29:54 +0200	[thread overview]
Message-ID: <477B5992.9060704@qumranet.com> (raw)
In-Reply-To: <20080102044438.GB8605@tapir>

Carlo Marcelo Arenas Belon wrote:
> Avi,
>
> now that vgabios has been merged, would be probably a good idea to remove the
> unused vgabios BLOBs in the bios directory which were left from the import of 
> the BOCHS bios (I have a patch but felt bad about sending it out with up to
> 96K) :
>
>   bios/VGABIOS-lgpl-README              |  214
>   bios/VGABIOS-lgpl-latest              |  Bin 38400 -> 0 bytes
>   bios/VGABIOS-lgpl-latest-cirrus       |  Bin 35328 -> 0 bytes
>   bios/VGABIOS-lgpl-latest-cirrus-debug |  Bin 35840 -> 0 bytes
>   bios/VGABIOS-lgpl-latest-debug        |  Bin 39936 -> 0 bytes
>
>   

A git patch would have been quite small.  Anyway, I removed the files.

> in preparation for portability work, I suspect though might be a good idea to
> create a "firmware" tree were other firmware might be later added to support
> the non-PC architectures like ppc, ia64 and others that seem to be imminent.
>
> I'll let the specifics to all the portability interested parties (I mostly use
> PC) but would suspect something similar to the work done for the code should
> be most likely what is needed :
>
>   firmware -- x86 -- bios
>            |      |- vgabios
>            |- ia64
>            ..
>   

While this is a good suggestion, the mechanics of the cvs import -> git 
conversion are nasty enough for me not to want to change things.

New firmware can certainly go into the new directory as you suggest.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      parent reply	other threads:[~2008-01-02  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02  4:44 vgabios and other guest related firmware Carlo Marcelo Arenas Belon
2008-01-02  8:14 ` Zhang, Xiantao
     [not found]   ` <42DFA526FC41B1429CE7279EF83C6BDCBB773B-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-02  9:30     ` Carlo Marcelo Arenas Belon
2008-01-02  9:36       ` Avi Kivity
     [not found]         ` <477B5B2F.7080304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-02  9:46           ` Zhang, Xiantao
     [not found]             ` <42DFA526FC41B1429CE7279EF83C6BDCBB77B5-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-02  9:52               ` Avi Kivity
     [not found]                 ` <477B5EC8.4060101-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-02  9:57                   ` Zhang, Xiantao
2008-01-02 10:29               ` Carlo Marcelo Arenas Belon
2008-01-02  9:54       ` Zhang, Xiantao
2008-01-02  9:29 ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=477B5992.9060704@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.