qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Natalia Portillo <iosglpgc@teleline.es>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OPENSTEP challenge...
Date: Tue, 5 Apr 2005 11:17:40 +0100	[thread overview]
Message-ID: <66cc62eb6b9c90921fdba4d679407601@teleline.es> (raw)
In-Reply-To: <9087.1112653911@www49.gmx.net>

Hi!

What are exactly the setup options you selected (when it asks for 
drivers)?

IT is known that OpenStep has some installer bugs, so this is important 
on some hardware.

Also what OpenStep version are you testing? 4.0, 4.1 or 4.2?

There are drivers for AMD Lance, and OpenStep supports Sound Blaster 16 
(teorically both ISA and ISA PnP but never got work ISA PnP driver on 
NeXTStep 3.3 nothing known about the 4.x version).
I think that there are also drivers for CL VGA cards.

Did you tested Rhapsody? I've tested (http://www.claunia.com/qemu) it 
but installer bug shows!
And I've lost my floppy disks so I can't test more.

Regards

El 04/04/2005, a las 23:31, Patrick Schulz escribió:

> Hello Qemu developers!
>
> Are you up for a challenge? Do you want to add another OS to your list 
> of
> supported ones? Here's your chance... :-)
> For quite some time I've tried to use OPENSTEP 4.2 on qemu. In 
> principle it
> works, but here are the details:
>
> plain VGA works (gives you 640x480 b/w screen)
> EIDE works (hard drives work)
> PCI works,
> ISA works,
> PS/2 mouse doesn't work (freezes after one move)
> Keyboard works (as long as PS/2 mouse doesn't lock up)
> serial mouse doesn't work (using the slsnif workround)
> VESA graphics work, but incorrect (16bit modes produce too dark colors 
> in
> graphics mode, 8 bit modes don't produce anything useful)
> cirrus-logic VGA - unknown
> NE2000 - unknown
> SoundBlaster - unknown
>
> The most important thing is the mouse. You can't use OPENSTEP without 
> it.
> All tests were done on qemu 0.6.1 or several newer CVS snapshots. I 
> also
> used the Xlib-only patch and the rfb patch, the result is always the 
> same:
> as soon as you start moving the mouse, the cursor moves a bit and then 
> locks
> up (no more events) and the keyboard stops working. The Windows Qemu 
> shows
> the same behaviour.
> The OPENSTEP PS/2 mouse driver seems to be very picky, since VMware 
> also has
> problems with it (generates random events), Bochs however has no 
> problems
> with the PS/2 mouse, but is painfully slow.
> An alternative would be to emulate a serial mouse or to use the serial 
> port
> of the host to attach a serial mouse (I can use VMware this way).
> One more thing I discovered, if you generate many mouse events during
> boot-up of  OPENSTEP (before the PS/2 driver has been loaded) the IDE
> controller "looses" it's disks, you see timeouts and bus resets, but
> OPENSTEP can't recover from it.
>
> Unfortunately I don't have enough time to fix the mouse issues, but I'm
> willing to help getting OPENSTEP to run on qemu. As soon as the mouse 
> works
> I can continue to test the other components. To get everything 
> working, qemu
> needs to have ISA and PCI bus working at the same time (SB16 and 
> NE2000 need
> to be ISA devices, VESA only works on PCI) or qemu adds new PCI 
> "hardware"
> such as an AMD Lance network adapter instead the NE2000.
>
> What do you think?
>
> PS  to moderator: I resent the message but without picture this time, 
> sorry.
>
> -- 
> Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

      reply	other threads:[~2005-04-05 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 22:31 [Qemu-devel] OPENSTEP challenge Patrick Schulz
2005-04-05 10:17 ` Natalia Portillo [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=66cc62eb6b9c90921fdba4d679407601@teleline.es \
    --to=iosglpgc@teleline.es \
    --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).