From: "Martin Krüger" <m_a_krueger@gmx.de>
To: Pavel Hofman <pavel.hofman@insite.cz>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?)
Date: Tue, 24 Jun 2008 13:07:42 +0200 [thread overview]
Message-ID: <4860D57E.10509@gmx.de> (raw)
In-Reply-To: <484AFF77.3030901@insite.cz>
Pavel Hofman schrieb:
> Pavel Hofman wrote:
>
> Ubuntu Studio 7.10 with kernel upgraded to 2.6.25 according to
> http://74.125.39.104/search?q=cache:0fDGNG0KRbwJ:forum.zackyfiles.com/showthread.php%3Fp%3D3351188+gutsy+2.6.25+package&hl=en&ct=clnk&cd=1
>
>
> Latest download of alsa from git, compiled by ./gitcompile.
>
> Ancient Duron 1GHz, Audiotrak Prodigy 192
>
> Both MIDI input (amidi -p hw:0 -d) and output (amidi -p hw:0 -S
> F0411042110C000000000074FF0411042110C0000000000\
> 74F7F0411042110C000000000074F7F0411042110C0F0411\
> 042110C000000000074FF0411042110C000000000074F7F0\
> 411042110C000000000074F7F0411042110C0)
> work fine, no problems.
>
> Regards,
>
> Pavel.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
Hi Pavel,
sorry for the long break, i was really busy at studying.
The problem still exists for me, and i tried to debug it a bit by adding
printk's to the rawmidi module.
Unfortunatly, i am more confused at this problem than ever before.
I added printk("some text"); to the following subroutines:
- int snd_rawmidi_transmit
- snd_rawmidi_kernel_write1
- snd_rawmidi_kernel_write
As i read the source, these routines should be the ones who do all the
midi output to the device. And the printk's should appear in the
kern.log files.
Please tell me, if i am wrong here.
But none of the printk outputs appear in the logging. I added some
outputs similar to the other ones to the Midi Input procedures, and
everything works fine.
Does amidi write directly to the routines above? Or is there some Stuff
between? I tried to read the amidi source, but my C/C++ knowledge is
very poor, i am more on the java side of code...
Perhaps you have an idea where to start the debugging, to find that bug...
Thanks a lot,
Martin
next prev parent reply other threads:[~2008-06-24 11:07 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
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 [this message]
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=4860D57E.10509@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.