All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Oldeman <Bart.Oldeman@bristol.ac.uk>
To: linux-msdos@vger.kernel.org
Subject: Re: some problems (1.1.5 and 1.1.4)
Date: Tue, 1 Jul 2003 12:16:36 +0100 (BST)	[thread overview]
Message-ID: <Pine.SOL.3.95q.1030701121200.27951A-100000@eis.bris.ac.uk> (raw)
In-Reply-To: <20030701101941.48416.qmail@web20204.mail.yahoo.com>

On Tue, 1 Jul 2003, Will Styles wrote:

> --- Justin Zygmont <jzygmont@solarflow.dyndns.org> wrote:
> > i'll try.  however when I managed to try again with 1.1.4, the problem was 
> > there, just not quite as bad.  
> well the patchset number is really critical here...
> 
> > So I don't know if it'll make much 
> > difference if it was like that all along.
> > 
> i'm not concerned with persistent problems.
> i'm more concerned about this: if the situation gets *drastically* worse from
> 1.1.4.9 to 1.1.4.10, i know what the problem is. so i am most interested in
> these 2 revisions.

hmm what would be the problem in 1.1.4.10? I can see
+       - allow DSP commands in high speed mode (fixed problem with
+         Pinball Dreams 2)

@@ -754,7 +753,7 @@
   case 0x0C:           /* dsp write register */
                if (SB_dsp.dma_mode & HIGH_SPEED_DMA) {
                  S_printf("SB: Commands are not permitted in High-Speed DMA mode!\n");
-                 break;
+                 /* break; */
                }
                sb_dsp_write ( value );
                break;

Does this change make all the difference for you? Funny...

Bart


  reply	other threads:[~2003-07-01 11:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 11:51 some problems (1.1.5 and 1.1.4) Will Styles
2003-06-30 17:39 ` Justin Zygmont
2003-07-01 10:19   ` Will Styles
2003-07-01 11:16     ` Bart Oldeman [this message]
2003-07-01 22:49     ` Justin Zygmont
2003-07-04  3:32 ` Justin Zygmont
2003-07-04 18:10   ` (unknown) Darryl Perry
2003-07-04 18:21     ` your mail Ged Haywood
2003-07-05 14:48       ` Jim Hartley
2003-07-05 14:53         ` Ged Haywood
     [not found]           ` <1057435822.2023.49.camel@tamriel.terranforge.com>
2003-07-06  4:06             ` Jim Hartley
2003-07-06 11:20               ` Jochen Reinwand
2003-07-06 11:56                 ` Ged Haywood
2003-07-06 16:26                   ` Jochen Reinwand
2003-07-06 19:03                     ` Eemeli Kantola
2003-07-06 23:10                       ` Jochen Reinwand
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01 11:26 some problems (1.1.5 and 1.1.4) Will Styles
2003-07-01 11:06 Bart Oldeman
2003-06-25 17:39 Stas Sergeev
2003-06-25 21:11 ` Justin Zygmont
2003-07-04  5:26 ` Justin Zygmont
2003-06-25 17:30 Stas Sergeev
2003-06-26  1:27 ` Ryan Underwood
2003-06-15 12:48 Stas Sergeev
2003-06-24 23:21 ` Ryan Underwood
2003-06-25  0:50   ` Justin Zygmont
2003-06-14 10:09 Jan Willem Stumpel
2003-06-14 10:36 ` Bart Oldeman
2003-06-14 23:58   ` Ryan Underwood
2003-06-14 17:17 ` Justin Zygmont
2003-06-14 19:42   ` Jan Willem Stumpel
2003-06-14 23:57     ` Ryan Underwood

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=Pine.SOL.3.95q.1030701121200.27951A-100000@eis.bris.ac.uk \
    --to=bart.oldeman@bristol.ac.uk \
    --cc=linux-msdos@vger.kernel.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 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.