From: Robert Schwebel <r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: alfred steele <alfred.jaquez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: "I2C_RDWR" ioctl returning EINVAL on Freescale mxc
Date: Tue, 18 Aug 2009 08:13:35 +0200 [thread overview]
Message-ID: <20090818061335.GB29655@pengutronix.de> (raw)
In-Reply-To: <528f13590908172025i276dc634qd0829cfad8c8c608-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Alfred,
On Mon, Aug 17, 2009 at 10:25:34PM -0500, alfred steele wrote:
> I skimmed through the imx-i2c.c and ompared it to the driver i have
> mxc-i2c. I do not understand how the changes might affect the IOCTL
> "I2C_RDWR".Can you please elaborate? At the bottom is the mxc-i2c
> driver i have.
> Isn't i2c-dev "i2c-dev.c" driver responsible for returning EINVAL
> based on some validation checks. Has that also changed in the latest
> GIT.
Between 2.6.24 and 2.6.31-dirty are about 156849 patches, not to mention
what Freescale may have patched in your kernel. It might effect your
problem or it might not.
Could you test against mxc-master? If you do, others in the community
can reproduce your problem quickly and might find a fix.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2009-08-18 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 21:09 "I2C_RDWR" ioctl returning EINVAL on Freescale mxc alfred steele
[not found] ` <528f13590908141409g4b2556e5m10aec0dc15429457-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17 6:53 ` Robert Schwebel
[not found] ` <20090817065313.GJ31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-17 14:51 ` alfred steele
[not found] ` <528f13590908170751u4dcf6d8ftb865103b888225e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17 15:01 ` Robert Schwebel
[not found] ` <20090817150159.GT31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-17 21:04 ` alfred steele
[not found] ` <528f13590908171404q2aa4f9aaub98a191c91bd2448-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17 21:21 ` Robert Schwebel
[not found] ` <20090817212127.GB31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-18 3:25 ` alfred steele
[not found] ` <528f13590908172025i276dc634qd0829cfad8c8c608-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-18 6:13 ` Robert Schwebel [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=20090818061335.GB29655@pengutronix.de \
--to=r.schwebel-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=alfred.jaquez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).