* FW: HELP ME! DM355 EVM MT9T001 question! [not found] ` <bfd52c5b0808280642o5d30b0f1g77240bd5e0165b16-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2008-09-01 17:35 ` xiaowinky [not found] ` <BLU111-W4910427AB2C320E39BF04CB75C0-MsuGFMq8XAE@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: xiaowinky @ 2008-09-01 17:35 UTC (permalink / raw) To: i2c-GZX6beZjE8VD60Wz+7aTrA [-- Attachment #1.1: Type: text/plain, Size: 1227 bytes --] hi,all! I use the i2c-tools-3.0.1 tool to compile and install in DM355 EVM kernel, For example with orders #i2cdetect 0, prompts following information: WARNING! This program can confuse your I2C bus, cause data loss and worse!I will probe file /dev/i2c/0.I will probe address range 0x03-0x77.Continue? [Y/n]Then the basis bus address range 0x03-0x07,orders the test with below: #i2cdump 0 0x03-0x77, only 0x5D and 0x1B two bus addresses are effective, For example # i2cdump 0 0x5dprompt the information to be as follows:No size specified (using byte-data access)Error: Could not set address to 0x5d: Device or resource busy Other bus address is invalid, For example : # i2cdump 0 0x3aprompts the information to be as follows: No size specified (using byte-data access) WARNING! This program can con fuse your I2C bus, cause data loss and worse!I will probe file /dev/i2c/0, address 0x3a, mode byteContinue? [Y/n] Whether only 0x5D and the 0xB1 two device address hang on the I2C bus ??? First time with this tool software, everybody help explained in detail! thanks everybody! winkyxiao! _________________________________________________________________ MSN 中文网,最新时尚生活资讯,白领聚集门户。 http://cn.msn.com [-- Attachment #1.2: Type: text/html, Size: 1597 bytes --] [-- Attachment #2: Type: text/plain, Size: 157 bytes --] _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <BLU111-W4910427AB2C320E39BF04CB75C0-MsuGFMq8XAE@public.gmane.org>]
* Re: FW: HELP ME! DM355 EVM MT9T001 question! [not found] ` <BLU111-W4910427AB2C320E39BF04CB75C0-MsuGFMq8XAE@public.gmane.org> @ 2008-09-02 7:15 ` Jean Delvare [not found] ` <BLU111-W23C107BF557C2DEB8093CFB75F0@phx.gbl> [not found] ` <20080902091532.0f4319ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 0 siblings, 2 replies; 4+ messages in thread From: Jean Delvare @ 2008-09-02 7:15 UTC (permalink / raw) To: xiaowinky; +Cc: i2c-GZX6beZjE8VD60Wz+7aTrA On Tue, 2 Sep 2008 01:35:00 +0800, xiaowinky wrote: > hi,all! > I use the i2c-tools-3.0.1 tool to compile and install in DM355 EVM kernel, Which kernel version are you using? > For example with orders #i2cdetect 0, > prompts following information: > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/0. > I will probe address range 0x03-0x77. > Continue? [Y/n] What is the output of this command? > Then the basis bus address range 0x03-0x07,orders the test with below: > #i2cdump 0 0x03-0x77, > only 0x5D and 0x1B two bus addresses are effective, For example # i2cdump 0 0x5d > prompt the information to be as follows: > No size specified (using byte-data access) > Error: Could not set address to 0x5d: Device or resource busy This means that there's already a kernel driver bound to this device. To find out which it is, you can follow the driver link in /sys/bus/i2c/devices/0-005d. To solve this, you can either unload the driver in question (with rmmod), or you can pass option "-f" to i2cdump to force i2c-dev to access the device even though it is busy. But beware that this might confuse the kernel driver that is bound to the device, so this is generally discouraged. > > Other bus address is invalid, For example : # i2cdump 0 0x3a > prompts the information to be as follows: > No size specified (using byte-data access) > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/0, address 0x3a, mode byte > Continue? [Y/n] > > Whether only 0x5D and the 0xB1 two device address hang on the I2C bus ??? I don't understand this question, sorry. Please rephrase in proper English. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <BLU111-W23C107BF557C2DEB8093CFB75F0@phx.gbl>]
[parent not found: <BLU111-W23C107BF557C2DEB8093CFB75F0-MsuGFMq8XAE@public.gmane.org>]
* Re: DM355 EVM MT9T001 question! [not found] ` <BLU111-W23C107BF557C2DEB8093CFB75F0-MsuGFMq8XAE@public.gmane.org> @ 2008-09-02 8:07 ` Jean Delvare 0 siblings, 0 replies; 4+ messages in thread From: Jean Delvare @ 2008-09-02 8:07 UTC (permalink / raw) To: xiaowinky, Linux I2C Please keep the i2c list Cc'd. On Tue, 2 Sep 2008 15:44:27 +0800, xiaowinky wrote: > hi,Jean! > my kernel version is 2.6.10_mvl401! Huh, this is very old... > I use "#i2cdetect 0"command to probe the I2C address range, > I get a long list (shown below) There's nothing shown below. Try again. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <20080902091532.0f4319ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>]
* Re: FW: HELP ME! DM355 EVM MT9T001 question! [not found] ` <20080902091532.0f4319ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> @ 2008-09-02 8:12 ` xiaowinky 0 siblings, 0 replies; 4+ messages in thread From: xiaowinky @ 2008-09-02 8:12 UTC (permalink / raw) To: Jean Delvare, i2c-GZX6beZjE8VD60Wz+7aTrA [-- Attachment #1.1: Type: text/plain, Size: 2582 bytes --] hi,Jean! my kernel version is 2.6.10_mvl401!I use "#i2cdetect 0"command to probe the I2C address range,I get a long list (shown below) > >WARNING! This program can confuse your I2C bus, cause data loss and worse!> > I will probe file /dev/i2c/0.> > I will probe address range 0x03-0x77.> > Continue? [Y/n]I do not understand above meaning,Please advise!sorry for my english. Thanks your reply, winkyxiao! > Date: Tue, 2 Sep 2008 09:15:32 +0200> From: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> To: nanguangzhixing-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org> CC: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org> Subject: Re: [i2c] FW: HELP ME! DM355 EVM MT9T001 question!> > On Tue, 2 Sep 2008 01:35:00 +0800, xiaowinky wrote:> > hi,all!> > I use the i2c-tools-3.0.1 tool to compile and install in DM355 EVM kernel,> > Which kernel version are you using?> > > For example with orders #i2cdetect 0,> > prompts following information:> > WARNING! This program can confuse your I2C bus, cause data loss and worse!> > I will probe file /dev/i2c/0.> > I will probe address range 0x03-0x77.> > Continue? [Y/n]> > What is the output of this command?> > > Then the basis bus address range 0x03-0x07,orders the test with below:> > #i2cdump 0 0x03-0x77,> > only 0x5D and 0x1B two bus addresses are ef fective, For example # i2cdump 0 0x5d> > prompt the information to be as follows:> > No size specified (using byte-data access)> > Error: Could not set address to 0x5d: Device or resource busy> > This means that there's already a kernel driver bound to this device.> To find out which it is, you can follow the driver link> in /sys/bus/i2c/devices/0-005d.> > To solve this, you can either unload the driver in question (with> rmmod), or you can pass option "-f" to i2cdump to force i2c-dev to> access the device even though it is busy. But beware that this might> confuse the kernel driver that is bound to the device, so this is> generally discouraged.> > > > > Other bus address is invalid, For example : # i2cdump 0 0x3a> > prompts the information to be as follows:> > No size specified (using b yte-data access)> > WARNING! This program can confuse your I2C bus, cause data loss and worse!> > I will probe file /dev/i2c/0, address 0x3a, mode byte> > Continue? [Y/n]> > > > Whether only 0x5D and the 0xB1 two device address hang on the I2C bus ???> > I don't understand this question, sorry. Please rephrase in proper> English.> > -- > Jean Delvare _________________________________________________________________ 谈话枯燥无味?让MSN魔法书来点缀您的MSN! http://im.live.cn/emoticons/?ID=6 [-- Attachment #1.2: Type: text/html, Size: 3322 bytes --] [-- Attachment #2: Type: text/plain, Size: 157 bytes --] _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-09-02 8:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <rUwzhhPSZ00096e49@blu0-omc2-s21.blu0.hotmail.com>
[not found] ` <BLU111-W21AE70F6BF9A6CFACB1D7AB7600@phx.gbl>
[not found] ` <AEA06231B7D16F4CA77C0C1550F3D73005DDD727@sin2apfpew01.ap.sanm.corp>
[not found] ` <BLU111-W438DFF6CC1D3E1028E9BB1B7600@phx.gbl>
[not found] ` <bfd52c5b0808280642o5d30b0f1g77240bd5e0165b16@mail.gmail.com>
[not found] ` <bfd52c5b0808280642o5d30b0f1g77240bd5e0165b16-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-01 17:35 ` FW: HELP ME! DM355 EVM MT9T001 question! xiaowinky
[not found] ` <BLU111-W4910427AB2C320E39BF04CB75C0-MsuGFMq8XAE@public.gmane.org>
2008-09-02 7:15 ` Jean Delvare
[not found] ` <BLU111-W23C107BF557C2DEB8093CFB75F0@phx.gbl>
[not found] ` <BLU111-W23C107BF557C2DEB8093CFB75F0-MsuGFMq8XAE@public.gmane.org>
2008-09-02 8:07 ` Jean Delvare
[not found] ` <20080902091532.0f4319ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-09-02 8:12 ` FW: HELP ME! " xiaowinky
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox