From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Norman Schleicher <NormanSchleicher@gmx.de>, alsa-devel@alsa-project.org
Subject: Re: Steinberg Midex 8 driver development
Date: Wed, 16 May 2007 09:17:24 +0200 [thread overview]
Message-ID: <1179299844.4902.1190076781@webmail.messagingengine.com> (raw)
In-Reply-To: <20070515093557.311300@gmx.net>
Norman Schleicher wrote:
> I am currently on development for the Steinberg Midex8 USB driver.
>
> At the moment I can send notes to my Midi equipment via this device.
> Receiving is currently not implemented.
>
> My questions are:
> 1. Are there any tools to test the Alsa-Midi compatiblity ?
You can send raw MIDI data with amidi, or play entire .mid files with
aplaymidi.
To see received data, use amidi or aseqdump.
> 2. May I release some milestone results to the Alsa project ?
Just publish them somewhere.
> 3. What are the requirements to get released in an official alsa release
> package ?
Post the patches against the latest Hg tree here.
> 4. Where can I read how the source code is organized in the repository
The alsa-kernel tree contains an almost exact copy of the sound/
directory in the Linux kernel tree.
The alsa-driver tree contains the build mechanism for the separate
alsa-driver package, patches and compatibility code to make the code
in alsa-kernel work with older kernels, and some drivers that are too
new or too horrible to allow them into the kernel.
> and how to manage tags and branches for the development ?
https://bugtrack.alsa-project.org/wiki/wikka.php?wakka=SourceCodeRepository
and see the Hg docs.
HTH
Clemens
prev parent reply other threads:[~2007-05-16 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 9:35 Steinberg Midex 8 driver development Norman Schleicher
2007-05-16 7:17 ` Clemens Ladisch [this message]
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=1179299844.4902.1190076781@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=NormanSchleicher@gmx.de \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).