On Mon, Oct 22, 2018 at 11:00:41AM +0200, Hans Petter Selasky wrote:
> On 10/20/18 6:56 PM, Peter Holm wrote:
> > I can trigger this on 13.0-CURRENT r339445 with a non-root test program:
> >
>
> Hi,
>
> The following commits should fix the issues you experience:
>
> https://svnweb.freebsd.org/c
On 10/20/18 6:56 PM, Peter Holm wrote:
I can trigger this on 13.0-CURRENT r339445 with a non-root test program:
Hi,
The following commits should fix the issues you experience:
https://svnweb.freebsd.org/changeset/base/339581
https://svnweb.freebsd.org/changeset/base/339582
https://svnweb.fre
On 10/20/18 6:56 PM, Peter Holm wrote:
I can trigger this on 13.0-CURRENT r339445 with a non-root test program:
Calling uiomove() with the following non-sleepable locks held:
exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @
dev/sound/midi/sequencer.c:952
stack
On Sun, Oct 21, 2018 at 12:59 AM Peter Holm wrote:
> I can trigger this on 13.0-CURRENT r339445 with a non-root test program:
>
> Calling uiomove() with the following non-sleepable locks held:
> exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @
>
I can trigger this on 13.0-CURRENT r339445 with a non-root test program:
Calling uiomove() with the following non-sleepable locks held:
exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @
dev/sound/midi/sequencer.c:952
stack backtrace:
#0 0x80bfe263 at
On Sat, 15 Nov 2003 22:42:44 +0900,
Seigo Tanimura <[EMAIL PROTECTED]> said:
tanimura> Mathew Kanner has developed the new version of the midi framework,
tanimura> based on kobj(9) and buildable as a module. As the first step to
tanimura> replace the midi driver, the conv
Hello All,
I'm sorry to be a pain, but I think it's important this PR be
commited before any branch.
http://www.freebsd.org/cgi/query-pr.cgi?pr=59233
It's vital to build current midi software and it has been in
other OSes for a while.
Thanks,
On Sat, Nov 15, 2003 at 10:42:44PM +0900, Seigo Tanimura wrote:
> Mathew Kanner has developed the new version of the midi framework,
> based on kobj(9) and buildable as a module. As the first step to
> replace the midi driver, the conventional one is removed from the
> kernel
Mathew Kanner has developed the new version of the midi framework,
based on kobj(9) and buildable as a module. As the first step to
replace the midi driver, the conventional one is removed from the
kernel in a minute.
Mathew will soon be starting a work to merge his driver.
--
Seigo Tanimura
I create isa devices from a pci device. Do I search up the
> soundcard tree for the pci bus then search down for the isa bus, then
> create_child(..."mpushim")?
In pci device_attach:
isa=devclass_find("isa");
if( !isa ) {
device_printf(sc->
Hello,
I've been fiddling with pci drivers in freebsd for a couple of
months and up to now everything has ok, I did a midi driver for es137x
which was relatively easy because the io was done on the pci bus. I
was very pleased that there were enough resources for a newbie like me
to
this is what he's been working on:
>http://chibis.persons.gfk.ru/audigy/
No! I'm not a MIDI subsystem developer! The only thing I do is an attempt to add MIDI
I/O to Live/Audigy cards. If MIDI subsystem is not compllete I'll stop this work. I'm
going to do only card-specific
David Schultz wrote:
Thus spake Thanjee Neefam <[EMAIL PROTECTED]>:
I was very happy when compiling my 5.0 kernel. For the first time "device
midi" compiled without giving any errors. This abnormal excitement only
led to misery when I discovered after rebooting that there still
Thus spake Thanjee Neefam <[EMAIL PROTECTED]>:
> I was very happy when compiling my 5.0 kernel. For the first time "device
> midi" compiled without giving any errors. This abnormal excitement only
> led to misery when I discovered after rebooting that there still was no
&g
I'm interrested in using MIDI on FreeBSD, too, but I have to tell you,
that - as far as I found out - there has been midi support some time
ago, but it's not included in the system/kernel anymore.
There's probably some hope although, I don't find it, but I remember
someone
Hello,
I am not sure if this is most appropriate here, but there is no
sound-dev-current mailing list.
I was very happy when compiling my 5.0 kernel. For the first time "device
midi" compiled without giving any errors. This abnormal excitement only
led to misery when I discovered after
Am Mo, 2003-03-24 um 14.02 schrieb Yuriy Tsibizov:
> MIDI I/O should be almost the same between EMU10Kx cards... But I don't have any
> MIDI devices (other than AudigyDrive remote control, it should act as a MIDI
> controller on second MIDI port, AFAIK) to check it.
I have seve
> From: Julian St. [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 24, 2003 3:26 PM
> > > just out of curiosity: Is someone working in MIDI support for
> > > Creative EMU10K1
> > > based sound cards (aka Soundblaster Live!) ?
> > Nobody. Our target for n
Am Mo, 2003-03-24 um 07.47 schrieb Yuriy Tsibizov:
> > just out of curiosity: Is someone working in MIDI support for
> > Creative EMU10K1
> > based sound cards (aka Soundblaster Live!) ?
> Nobody. Our target for nearest future is Audigy/Audigy2 support.
>
> just out of curiosity: Is someone working in MIDI support for
> Creative EMU10K1
> based sound cards (aka Soundblaster Live!) ?
Nobody. Our target for nearest future is Audigy/Audigy2 support.
Yuriy Tsibizov,
http://chibis.persons.gfk.ru/audigy/
To Unsubscribe: send mail to [EMAIL
Hello,
no luck here either:
http://www.opensound.com/readme/README.SBLive.html
-> o EMU Wavetable MIDI synthesizer not yet supported
The only thing that is (partially) working seems to be ALSA.
Regards,
Julian
On 22-Mar-2003 Michael Nottebrock wrote:
> On Friday 21 March 2003 21:01,
On Mar 22, Michael Nottebrock wrote:
> On Friday 21 March 2003 21:01, [EMAIL PROTECTED] wrote:
> > just out of curiosity: Is someone working in MIDI support for Creative
> > EMU10K1 based sound cards (aka Soundblaster Live!) ?
> On and off, as far as I can tell. If you want MIDI
On Saturday 22 March 2003 16:15, Peter Schultz wrote:
> OSS is on the outs. New applications that are ALSA only will soon be
> common, won't they?
No. In fact, there is quite an explosion in multimedia middleware projects
right now and people are having heated discussions in other places which
Peter Schultz wrote:
Michael Nottebrock wrote:
On Saturday 22 March 2003 14:52, Peter Schultz wrote:
[EMAIL PROTECTED] wrote:
Hello,
just out of curiosity: Is someone working in MIDI support for Creative
EMU10K1 based sound cards (aka Soundblaster Live!) ?
Regards,
Julian Stecklina
Having a
Having a port of ALSA would sure round out 5.2 nicely, and would get you
MIDI support: http://www.alsa-project.org/
I think you wouldn't really do anyone a favour, including the ALSA
folks, if you went and made a port right now. The ALSA project is still
not at 1.00 status and still qui
Michael Nottebrock wrote:
On Saturday 22 March 2003 14:52, Peter Schultz wrote:
[EMAIL PROTECTED] wrote:
Hello,
just out of curiosity: Is someone working in MIDI support for Creative
EMU10K1 based sound cards (aka Soundblaster Live!) ?
Regards,
Julian Stecklina
Having a port of ALSA would sure
On Friday 21 March 2003 21:01, [EMAIL PROTECTED] wrote:
> Hello,
>
> just out of curiosity: Is someone working in MIDI support for Creative
> EMU10K1 based sound cards (aka Soundblaster Live!) ?
On and off, as far as I can tell. If you want MIDI right now, take a look at
what 4Front
On Saturday 22 March 2003 14:52, Peter Schultz wrote:
> [EMAIL PROTECTED] wrote:
> > Hello,
> >
> > just out of curiosity: Is someone working in MIDI support for Creative
> > EMU10K1 based sound cards (aka Soundblaster Live!) ?
> >
> > Regards,
> > Jul
Hello,
> Having a port of ALSA would sure round out 5.2 nicely, and would get you
> MIDI support: http://www.alsa-project.org/
Quote from this page:
"Known bugs
- MIDI on SB live drive not working properly."
Seems MIDI is not a great priority anymore. But I would certainly g
[EMAIL PROTECTED] wrote:
Hello,
just out of curiosity: Is someone working in MIDI support for Creative EMU10K1
based sound cards (aka Soundblaster Live!) ?
Regards,
Julian Stecklina
Having a port of ALSA would sure round out 5.2 nicely, and would get you
MIDI support: http://www.alsa-project.org
Hello,
just out of curiosity: Is someone working in MIDI support for Creative EMU10K1
based sound cards (aka Soundblaster Live!) ?
Regards,
Julian Stecklina
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hello everybody,
While the flamage rages on on cvs-all, I would like to report the second
driver that does not pass the recently introduced warning-to-panic test
because of driver mistake. It is the Midi driver (device midi and device seq)
I have an SB 64 AWE ISA PnP card so I had these devices
Hello Jim,
On Sun, Mar 25, 2001 at 07:20:04PM -0500, Jim Bloom wrote:
> I get a slightly different backtrace, but was able to use my palm pilot as the
> serial console. I have had this same problem for quit a while (about a month).
> I suspect a locking issue related to Seigo Tanimura's commit o
to make
> sure that I try today's sources first)
>
> device midi
> device seq
>
> (my sound card is a ISAPnP SB 64 AWE)
>
> I use device sbc too.
>
> the kernel still panics with Fatal Trap 12. I have Seigo Tanimura's
> fixes, and yet this still
Hello folks,
I have tried it with today's -CURRENT, and as soon as I try to boot a
kernel with the options (this has occured also earlier but wanted to make
sure that I try today's sources first)
device midi
device seq
(my sound card is a ISAPnP SB 64 AWE)
I use device sbc too.
On Wed, 14 Mar 2001 00:49:53 -0800,
Alex Zepeda <[EMAIL PROTECTED]> said:
Alex> On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote:
>> I wonder if this is known? If not, I can certainly provide more
>> information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It
>>
On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote:
> I wonder if this is known? If not, I can certainly provide more
> information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It
> works fine otherwise. (as it always has)
Yup I'm seeing this too. SMP kernel, AWE64
Hello everybody,
I had been away for two weeks and after upgrading to the latest -CURRENT I
noticed that leaving
device midi
(and maybe device seq, I did not test separately)
in my kernel config file causes a Trap 12 with interrupts disabled on
_mtx_lock_sleep+0x29a: movl 0x1a0(%edx),%eax
On Tue, 27 Feb 2001 22:53:06 +0900,
"Daniel C. Sobral" <[EMAIL PROTECTED]> said:
Daniel> I'm getting fatal trap 12 with interrupts disabled related to the midi
Daniel> code during boot.
Daniel> Backtrace is:
Daniel> _mtx_lock_sleep+0x23a
Daniel> mpu_u
I'm getting fatal trap 12 with interrupts disabled related to the midi
code during boot.
Backtrace is:
_mtx_lock_sleep+0x23a
mpu_uartmode+0x3e
mpu_attach+0x25
mpusbc_attach+0x19
device_probe_and_attach+0x9a
bus_generic_attach+0x16
sbc_attach+0x3ad
device_probe_and_attach+0x9a
isa_probe_chi
The patch at
http://people.FreeBSD.org/~tanimura/patches/midimutex.diff.gz
makes midi(4) MP-safe. With this patch, my kernel with WITNESS and
INVARIANTS plays my favorite midi tunes just fine, except that the
callout used by the midi sequencer gets delayed under a heavy load. As
the sequencer
Hi,
I'm tracking -CURRENT and build a kernel yesterday with the following
options (edited):
device sbc # Soundblaster Bridge-Code to pcm
device pcm # PnP/PCI Sound Cards
#device midi # Midi interfaces
#device
Does anyone know when PCM will support midi?
Thanks!
Bob
--
"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
After a long absense, newmidi now supports CS461x/428x PCI Audio
and GUS midi, with some bug fix. Both pcm and midi on an ISA PnP/
PCI card now work(for SB/GUS/CS461x). Microtimeout and APIC timer
patches are separated from newmidi.
Please follow the document at:
http://www.freebsd.org
>this is problematic.
>
>you cannot add a new element before the pending firing because you can't
>tell how far into the present trigger you are.
This is not a problem for readable counters like the i8254. The problem
for the i8254 is that reading and writing it takes a long time (perhaps
5 usec
Somebody should study the abilities of the on-cpu APIC for this
for pentium ff. machines.
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>>dfr> If I understand this correctly, you are suggesting that we program timer0
>>dfr> so that we only take interrupts when a finetimer is due to fire?
>dfr> If I understand this correctly, you are suggesting that we program timer0
>dfr> so that we only take interrupts when a finetimer is due to fire? If so,
>dfr> then it sounds very good. The idea of taking 6000+ interrupts/sec made me
>dfr> uneasy, even though most would return without doing an
1024hz) so the
dfr> granularity of timing is better but probably not good enough for midi or
dfr> pca.
I agree.
Seigo Tanimura <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
>
> Ow, I thought it was in the mailing list archive, turned out not.
> I will attach the paper below. Sorry for a long mail.
>
>
> --- v --- cut here --- v ---
> Unlike 16550, MPU401 does not generate an interrupt on TX-ready.
> So we have to choose
On Wed, 7 Jul 1999 19:18:57 -0700 (PDT),
Julian Elischer <[EMAIL PROTECTED]> said:
>> Sorry, finetimer(9) is the new timer implemented in my latest midi driver.
>> You can read the short paper describing the feature and principle in:
>>
>> Message-Id: <[EM
al
>
>
> Sorry, finetimer(9) is the new timer implemented in my latest midi driver.
> You can read the short paper describing the feature and principle in:
>
> Message-Id: <[EMAIL PROTECTED]>
how do I read that?
>
> finetimer(9) has the same interface functions
On Wed, 7 Jul 1999 19:06:48 -0700 (PDT),
Julian Elischer <[EMAIL PROTECTED]> said:
julian> uh...
julian> [phaser.whistle.com] 536 man 9 finetimer
julian> No entry for finetimer in section 9 of the manual
Sorry, finetimer(9) is the new timer implemented in my latest midi drive
uh...
[phaser.whistle.com] 536 man 9 finetimer
No entry for finetimer in section 9 of the manual
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
> Another idea has come to my mind...
>
>
> pca(4) currently uses acquire_timer0(), which changes the timer
> frequency directly, breaking finetimer(9)
p...@originative.co.uk wrote in message ID
:
> The Acorn used a 6502. They went on to produce a box in the UK called the
> BBC Computer. It was *way* ahead of it's time, I still have it in the
> garage. Graphics resolutions that were better than the IBM PC that came
> later, 3 channel sound capabil
: Re: Call for Review: Voxware midi driver for serial ports
>
>
> From: Juergen Lock
> Subject: Re: Call for Review: Voxware midi driver for serial ports
> Date: Sun, 2 May 1999 02:15:00 +0200
> Message-ID: <19990502021500.a3...@saturn.kn-bremen.de>
>
> nox> On Tue,
From: Juergen Lock
Subject: Re: Call for Review: Voxware midi driver for serial ports
Date: Sun, 2 May 1999 02:15:00 +0200
Message-ID: <19990502021500.a3...@saturn.kn-bremen.de>
nox> On Tue, Apr 20, 1999 at 10:27:35AM +0900, Seigo TANIMURA wrote:
nox> > On Sun, 18 Apr 1999 22:1
56 matches
Mail list logo
