From: "Alexander Povolotsky" <pevnev@juno.com>
To: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: question on CONFIG_I2C_SPI_UCODE_PATCH and CONFIG_I2C_SPI_SMC1_UCODE_P ATCH
Date: Wed, 9 Feb 2005 18:22:10 GMT [thread overview]
Message-ID: <20050209.102300.2012.117453@webmail01.lax.untd.com> (raw)
Hi,
I have a question on use of CONFIG_I2C_SPI_UCODE_PATCH and CONFIG_I2C_SPI_SMC1_UCODE_PATCH in Linux 2.6.
Could someone from this list explain for me what problems each of those two patches are addressing ?
I have MPC 880 based board with single 24C02 I2C EEPROM,
connected to the I2C bus and currently (without those two patches configured in .config) I have problem of communicating
over I2C bus with that device - scanning for any address (in the range between 0 and 128) on the I2C bus does not get any response (interrupt)
so code remains in the sleep (on interrupt) mode.
Would applying (any or both) above patches resolve my problem as described ?
Thanks,
Best Regards,
Alex
___________________________________________________________________
Speed up your surfing with Juno SpeedBand.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.juno.com/surf to sign up today!
reply other threads:[~2005-02-09 18:23 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=20050209.102300.2012.117453@webmail01.lax.untd.com \
--to=pevnev@juno.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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).