>How does this work then? Can a file be opened from kernel space? Or
sys_{open,read,write,ioctl,close} can be called from kernel space.
--p
___
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. Y
> > This is nice. What documentation did you use for writing the driver?
>
> http://www.math.tu-berlin.de/~sbartels/unitor/unitor8_doc.txt
>
> It's in German. I have a translation of it I made using some online
> translation thingy a while ago, but I still find the German version a bit
> more re
On Wed, 1 May 2002, Paul Davis wrote:
> >This looks nice. Do rawmidi ports created this way appear as sequencer
> >clients as well?
>
> it depends. there is a module that looks at all current rawmidi ports
> and makes them available as sequencer clients. just creating a rawmidi
> device doesn't d
>This looks nice. Do rawmidi ports created this way appear as sequencer
>clients as well?
it depends. there is a module that looks at all current rawmidi ports
and makes them available as sequencer clients. just creating a rawmidi
device doesn't do this by itself.
i wanted to add, for clarificat
On Wed, 1 May 2002, Paul Davis wrote:
> >A solution could be alter libasound to support non-kernel drivers. Or use
> >a loopback device in the kernel.
>
> libasound *does* support non-kernel drivers. when you access
>
> snd_{pcm,rawmidi}_foo (handle, ...)
>
> what you're actually doing is
> > I have that document also. Emagic would not give me any AMT
> > documentation, that's why I aksed.
>
> Did they actually say 'no', or just didn't answer?
They did asnwer:
> Hi there,
> as AMT is our own standard and permanently improved, there is no
> possibility of public access of the te
>A solution could be alter libasound to support non-kernel drivers. Or use
>a loopback device in the kernel.
libasound *does* support non-kernel drivers. when you access
snd_{pcm,rawmidi}_foo (handle, ...)
what you're actually doing is:
1) check the device type of handle
2
On Wed, 1 May 2002, Martijn Sipkema wrote:
> > > This is nice. What documentation did you use for writing the driver?
> >
> > http://www.math.tu-berlin.de/~sbartels/unitor/unitor8_doc.txt
> >
> > It's in German. I have a translation of it I made using some online
> > translation thingy a while ag
On Wed, 1 May 2002, Martijn Sipkema wrote:
> > The following patch:
> >
> > http://fett.net/m/alsa/alsa-0.9.0rc1-unitor8.patch
> >
> > implements a driver for the Emagic Unitor family of multiport MIDI
> > interfaces. Only serial connection is supported. You need to rerun the
> > autoconf toolcha
> The following patch:
>
> http://fett.net/m/alsa/alsa-0.9.0rc1-unitor8.patch
>
> implements a driver for the Emagic Unitor family of multiport MIDI
> interfaces. Only serial connection is supported. You need to rerun the
> autoconf toolchain after applying the patch.
>
> The driver is heavily bas
The following patch:
http://fett.net/m/alsa/alsa-0.9.0rc1-unitor8.patch
implements a driver for the Emagic Unitor family of multiport MIDI
interfaces. Only serial connection is supported. You need to rerun the
autoconf toolchain after applying the patch.
The driver is heavily based o
11 matches
Mail list logo
