Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Krüger" <m_a_krueger@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Pavel Hofman <pavel.hofman@insite.cz>
Subject: Re: PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?)
Date: Mon, 26 May 2008 18:29:00 +0200	[thread overview]
Message-ID: <483AE54C.3090807@gmx.de> (raw)
In-Reply-To: <s5hbq2tunel.wl%tiwai@suse.de>

Takashi Iwai schrieb:
> At Mon, 26 May 2008 12:54:32 +0200,
> Martin Krüger wrote:
>   
>> Pavel Hofman wrote:
>>     
>>> Martin Krüger wrote:
>>>   
>>>       
>>>> Pavel Hofman wrote:
>>>>     
>>>> Hi, 
>>>>
>>>> thanks a lot for taking care for that issue. 
>>>> I just tried it out by modifying the following files from the 2.6.26-rc3 kernel:
>>>>
>>>> sound/pci/Kconfig (modified by hand)
>>>> sound/pci/ice1712/ice1712.h (modified by hand)
>>>> sound/pci/ice1712/envy24ht.h (modified by hand)
>>>> sound/pci/ice1712/ice1724.c (copied from the actual Git snapshot)
>>>>
>>>> I double-checked all the handmade changes, should be ok. 
>>>>
>>>> Midi in via "amidi -p hw:0 -d" works now without problem, 
>>>> but when trying to write to the device, for example by "amidi -p hw:0 -s txdata.syx" 
>>>> it causes an immediate crash. 
>>>>
>>>> That would not be a problem for me, but jackd probes all ports, and is unusable now.
>>>>
>>>> Perhaps i forgot a patch, is the output working for you? 
>>>>     
>>>>         
>>> Hello Martin,
>>>
>>> I did check the MIDI output using command
>>>
>>> amidi -p hw:0 -S F0411042110C000000000074FF0411042110C000000
>>>
>>> Ubuntu Studio 7.10, both -generic and -rt kernel, Audiotrak Prodigy 192, 
>>> the original patch (I assume the current git version is identical).
>>>
>>> There was no MIDI device connected to the output as I have none.
>>>
>>> I traced if MIDI-out on Juli goes through the Xilinx CPLD, and it seemed 
>>> the MIDI lines go straight to the connectors, just as on my Prodigy 192. 
>>> Unfortunately, I do not have Juli available any more to test the patch.
>>>
>>> Please could you provide more details about the crash?
>>>
>>> Thanks,
>>>
>>> Pavel.
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>   
>>>       
>> Hello Pavel,
>>
>> i just compiled a new 2.6.25.4 kernel with realtime support. the kernel 
>> is from kernel.org, so without any patches except the realtime patch 
>> from the alsa wiki.
>>     
>
> To be sure -- does 2.6.25.4 without realtime support work?
>
>
> Takashi
>   
No. Not with an unpatched kernel set to "Preemptible Kernel (Low-Latency 
Desktop) PREEMPT_DESKTOP". I didn't test the lower preemption modes.

Martin

  reply	other threads:[~2008-05-26 16:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080520112539.81C9D2484D@alsa0.perex.cz>
2008-05-23 10:26 ` [alsa-cvslog] alsa-kmirror: ALSA kernel mirror repository branch, master now at 9d46f4a919532c3f29a4ca1df3a4ce4686b11f37 Thierry Vignaud
2008-05-24 16:53   ` PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?) Martin Krüger
2008-05-26  7:57     ` Pavel Hofman
2008-05-26 10:54       ` Martin Krüger
2008-05-26 14:53         ` Takashi Iwai
2008-05-26 16:29           ` Martin Krüger [this message]
2008-05-28 11:58             ` Martin Krüger
2008-05-29  9:35               ` Pavel Hofman
2008-05-29 14:03                 ` "Martin Krüger"
2008-05-29 16:14                   ` Pavel Hofman
2008-06-07 21:36                     ` Pavel Hofman
2008-06-24 11:07                       ` Martin Krüger
2008-06-26 21:01                         ` Martin Krüger
2008-06-27 13:54                           ` Pavel Hofman
2008-06-27 14:24                             ` Takashi Iwai
2008-06-18  9:58   ` can we make the log appears in subject instead of useless sha1 ID? Thierry Vignaud
2008-06-19  9:54     ` Takashi Iwai

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=483AE54C.3090807@gmx.de \
    --to=m_a_krueger@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pavel.hofman@insite.cz \
    --cc=tiwai@suse.de \
    /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