From: tony@atomide.com
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: I2C zero length transfers and SMBUS_QUICK, was: Pending October patches
Date: Tue, 7 Nov 2006 19:40:40 +0200 [thread overview]
Message-ID: <20061107174039.GG6215@atomide.com> (raw)
In-Reply-To: <200611051737.11242.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [061106 03:44]:
> On Sunday 05 November 2006 2:32 am, Dirk Behme wrote:
> >
> > Our hack to make things work on OMAP will not be accepted
> > upstream. But staying with broken OMAP features only because
> > (available) hack isn't acceptable in mainline doesn't sound
> > like an option as well.
> >
> > I personally vote for working OMAP ;)
>
> Me too ... the sad part is that this is basicallly a design bug
> in the upstream I2C stack, and over the past couple years there
> have been no evident signs of it ever getting fixed.
I wonder if we could help somehow by doing "embedded i2c stack"
by modifying your SPI framework to support i2c?
Tony
next prev parent reply other threads:[~2006-11-07 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 15:54 Pending October patches Dirk Behme
2006-11-01 21:28 ` tony
2006-11-02 17:00 ` Dirk Behme
2006-11-03 10:50 ` Komal Shah
2006-11-05 10:32 ` I2C zero length transfers and SMBUS_QUICK, was: " Dirk Behme
2006-11-05 19:49 ` Komal Shah
2006-11-06 10:36 ` Arnaud Patard
2006-11-06 18:33 ` Broken N770, was: I2C zero length transfers and SMBUS_QUICK Dirk Behme
2006-11-06 19:49 ` Arnaud Patard
2006-11-06 20:18 ` Broken N770 Dirk Behme
2006-11-06 20:24 ` Arnaud Patard
2006-11-06 1:37 ` I2C zero length transfers and SMBUS_QUICK, was: Pending October patches David Brownell
2006-11-07 17:40 ` tony [this message]
2006-11-07 20:24 ` I2C zero length transfers and SMBUS_QUICK David Brownell
2006-11-09 2:32 ` Tony Lindgren
2006-11-03 19:52 ` Pending October patches David Brownell
2006-11-03 20:18 ` Dirk Behme
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=20061107174039.GG6215@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.