From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Thomas Koch <tom-koch-Mmb7MZpHnFY@public.gmane.org>
Cc: Till Harbaum <till-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>,
Martin Michlmayr <tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
513894-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: Re: Bug#513894: Oops: f3 with i2c-tiny-usbHello,
Date: Tue, 17 Feb 2009 11:24:15 +0100 [thread overview]
Message-ID: <20090217112415.6cbb6fc2@hyperion.delvare> (raw)
In-Reply-To: <200902170435.53010.tom-koch-Mmb7MZpHnFY@public.gmane.org>
On Tue, 17 Feb 2009 04:35:52 +0100, Thomas Koch wrote:
> What I also noticed is when I do an i2cdetect the bus type of the interface is
> shown as dummy. Normaly the type is i2c.
"i2cdetect -l" queries the bus functionality to find out whether it can
do raw I2C or only SMBus. If it returns "dummy" this means that the
functionality request itself failed (which would probably be confirmed
by "i2cdetect -F"), which isn't necessarily surprising if the
i2c-tiny-usb driver is crashed.
--
Jean Delvare
prev parent reply other threads:[~2009-02-17 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 18:10 Bug#513894: Oops: f3 with i2c-tiny-usb Martin Michlmayr
[not found] ` <20090209181043.GB19801-u+sgIaa8TU6A7rR/f+Zz5kHK5LHFu9C3@public.gmane.org>
2009-02-09 19:29 ` Till Harbaum
[not found] ` <200902092029.05036.till-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>
2009-02-17 3:35 ` Bug#513894: Oops: f3 with i2c-tiny-usbHello, Thomas Koch
[not found] ` <200902170435.53010.tom-koch-Mmb7MZpHnFY@public.gmane.org>
2009-02-17 10:24 ` Jean Delvare [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=20090217112415.6cbb6fc2@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=513894-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org \
--cc=till-RcHadlBFbzVAfugRpC6u6w@public.gmane.org \
--cc=tom-koch-Mmb7MZpHnFY@public.gmane.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