From mboxrd@z Thu Jan 1 00:00:00 1970 From: x.zupftom@web.de Subject: Re: MIDI input patch Date: Fri, 17 Jul 2009 13:10:08 +0200 Message-ID: <716672598@web.de> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Sender: linux-msdos-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Bart Oldeman Cc: linux-msdos@vger.kernel.org Hi again, I just found out myself how to emulate the CPU. I set $_cpu_emu to "vm= 86" in /etc/dosemu/dosemu.conf on my T22, and so far no more problems! = Seems to be a bug that only occurs when running on the real CPU. Thomas W. > -----Urspr=FCngliche Nachricht----- > Von: > Gesendet: 17.07.09 11:57:08 > An: Bart Oldeman > CC: linux-msdos@vger.kernel.org > Betreff: Re: MIDI input patch > Hi all, >=20 > it's great that MIDI is working now with the latest SVN version. Howe= ver, when trying to use it on my Thinkpad T22 (Pentium III, Xubuntu Jau= nty, 2.6.28-13-generic kernel), there is another problem, both in revis= ion 1897 and 1898. Two other people have reported this problem, too. I = don't experience this problem on my desktop machine (AMD Athlon 64 X2 3= 800+ machine, Ubuntu Hardy, 2.6.24-24-generic kernel). So this could ha= ve to do something with a real vs. an emulated CPU. I tried to force CP= U emulation on the T22 by starting dosemu with dosemu -I 'cpu emulated'= , but I'm not sure whether this works and if CPU emulation was at all i= ncluded at compile time. How can I tell whether I compiled dosemu with = CPU emulation or not? And how can I influence this? >=20 > I guess the problem might also be MIDI related, even if one doesn't u= se MIDI input because it occurs in input mode where Score expects music= input via qwerty or MIDI keyboard (you can mix both, enter some notes = via MIDI, some via qwerty). I removed the dosemu-midi_in links on both = my machines for the following test (both running with the MIDI patch). = When I start dosemu with "dosemu -O -D+S", the first debugging output a= fter starting Score is when I enter input mode. On my AMD 64 machine, i= t looks as follows: >=20 >=20 > MPU401: Read status port =3D 0xbf > MPU401: Read status port =3D 0xbf > MPU401: Write 0xff to command port > SB: Activating irq type 4 > MPU401: Read status port =3D 0x3f > MPU401: Read data port =3D 0xfe, 0 bytes still in queue > SB: Deactivating irq type 4 > MPU401: Read status port =3D 0xbf > MPU401: Write 0x3f to command port > SB: Activating irq type 4 > MPU401: Read status port =3D 0x3f > MPU401: Read data port =3D 0xfe, 0 bytes still in queue > SB: Deactivating irq type 4 >=20 >=20 > On the T22 it's the same except for one word: The last line says "SB:= Warning: Deactivating irq type 4". This raises my suspicion. Anyway, s= o far there is no problem. I can go on and enter music with the qwerty = keyboard. When I'm finished with that and Score does not expect any fur= ther input, the next messages pop up on the console. >=20 > On the AMD64: >=20 > MPU401: Read status port =3D 0xbf > MPU401: Read status port =3D 0xbf > MPU401: Write 0xff to command port > SB: Activating irq type 4 > MPU401: Read status port =3D 0x3f > MPU401: Read data port =3D 0xfe, 0 bytes still in queue > SB: Deactivating irq type 4 >=20 >=20 > On the T22, almost the same, except for the lines I marked with "=3D>= ": >=20 > MPU401: Read status port =3D 0xbf > MPU401: Read status port =3D 0xbf > MPU401: Write 0xff to command port > SB: Activating irq type 4 > =3D> SB: Interrupt activated > =3D> SB: Activated IRQ for MIDI > MPU401: Read status port =3D 0x3f > MPU401: Read data port =3D 0xfe, 0 bytes still in queue > =3D> >=20 > The last line from my AMD64, "SB: Deactivating irq type 4", is missin= g in the T22 output. >=20 > However, both machines continue to work happily, until I want to ente= r input mode again. This causes dosemu on the T22 to hang. On the AMD m= achine everything is fine and the fresh debugging output looks exactly = like when entering input mode the first time. >=20 > I can only guess what this all means. Does it mean, that the T22 miss= ed to deactivate IRQ type 4 when leaving input mode and therefore can't= read status port =3D 0xbf?? (I've no idea what's behind all this IRQ s= tuff.) >=20 > Can anyone help? >=20 > Thomas W. >=20 > ______________________________________________________ > GRATIS f=FCr alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://movieflat.web.de >=20 > -- > To unsubscribe from this list: send the line "unsubscribe linux-msdos= " in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >=20 ______________________________________________________ GRATIS f=FCr alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html