From owner-freebsd-current@FreeBSD.ORG Thu Jun 3 11:42:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8335D16A4CE for ; Thu, 3 Jun 2004 11:42:35 -0700 (PDT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3851343D4C for ; Thu, 3 Jun 2004 11:42:35 -0700 (PDT) (envelope-from pdseniura@techie.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])26EE71800A83 for ; Thu, 3 Jun 2004 18:42:31 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 3 Jun 2004 18:42:01 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id EAABF79006C; Thu, 3 Jun 2004 18:42:30 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [192.149.244.9] by ws1-14.us4.outblaze.com with http for pdseniura@techie.com; Thu, 03 Jun 2004 12:42:30 -0600 From: "P.D. Seniura" To: "Brooks Davis" Date: Thu, 03 Jun 2004 12:42:30 -0600 X-Originating-Ip: 192.149.244.9 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20040603184230.EAABF79006C@ws1-14.us4.outblaze.com> cc: freebsd-current@freebsd.org Subject: Re: What happened to src/sys/dev/sound/midi ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 18:42:35 -0000 ----- Original Message ----- From: Brooks Davis Date: Thu, 3 Jun 2004 10:17:18 -0700 To: Paul Seniura Subject: Re: What happened to src/sys/dev/sound/midi ? > On Thu, Jun 03, 2004 at 12:03:29PM -0500, Paul Seniura wrote: > > > > Hi y'all, > > > > > > What happened to src/sys/dev/sound/midi/* ? > > > > There's nothing mentioned in /src/UPDATING . > > > > I cannot find a cvs commit entry for it by searching at > > . > > > > I see no "HEADS UP" in the maillists anywhere over the past > > two weeks concerning this. > > > > In my CTM logs, since we were on holiday early this week, I > > got caught up to the CTM buckets on June 1, and this is the > > CTM "file/dir remove" entries for that entire subdir: > > > > >>>> > > ./20040601/ctm_src_PM.log:139:> FR /src/sys/dev/sound/midi/midi.c > > ./20040601/ctm_src_PM.log:140:> FR /src/sys/dev/sound/midi/midi.h > > ./20040601/ctm_src_PM.log:141:> FR /src/sys/dev/sound/midi/midibuf.c > > ./20040601/ctm_src_PM.log:142:> FR /src/sys/dev/sound/midi/midibuf.h > > ./20040601/ctm_src_PM.log:143:> FR /src/sys/dev/sound/midi/midisynth.c > > ./20040601/ctm_src_PM.log:144:> FR /src/sys/dev/sound/midi/midisynth.h > > ./20040601/ctm_src_PM.log:145:> FR /src/sys/dev/sound/midi/miditypes.h > > ./20040601/ctm_src_PM.log:146:> FR /src/sys/dev/sound/midi/sequencer.c > > ./20040601/ctm_src_PM.log:147:> FR /src/sys/dev/sound/midi/sequencer.h > > ./20040601/ctm_src_PM.log:148:> FR /src/sys/dev/sound/midi/timer.c > > ./20040601/ctm_src_PM.log:149:> FR /src/sys/dev/sound/midi/timer.h > > ./20040601/ctm_src_PM.log:150:> DR /src/sys/dev/sound/midi > > <<<< > > From the commit message (which you are supposed to have read since you > are running current :) Thank you for providing the quote from the commit, but I just have to ask: Did YOU read MY message above?? I said I COULD NOT FIND THE CVS COMMIT ON THIS after properly searching the maillist archives! CTM Deltas Do Not Show What/Why it was changed! And I showed what the CTM log shows verbatim. CTM != (CVS | CVSup) In fact I've been spotting _many_ commits that I cannot find in the recent archives. For one, the commit that moves the port print/teTeX to print/teTeX-base does not present itself in a search (using all sorts of keywords I can think-up). Yanking the rug out from under us like this needs to be documented better. Deleting support for devices. And not replacing it with something else ("yet"). Whatever's going on should've been documented. Properly. So everyone can know about it. And what to expect later on. > Axe the old midi drivers and framework. matk has developed a new > module-friendly midi subsystem to be merged soon. So where is the URL for this quote, please? I said twice now that I cannot find it. And I *still* cannot find it! (third time... ;) Showing me where you got this quote will sure help me explain to others why we can't use our musical devices and sequencing software in the meantime. And to the committer: Why get rid of these things when "module-friendly midi" is not ready yet? I was going to ask to undo the commit until it is ready but that'll depend on "what the meaning of 'soon' is". Don't get me wrong: MIDI is very dear to me. I was a member of the IMA even before the 1.0 spec came out. Spent a lot of my own money developing a prototype board for the Tandy CoCo3 (yes it was way back then) completely "per spec" with opto-isolators and such. Someone at Sierra Games released their code that parsed SMFs (Standard MIDI Files) and we used it on OS-9/6809 and OSK (OS-9/68K) after I wrote system-level drivers for the prototype hardware. Yes way back then. ;) But I'm not aware of any discussions of axing what we had here on BSD to replace it with something else. I'm not _that_ worried about it on the i386 platform since OSX (what I use at home on my G4 Sawtooth) already has it sewed up. But I am worried that FreeBSD/PPC will need it. MIDI needs to be as "real time" as it can possibly get. That's the crux of why CoreMIDI & CoreAudio were invented. It'd sure be worth it to see if these projects can be ported to BSD natively. Not even sure if Darwin/i386 includes it (can't test it on these dilapidated machines TPTB lets us use here). > -- Brooks Thank you for any help. Sorry for bellyachin but I *still* cannot find the source of these commits (and others)! -- Paul Seniura -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm