MIDI sup­port in ‑cur­rent

I just com­mit­ted the old-new midi code ftom tan­imu­ra and matk.Yuriy Tsi­bi­zov (of emu10kx fame) inte­grat­ed it into cur­rent. I think it wil need a lot of work until it’s real­ly mature, but as long as it isn’t in the tree, near­ly nobody will have a look at it.

We need a main­tain­er for this!

I will try to fix pan­ics and LOR’s, but I will not extend dri­vers to use it. The emu10k1 and the cmi dri­vers already have sup­port. The emu10kx dri­ver will also make use of it when it enters the tree.

Send to Kin­dle

SoC2006->my_students->start()

Since Roman want­ed to cre­ate his lin­ux­o­la­tor branch in per­force, I had to make myself famil­iar with per­force too, to be able to answer his ques­tions. I learned my first steps in per­force by cre­at­ing the sound branch (I’m men­tor­ing Ryan togeth­er with Ariff). Cre­at­ing the branch was not hard, but I man­aged to fail in some way… I used the wrong user­name part for Ryan’s branch name (“rbeasley” instead of “ryanb”). I think this means I should­n’t trust my mem­o­ry and double-check such facts in the future. Since it’s only a name­space issue to not have con­flicts when sev­er­al peo­ple want to cre­ate branch­es with the same name (but a dif­fer­ent seman­tic of what has to be done there), I don’t think it mat­ters.

Roman had­n’t as much “luck” than I had. He for­got to add a ‘/’ in an impor­tant place which result­ed in files like “…_linuxolatoramd64/…” instead of “…_linuxolator/amd64/…” while branch­ing. While ICQ is nice to dis­cuss some­thing in real-time over large dis­tances, you can’t look over the shoul­der of some­one. Mea cul­pa (stu­dents which are excit­ed and eager to try some­thing… I think I remem­ber how this feels 😉 ). He is resolv­ing this as I write this.

While I see some ben­e­fits in the way per­force is work­ing (seems to allow some pow­er­ful things we can’t do with CVS), I have to say the per­for­mance sucks when cre­at­ing branch­es (I did it at home via DSL and a com­pressed ssh tun­nel to the per­force serv­er, not on freefall where it should have been much faster). But I did­n’t cre­at­ed a FreeB­SD branch with CVS, so maybe CVS sucks more when doing this. 🙂

Send to Kin­dle

The ker­nel sub­sys­tem API doc­u­men­ta­tion gen­er­a­tion frame­work.

I com­mit­ted the ker­nel sub­sys­tem API doc­u­men­ta­tion gen­er­a­tion frame­work. It allows to gen­er­ate the API doc­u­men­ta­tion of a sub­sys­tem (with doxy­gen) just by adding a short con­fig file (around 22 lines with com­ments and blank lines, maybe 14 lines with­out com­ments and blank lines). Here’s an exam­ple of such a con­fig:

—snip—
PROJECT_NAME = “FreeB­SD ker­nel sound device code”
OUTPUT_DIRECTORY = $(DOXYGEN_DEST_PATH)/dev_sound/
EXTRACT_ALL = YES # for undoc­u­ment­ed src, no warn­ings enabled
INPUT = $(DOXYGEN_SRC_PATH)/dev/sound/

GENERATE_TAGFILE = dev_sound/dev_sound.tag
TAGFILES = dev_pci/dev_pci.tag=../../dev_pci/html \
dev_usb/dev_usb.tag=../../dev_usb/html
@INCLUDE_PATH = $(DOXYGEN_INCLUDE_PATH)
@INCLUDE = common-Doxyfile
—snip—

The frame­work is con­fig­ured to not only gen­er­ate the HTML ver­sion, but also a PDF ver­sion.

Sub­sys­tems for which docs are gen­er­at­ed cur­rent­ly (con­figs for oth­er sub­sys­tems are wel­come):

Peo­ple which want to help doc­u­ment­ing the code may want to have a look at the spe­cial com­mands doxy­gen under­stands.

