From: Pavel Hofman <pavel.hofman@insite.cz>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Cc: Sergio Atzori <sergioatzori@gmail.com>
Subject: Re: Some questions about devices supported by alsa
Date: Mon, 11 Feb 2008 11:13:53 +0100 [thread overview]
Message-ID: <47B01FE1.1050504@insite.cz> (raw)
In-Reply-To: <47ADFFF2.4050803@gmail.com>
Hi Sergio,
Esi Juli@ seems to be a different beast than most other ice1724-based
cards. I am working on the driver, it will take a number of changes to
the generic ice1724 driver due to presumably different clocking scheme.
The ice1724 midi driver has a bug causing kernel hang when opening the
device. It has been reported, and Takashi has provided an experimental
patch.
http://mailman.alsa-project.org/pipermail/alsa-devel/2007-April/000641.html
It would be great if you were able to test the patch. The midi device
should work (hopefully) using the existing driver for Juli@.
Thanks a lot,
Pavel.
Sergio Atzori wrote:
> Hello, my name is Sergio Atzori. I'm a musician and I love very much
> linux and open source. I have a lot of hardware for music, something
> well supported by linux, something else not supported...I have some
> questions:
> 1) Esi Juli@: reported as supported by alsa, but it isn't. Looking at
> http://www.linuxdriverproject.org/twiki/bin/view/Main/DriversNeeded and
> http://alsa.opensrc.org/index.php/Ice1724, this really beautiful card is
> unusable in linux. I have one and I tried to get it working with some
> distros, but nothing..I experience a computer freeze (kernel panic
> perhaps?) in every attempt to configure it with alsa-conf, or just
> opening an application that uses midi system (like Rosegarden). So I
> would know, there is someone working on a better driver? Can I hope to
> get it working in the near future? According to me there is a lot of
> people waiting for a driver for this card, I'm waiting since 2005..
> 2) Miditech I2 control-37 (http://www.miditech.de/produktee_i2.htm):
> beatiful usb-keyboard, not mentioned in Linux-USB device site, it does
> not work in linux...I think the kernel configure it well (as
> snd-usb-audio device) but I can't see it in Jack midi connections..
> 3) RME AES32 (and AES32express) & Lynx AES16: this driver could be
> important for professional studios..if we want to put linux distros on
> the professional side. I've none of them, but some people ask me to
> build a professional multichannel live machine, I'd like to build a
> linux based machine...there are not alternatives to these cards, because
> I can build a system with more than one of them (really powerful
> multichannel environment).
>
> Thanks so much for attention.
> Ciao
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-02-11 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 19:33 Some questions about devices supported by alsa Sergio Atzori
2008-02-10 10:21 ` John Rigg
2008-02-11 10:13 ` Pavel Hofman [this message]
2008-02-11 10:45 ` Clemens Ladisch
2008-02-11 10:49 ` Pavel Hofman
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=47B01FE1.1050504@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=sergioatzori@gmail.com \
/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