From: James Courtier-Dutton <James@superbug.co.uk>
To: Harish K Harshan <harish@arl.amrita.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA Transfer problem
Date: Tue, 24 Jan 2006 12:59:32 +0000 [thread overview]
Message-ID: <43D624B4.5070300@superbug.co.uk> (raw)
In-Reply-To: <43D5B473.3060006@arl.amrita.edu>
Harish K Harshan wrote:
> Hello,
>
> Im having problems with DMA transfer on Linux, for an ADC card. The
> card is AxiomTek AX5621H, and can use DMA channels 1 and 3. I tried
> both the channels, but the DMA transfers are irregular (i.e.) at
> different speeds (which of course is not acceptable, since that
> application is time critical). The device driver (which I wrote) seems
> to work fine for all the other systems I tried it on. But this problem
> occurs only on one particular model of computer (Chino-Laxsons
> Pentium-4 boards). I tried another system with the same configuration,
> but the same resulted. After some time of execution, I get the kernel
> panic screen, which says the CPU context is corrupt. Please help me
> with this problem, as I need to get this driver working somehow on the
> P4 systems. I tried the Redhat-9 kernel (2.4.20-8) and the debian
> kernel too (2.2.20).... gave the same results.
>
Could an ADC card be treated as a ALSA sound card PCM device.
That card seems to have features very similar to a sound card.
Sample rate.
Variable gain.
Multi-channels.
ADC
DMA
I only suggest this, because it could result in a driver that is much
easier to implement as ALSA supplies a lot of generalised support code
at the kernel level.
James
next prev parent reply other threads:[~2006-01-24 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 5:00 DMA Transfer problem Harish K Harshan
2006-01-24 12:59 ` James Courtier-Dutton [this message]
2006-01-24 13:20 ` Harish K Harshan
2006-01-24 13:22 ` James Courtier-Dutton
2006-01-30 16:37 ` Martin Drab
2006-01-30 17:06 ` linux-os (Dick Johnson)
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=43D624B4.5070300@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=harish@arl.amrita.edu \
--cc=linux-kernel@vger.kernel.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).