From: "Jens Ch. Restemeier" <jenschrr@post.uni-bielefeld.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: via-cuda crashing ?
Date: Sun, 27 Dec 1998 23:18:22 +0100 [thread overview]
Message-ID: <3686B22B.69BA@post.uni-bielefeld.de> (raw)
Hi !
Nobody had any documentation on via-cuda, so I started some experiments
by myself. After a lot of reboots I found that after sending an
incomplete I2C request
- via cuda polling doesn't return
- if I use a timeout and send the next command anyway I get a
kernel-panic.
Is there any way to tell cuda: "Whatever you do, stop it and return to
normal operation" ?
I need this to implement I2C bus scanning.
Jens
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1998-12-27 22:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3686B22B.69BA@post.uni-bielefeld.de \
--to=jenschrr@post.uni-bielefeld.de \
--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).