From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH] tools/firmware: use a canned config for seabios
Date: Wed, 29 Mar 2017 10:28:15 +0000 [thread overview]
Message-ID: <99d0c13a0f47472098e4ff4f845c7f01@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170327143446.dqulx4g3oo7gxdjz@citrix.com>
> -----Original Message-----
[snip]
> > > > This patch adds the canned configuration into tools/firmware and
> modifies
> > > > the Makefile rule to copy it into place.
> > > >
> > >
> > > I think at some point someone (you?) tried to change the default
> > > upstream, what was the outcome?
> > >
> >
> > Yes I tried that. The maintainers nacked the patch.
> >
> > > I'm not against shipping a default config, but that wouldn't benefit all
> > > the distros that use their own seabios packages.
> > >
> >
> > No, but the status quo sucks. One hopes distros building their own Xen
> packages already choose a better firmware config. This patch makes the
> config for those rolling their own firmware better (and I suspect that's quite a
> few folks).
> >
>
> I forgot to ask: what exactly in this config file is different from the
> default one?
>
The commit message tells you... It turns on wide PIO and DMA for interaction with the emulated IDE controller.
Paul
> Wei.
>
> > Paul
> >
> > > Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-29 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 17:03 [PATCH] tools/firmware: use a canned config for seabios Paul Durrant
2017-03-24 11:46 ` Wei Liu
2017-03-24 11:54 ` Paul Durrant
2017-03-27 14:34 ` Wei Liu
2017-03-29 10:28 ` Paul Durrant [this message]
2017-03-29 10:40 ` Wei Liu
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=99d0c13a0f47472098e4ff4f845c7f01@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).