From: Erik Theisen <etheisen@mindspring.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: CONFIG_DTT_LM75 and CFG_EEPROM_PAGE_WRITE_ENABLE ???
Date: Sat, 16 Apr 2005 00:16:26 -0400 [thread overview]
Message-ID: <df191d48cb730e4b5a5eabb5661121c4@mindspring.com> (raw)
In message <425E665D.7030401@im...> Steven Scholz wrote:
> is it realy necessary to define CFG_EEPROM_PAGE_WRITE_ENABLE in order
> to use
> the LM75 within U-Boot?
>
> #ifdef CONFIG_DTT_LM75
> #if !defined(CFG_EEPROM_PAGE_WRITE_ENABLE) || \
> (CFG_EEPROM_PAGE_WRITE_BITS < 1)
> # error "CFG_EEPROM_PAGE_WRITE_ENABLE must be defined and
> CFG_EEPROM_PAGE_WRITE_BITS must be greater than 1 to use
> CONFIG_DTT_LM75"
> #endif
This is going somewhat on recollection...
The lm75 requires a multibyte write. The old i2c layer only worked
with 1 byte at a time unless page
writes were used. The newer i2c allows multibyte writes by default.
I believe it can go away.
Erik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 815 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050416/848de182/attachment.bin
reply other threads:[~2005-04-16 4:16 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=df191d48cb730e4b5a5eabb5661121c4@mindspring.com \
--to=etheisen@mindspring.com \
--cc=u-boot@lists.denx.de \
/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