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:	Thu, 6 Jun 2013 13:22:04 +0100
From:	"luke.leighton" <luke.leighton@...il.com>
To:	Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>
Cc:	devicetree-discuss <devicetree-discuss@...abs.org>,
	Stephen Warren <swarren@...dotorg.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	debian-arm@...ts.debian.org,
	"jonsmirl@...il.com" <jonsmirl@...il.com>,
	ARM Linux Mailing List <linux-arm-kernel@...ts.infradead.org>,
	debian-kernel@...ts.debian.org
Subject: Re: [Arm-netbook] getting allwinner SoC support upstream (was Re:
 Uploading linux (3.9.4-1))

On Thu, Jun 6, 2013 at 1:19 AM, Henrik Nordström
<henrik@...riknordstrom.net> wrote:
> tor 2013-06-06 klockan 00:54 +0100 skrev luke.leighton:
>
>> > Not really the case. Actually the opposite. DT have this as well, and
>> > integrated in device probing. Allwinner need to hack every driver used
>> > to add their gpio requests to have pinmuxing triggered.
>>
>>  augh.  ok.  solutions.  what are the solutions here?
>
> What I said before.

 idea: hook into devicetree gpio functions to allow script-fex gpio
functions to gain access in a separate module?  that sort of thing.

> Go with DT for the kernel. There is no need for two configuration
> mechanisms doing the same thing. Disguise it in fex form (and
> translator) if too hard for people with a DOS editior to configure.

 what methods for doing that.  i need proposals.  4 days on the clock.
--
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