LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Naru Sundar <nsundar@fulcrummicro.com>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6 (eldk) - I2C constants
Date: Fri, 26 May 2006 07:33:11 -0700	[thread overview]
Message-ID: <447711A7.5060200@fulcrummicro.com> (raw)

Hello folks, I'm porting a 2.4 driver over to 2.6 and noted some 
weirdness in the I2C headers.  I thought it was worth checking out here.

include/linux/i2c.h in 2.4 defined the following constants:
#define I2C_M_TEN   0x10    /* we have a ten bit chip address   */
#define I2C_M_RD    0x01
#define I2C_M_WR        0x00    /* For readable code!                   */
#define I2C_M_NOSTART   0x4000
#define I2C_M_REV_DIR_ADDR  0x2000

in ELDK 2.6 source drop I have (2.6.15), the I2C_M_WR constant was removed.

Any thoughts? I can declare that constant locally in the driver, but 
since these were standard I2C message constants I thought something
odd was up (or am I missing something obvious).

Thanks

--
Naru Sundar <nsundar@fulcrummicro.com>
Fulcrum Microsystems
http://www.fulcrummicro.com

                 reply	other threads:[~2006-05-26 14:54 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=447711A7.5060200@fulcrummicro.com \
    --to=nsundar@fulcrummicro.com \
    --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