linux-kernel - Re: [PATCH] i2c/busses: (mpc) Add support for SMBUS_READ_BLOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111115210528.0f9a0948@endymion.delvare>
Date:	Tue, 15 Nov 2011 21:05:28 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	guenter.roeck@...csson.com
Cc:	Tabi Timur-B04825 <B04825@...escale.com>,
	Ben Dooks <ben-linux@...ff.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tang Yuantian-B29983 <B29983@...escale.com>
Subject: Re: [PATCH] i2c/busses: (mpc) Add support for SMBUS_READ_BLOCK_DATA

On Tue, 15 Nov 2011 11:14:47 -0800, Guenter Roeck wrote:
> On Tue, 2011-11-15 at 14:02 -0500, Tabi Timur-B04825 wrote:
> > I think it's very important to keep the order as-is, if at all
> > possible.  This driver is very old and the hardware is used on all of
> > our SOCs, dating back several years.  It would be a nightmare to test
> > it all over again.
>
> I'll see if I can work around that. 1-byte block reads may be tricky,
> though, but maybe I can get that working as well.

IMHO it's OK if 1-byte blocks are not supported. In practice the length
of blocks seems to be known in advance and it's never 1. We can revisit
if this is ever needed in practice for this specific bus driver.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/