linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chip <chipslice-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Looking for i2c-sibyte block read/write patch
Date: Thu, 17 Dec 2009 18:16:32 -0500	[thread overview]
Message-ID: <15a867370912171516o17f31d63g2e5abd0665446338@mail.gmail.com> (raw)

I've seen this topic mentioned  in the archives but have not been able
to find the patch.

I'd like to use the i2c extended protocol support feature of the
Broadcom BCM1250 family to be able to read and write multiple bytes
(>2) from i2c devices. SMBus block read/write would be great, generic
i2c support would be even greater.

Is this implemented ? Any suggestions on where I can get the patch ?

Thanks in advance.
Chip

             reply	other threads:[~2009-12-17 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 23:16 Chip [this message]
     [not found] ` <15a867370912171516o17f31d63g2e5abd0665446338-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-18  9:50   ` Looking for i2c-sibyte block read/write patch Jean Delvare

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=15a867370912171516o17f31d63g2e5abd0665446338@mail.gmail.com \
    --to=chipslice-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).