On Sat, Jan 12, 2008 at 08:46:46AM +0100, Markus Armbruster wrote:
> "Pat Campbell" <plc@xxxxxxxxxx> writes:
>
> >>>> On Thu, Jan 10, 2008 at 3:18 AM, in message
> > <87ejcqhtku.fsf@xxxxxxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>
> > wrote:
> >> "Pat Campbell" <plc@xxxxxxxxxx> 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 -=|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home