From: valvoline <valvoline@vrlteam.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: DMA timing issues with promise controllers
Date: Wed, 14 Jan 2004 09:53:00 +0100 [thread overview]
Message-ID: <20040114085300.GL2658@adapter.n0skillz.org> (raw)
In-Reply-To: <20040112065447.GD7303@heliosphan.in.cryptobackpack.org>
On Sun, Jan 11, 2004 at 10:54:47PM -0800, mutex wrote:
> I'm willing to do some of the debugging myself, just not sure where to
> start.
> clues anyone ?
i'm not an ide guru, but your problem sounds like there's some troubles
in the timers handling/sync
regards
--
[ valvoline :: VRL Team :: s0ftpj :: freaknet Medialab :: GPG key available ]
[ key fingerprint :: - :: B7E2 48BC 705F AE8F 9ABE E422 076A 2561 1D67 B4DD ]
[ GPG key available on keyserver :: pgp.mit.edu :: with keyID :: 1D67B4DD :: ]
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-14 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 6:54 DMA timing issues with promise controllers mutex
2004-01-14 8:53 ` valvoline [this message]
2004-01-19 22:21 ` mutex
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 15:14 ghannon
2004-01-12 20:09 ` mutex
2004-01-12 20:57 ghannon
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=20040114085300.GL2658@adapter.n0skillz.org \
--to=valvoline@vrlteam.org \
--cc=linuxppc-dev@lists.linuxppc.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).