From: Wolfram Sang <wsa@the-dreams.de>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] i2c-tools: i2ctransfer: add new tool
Date: Sat, 9 May 2015 08:50:30 +0200 [thread overview]
Message-ID: <20150509065030.GA1511@katana> (raw)
In-Reply-To: <20150508234042.26708f86@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi Jean,
> If you think it's not enough, then the address modifier could go
> separately before or after the address byte, i.e. either r1@0x123t or
> r1@t0x123. I suspect that the latter should be easier to implement.
In deed, I would aim for maximum flexibility (i.e. possible to mix 7 and
10 bit addresses), and implement the latter proposal of yours.
> > Handling R/W as "just another" flag made this option extremly simple.
> > But we probably can work something out.
>
> I think the proposal above makes more sense than grouping it with the
> direction letter (r or w)
I agree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] i2c-tools: i2ctransfer: add new tool
Date: Sat, 09 May 2015 06:50:30 +0000 [thread overview]
Message-ID: <20150509065030.GA1511@katana> (raw)
In-Reply-To: <20150508234042.26708f86@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi Jean,
> If you think it's not enough, then the address modifier could go
> separately before or after the address byte, i.e. either r1@0x123t or
> r1@t0x123. I suspect that the latter should be easier to implement.
In deed, I would aim for maximum flexibility (i.e. possible to mix 7 and
10 bit addresses), and implement the latter proposal of yours.
> > Handling R/W as "just another" flag made this option extremly simple.
> > But we probably can work something out.
>
> I think the proposal above makes more sense than grouping it with the
> direction letter (r or w)
I agree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-09 6:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 16:16 [RFC] i2c-tools: i2ctransfer: add new tool Wolfram Sang
2015-02-27 16:16 ` Wolfram Sang
2015-02-27 16:16 ` Wolfram Sang
[not found] ` <1425053816-19804-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-04-20 17:36 ` Wolfram Sang
2015-04-20 17:36 ` Wolfram Sang
2015-04-20 17:36 ` Wolfram Sang
2015-04-21 5:25 ` Jean Delvare
2015-04-21 5:25 ` Jean Delvare
2015-04-21 5:25 ` Jean Delvare
[not found] ` <20150421072551.326bb4b7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-04-21 7:06 ` Wolfram Sang
2015-04-21 7:06 ` Wolfram Sang
2015-04-21 7:06 ` Wolfram Sang
2015-05-07 20:08 ` Jean Delvare
2015-05-07 20:08 ` Jean Delvare
2015-05-08 8:54 ` Jean Delvare
2015-05-08 8:54 ` Jean Delvare
2015-05-08 14:38 ` Wolfram Sang
2015-05-08 14:38 ` Wolfram Sang
2015-05-08 21:40 ` Jean Delvare
2015-05-08 21:40 ` Jean Delvare
2015-05-08 21:40 ` Jean Delvare
2015-05-09 6:50 ` Wolfram Sang [this message]
2015-05-09 6:50 ` Wolfram Sang
[not found] ` <20150508105401.223a8598-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-05-08 15:28 ` Randy Grunwell
2015-05-08 15:28 ` Randy Grunwell
2015-05-08 15:28 ` Randy Grunwell
2015-05-08 18:28 ` Uwe Kleine-König
2015-05-08 18:28 ` Uwe Kleine-König
2015-05-08 20:58 ` Jean Delvare
2015-05-08 20:58 ` Jean Delvare
[not found] ` <20150507220812.3776bb83-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-05-09 7:09 ` Wolfram Sang
2015-05-09 7:09 ` Wolfram Sang
2015-05-09 7:09 ` Wolfram Sang
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=20150509065030.GA1511@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jdelvare@suse.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.