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]
Date:	Sat, 18 Oct 2008 13:54:23 -0700
From:	David Brownell <david-b@...bell.net>
To:	"Piotr Skamruk" <piotr.skamruk@...il.com>
Cc:	"Michael Buesch" <mb@...sch.de>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Magnus Damm" <magnus.damm@...il.com>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] Add SPI over GPIO driver

On Saturday 18 October 2008, Piotr Skamruk wrote:
> 2008/10/18 Michael Buesch <mb@...sch.de>:
> > On Saturday 18 October 2008 06:36:31 Andrew Morton wrote:
> >> This patch has some "issues" a month or so ago.  Current status is that
> >
> > yeah, upstream maintainers don't like these patches.
> > Please drop this one and the "gpiommc" patch now.
> >
> As i remember - David stands that these patches (or even
> functionality) are not usable for him, so he don't want to see them in
> mainstream kernel sources. It's his choice, he is maintainer of this
> subsystem.

That patch is very limited, and wrong in several respects.

I fully support the idea of SPI over GPIO.  It's just that
particular patch which is problematic.


> You have this on openwrt svn, I have it on my dev gittree - and as You
> can see on Magnus example - anybody interested can google for it.
> Maybe if there will be next few peoples - David will change his
> opinion on this subject...

I'm sanity testing a refresh of the *original* late-2006
SPI-over-GPIO driver.  It's actually usable as a drop-in
replacement for a "native" driver.

Unfortunately I goofed and pulled down the current GIT tree
and found lots of unrelated breakage (non-SPI) that's keept
that sanity test from proceeding apace.  And the board on
which it's most recently been used is currently broken.
I may just send that patch out soon, as an FYI...

- Dave

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