linux-kernel - Re: [PATCH][RFC][POWERPC] i2c: adds support for i2c bus on 8xx

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>] [day] [month] [year] [list]

Date:	Wed, 25 Apr 2007 13:53:45 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Vitaly Bordug <vitb@...nel.crashing.org>
CC:	Olof Johansson <olof@...om.net>, Jean Delvare <khali@...ux-fr.org>,
	"linuxppc-dev@...abs.org" <linuxppc-dev@...abs.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][RFC][POWERPC] i2c: adds support for i2c bus on 8xx

Vitaly Bordug wrote:
> i2c && 8xx combo never work with 2.6 at least in mainstream. That's why 
> related stuff were scheduled to removal by Jean even,
> before I came up with this stuff.
[snip]
>> This could all be done with an of_platform driver instead, and avoid 
>> the above.
>> (Someone else already suggested that I believe).
>>
>>   
> 
> I know i know. But it was decided, while both ppc/ and powerpc/ wander 
> around, platform devices way is preferrable.

The idea is to avoid regressions in arch/ppc; maintaining feature parity 
isn't necessary.  If, as you say above, 8xx i2c was already broken in 
2.6 (even in arch/ppc), then I see no reason not to go to an of_device 
right away.

> It is apparent why - so far only mpc885 is alive in arch/powerpc, and it 
> is not going to change soon for 8xx. 

Actually, I plan to do some arch/powerpc 8xx work over the next couple 
months, so hopefully it will change soon. :-)

-Scott
-
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/