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
| ||
|
Date: Thu, 22 Nov 2012 10:30:20 -0700 From: Jason Gunthorpe <jgunthorpe@...idianresearch.com> To: Grant Likely <grant.likely@...retlab.ca> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Rob Herring <rob.herring@...xeda.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, devicetree-discuss <devicetree-discuss@...ts.ozlabs.org> Subject: Re: [PATCH] of: Have of_device_add call platform_device_add rather than device_add On Thu, Nov 22, 2012 at 03:36:21PM +0000, Grant Likely wrote: > Hmm... I've not tried it with assigned-address. I tried with two sibling > platform devices using just the 'reg' property. That the kernel will > complain about. For powerpc-only, the patch I posted allows the device > to get registered anyway even though the range incorrectly overlaps. My second example was done with the reg property.. gpio0: gpio@...00 { compatible = "marvell,orion-gpio"; #gpio-cells = <2>; gpio-controller; reg = <0x10100 0x40>; } chip_cfg@0 { compatible = "orc,chip_config"; // Doubles up on gpio0 reg = <0x10100 0x4>; }; f1010100-f101013f : /internal@...00000/gpio@...00 f1010100-f1010103 : /internal@...00000/chip_cfg@0 What did you try? Maybe order matters? Regards, Jason -- 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