qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Bob Breuer <breuerr@mc.net>
Cc: qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: [Qemu-devel] Re: sun framebuffer selection (was option-rom)
Date: Sun, 6 Jun 2010 07:32:22 +0000	[thread overview]
Message-ID: <AANLkTinyCMWHAgn_p5c7Pb4feewg4GOKPOypWQpbqEgO@mail.gmail.com> (raw)
In-Reply-To: <4C0AD980.8040206@mc.net>

On Sat, Jun 5, 2010 at 11:10 PM, Bob Breuer <breuerr@mc.net> wrote:
> Blue Swirl wrote:
>>  but again: should we have a new machine with cg14 or
>> some switch to select TCX vs. cg14?
>>
>> Maybe the recently proposed machine subtype patches could help here.
>>
> Well, let's try to figure out a method of selecting the framebuffer
> type.  I'll try to list some of the options, even if they might be
> ridiculous.
>
> 1) Use the -vga option.  I know TCX and cg14 are not vga, but I think
> it's the closest existing command line option available.
>
> 2) Switch based on the -g WxH option.  At the moment, the TCX emulation
> doesn't really handle anything other than 1024x768, so switch to cg14
> for other resolutions if supported.
>
> 3) Use some other existing command line option, -device, -set or
> -global?  Might work, but the syntax may not be easy to remember.

We don't have an equivalent of -chardev, -netdev and -drive for displays.

> 4) Machine subtype.
>
> 5) New command line option.  Anything above might be better.
>
> 6) New machine type.  Is it a big enough feature to demand it's own
> machine type?  Maybe, but see next option.
>
> 7) Select as default video for SS-20.  The SS-10 and SS-600MP are
> already very similar.  This would allow for some differentiation between
> the machines, but there could still be an option to switch back to TCX.
> Note that TCX was really only available for the SS-4 and SS-5.
>
>
> Is there anything else that I missed?

Combined 7 & 6: make cg14 default for SS-20, add a deprecated
compatibility machine for SS-20 with TCX.

>
> I'm going to go ahead with option 2 in the short term.  I'm inclined to
> narrow it down to options 1, 4, and 7.  I know that 7 would have
> backwards compatibility concerns.  The cg14 seems to have at least the
> same capabilities as TCX so there shouldn't be any loss of
> functionality.  Even though SS-20 is not the default machine, do you
> know of any OS that works with the sun4m implementation today but
> doesn't have a cg14 driver?  Possible downside to cg14 for video is that
> any "acceleration" is handled by the SX pixel processor which has no
> available documentation.  TCX also has some amount of unimplemented
> acceleration.

It would be nice to use some basic device with well defined
acceleration or just a frame buffer as default.

  reply	other threads:[~2010-06-06  7:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 17:40 [Qemu-devel] option-rom (was cg14) Artyom Tarasenko
2010-06-04 19:28 ` [Qemu-devel] " Blue Swirl
2010-06-05 20:25   ` Bob Breuer
2010-06-05 20:35     ` Blue Swirl
2010-06-05 23:10       ` [Qemu-devel] sun framebuffer selection (was option-rom) Bob Breuer
2010-06-06  7:32         ` Blue Swirl [this message]
2010-06-06 16:28           ` [Qemu-devel] " Artyom Tarasenko
2010-06-09 19:43             ` Blue Swirl

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=AANLkTinyCMWHAgn_p5c7Pb4feewg4GOKPOypWQpbqEgO@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=atar4qemu@googlemail.com \
    --cc=breuerr@mc.net \
    --cc=qemu-devel@nongnu.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).