Send to Kin­dle

Inter­est­ing Sum­mer for FreeB­SD

Now that we have (or “soon will have”) an offi­cial FreeB­SD blog, I decid­ed to give this kind of elec­tron­ic and pub­lic diary a try. At least to report the sta­tus and progress of some FreeB­SD relat­ed projects I’m involved in.

A lot hap­pened in the last days. We’re past the dead­line of the Google Sum­mer of Code rat­ing process and now the lucky stu­dents are cho­sen. It was­n’t easy. We had more than 120 pro­pos­als (out of ~6400). From those we where will­ing to men­tor 40 – 50 (based upon our resources and the qual­i­ty of the pro­pos­als). Google grant­ed 14 to us (a big thank you to Google!). I expect an offi­cial announce­ment “soon”. Hope­ful­ly some of those stu­dents Google was­n’t able to fund are will­ing to work with us regard­less of the mon­ey, there are a lot of very nice pro­pos­als (I will add some items to the ideas list based upon them lat­er). We’re at least will­ing to pro­vide the same amount of men­tor­ship as if they where select­ed.

I will work with two stu­dents. One of them will work on sync­ing the OSS API from recent releas­es from 4Front with our sound sys­tem. The oth­er one will work on improv­ing the lin­ux­o­la­tor. I will announce this on the cor­re­spond­ing mail­inglists after the offi­cial announce­ment. ATM we need to do some admin­is­tra­tive stuff (hand­ing out access to the wiki and per­force, set­ting up email alias­es, …).

I already mailed some gen­er­al guides to the stu­dents (note to men­tors: it’s in the wiki on the “hid­den” and restrict­ed to men­tors SoC page). For the sound stuff I don’t have a nice TODO list, but luck­i­ly the stu­dent already inves­ti­gat­ed the 4Front stuff for the pro­pos­al and is eager to start the work (basi­cal­ly this gives us the user­land inter­face for multi-channel mix­er sup­port). Regard­ing the lin­ux­o­la­tor improve­ments the stu­dent has a lit­tle bit less luck. I com­piled a nice TODO list which is based upon his own pro­pos­al and all the var­i­ous things I know about the lin­ux­o­la­tor (PR’s, mes­sages on emulation@, pri­vate con­ver­sa­tions, things we noticed while work­ing on the update of the lin­ux base to a recent Fedo­ra Core, …). I will be impressed if he man­ages to do every­thing on the TODO list (don’t wor­ry, he knows that not every­thing has to be done to declare “suc­cess” to Google).

Both of them may be can­di­dates for a com­mit bit (not with­in the SoC, but maybe lat­er), both are eager to do the work, inter­est­ed, moti­vat­ed, and don’t need hand-holding.

Fur­ther news in the area of the sound sys­tem: Ariff told me he is work­ing on multi-channel and endi­aness issues/support, and I may be able to com­mit two more sound dri­vers to the tree. One dri­ver is the emu10kx dri­ver cur­rent­ly avail­able in the Ports Col­lec­tion, and the oth­er one is a dri­ver for some envy24 chips. Cur­rent­ly I’m in con­tact with the author of the emu10kx dri­ver and a vol­un­teer who wants to improve an exist­ing envy24 dri­ver (author of the dri­ver con­tact­ed; since it’s BSD licensed, this is a “don’t be evil” action).

And some news regard­ing the user­land part of the lin­ux­o­la­tor: We’re wait­ing for a repo-copy form linux_base-fc3 to linux_base-fc4. It seems FC4 is com­pat­i­ble enough so that we can dire­clty move from Red­Hat 8 to FC 4. FC 5 is out of the game for a while, it does­n’t want to run with the old lin­ux ker­nel ver­sion our lin­ux­o­la­tor announces. Chang­ing the ver­sion via the sysctl does­n’t help (prob­a­bly because of the changed seman­tic of the lin­ux clone syscall between 2.4.x and 2.6.x), so it has to wait until the lin­ux­o­la­tor SoC fin­ish­es.

Send to Kin­dle