All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: xen-devel@lists.xensource.com, Pat Campbell <plc@novell.com>
Subject: Re: [PATCH][IOEMU] Dynamic modes support for PV xenfb (2 of 2)
Date: Sat, 12 Jan 2008 15:46:35 +0000	[thread overview]
Message-ID: <20080112154635.GA12159@redhat.com> (raw)
In-Reply-To: <87lk6vscyh.fsf@pike.pond.sub.org>

On Sat, Jan 12, 2008 at 08:46:46AM +0100, Markus Armbruster wrote:
> "Pat Campbell" <plc@novell.com> writes:
> 
> >>>> On Thu, Jan 10, 2008 at  3:18 AM, in message
> > <87ejcqhtku.fsf@pike.pond.sub.org>, Markus Armbruster <armbru@redhat.com>
> > wrote: 
> >> "Pat Campbell" <plc@novell.com> writes:
> >> 
> >>> Attached patch adds multiple frame buffer size support to the xenfb PV 
> >>> backend QEMU xenfb.  Backend sets feature-    resize and handles the
> >>> resize frame buffer event.
> >>>
> >>> Corresponding frontend LINUX patch is required for functionality but this
> >>> patch is not dependent on it, preserving backwards compatibility.
> [...]
> >> By the way, the feature negotiation only covers whether the frontend
> >> is permitted to resize, not acceptable resolutions.
> >
> > True.  Acceptable resolutions are what fits within a 5MB framebuffer
> > and has a width no greater than 1280.
> 
> Is this enough for all eternity?  Screen resolutions continue to
> grow...  If it's not, then how can we ensure that we can enlarge it
> easily while maintaining backwards compatibility?
> 
> Perhaps the backend could publish the maximum resolution it can
> accept, instead of just a flag that it can accept resize events.

Maximum resolutions are not well defined because they vary according
to your aspect ratio - normal vs widescreen. I increasingly like the
like of having a 'videoram' parameter in the backend config, so the
admin can set as large a value as they feel neccessary, and frontend
then set whatever resolutions they like within the constraint of that
value.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2008-01-12 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 15:34 [PATCH][IOEMU] Dynamic modes support for PV xenfb (2 of 2) Pat Campbell
2008-01-10 10:18 ` Markus Armbruster
     [not found]   ` <47872348.3E48.0018.0@novell.com>
2008-01-12  7:46     ` Markus Armbruster
2008-01-12 15:46       ` Daniel P. Berrange [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-11 15:15 Pat Campbell

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=20080112154635.GA12159@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=plc@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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.