From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Harish K Harshan <harish@arl.amrita.edu>
Cc: linux-arch@vger.kernel.org
Subject: Re: DMA Transfer Problem
Date: Tue, 24 Jan 2006 10:04:14 -0700 [thread overview]
Message-ID: <200601241004.14529.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <43D5B80F.3050705@arl.amrita.edu>
On Monday 23 January 2006 22:15, Harish K Harshan wrote:
> Im having problems with DMA transfer on Linux, for an ADC card. The
> card is AxiomTek AX5621H (ISA), 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.
You posted to the wrong list. linux-arch is for issue that affect
architecture maintainers specifically. linux-kernel@vger.kernel.org
is the list you want.
You also seem to be asking for help with a driver that's not in
the kernel tree, with ancient kernels that few developers use
anymore, and with only vague details about the actual problem,
so chances are slim that anybody will be interested or able to
help you. If you publish the driver as open-source and reproduce
the problem with a more recent kernel, you'll probably get more help.
prev parent reply other threads:[~2006-01-24 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 5:15 DMA Transfer Problem Harish K Harshan
2006-01-24 17:04 ` Bjorn Helgaas [this message]
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=200601241004.14529.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=harish@arl.amrita.edu \
--cc=linux-arch@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