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: <1379574653.6148.62.camel@pasglop>
Date:	Thu, 19 Sep 2013 17:10:53 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Olof Johansson <olof@...om.net>
Cc:	Stephen Warren <swarren@...dotorg.org>, Jon Loeliger <jdl@....com>,
	David Gibson <david@...son.dropbear.id.au>,
	Frank Rowand <frowand.list@...il.com>,
	Tomasz Figa <tomasz.figa@...il.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Rob Herring <rob.herring@...xeda.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [dtc RFC PATCH] Enforce node name unit-address presence/absence

On Wed, 2013-09-18 at 13:41 -0700, Olof Johansson wrote:
> Also, maybe warn for @0x<foo>, which is another unpreferred syntax, it
> should just be @<foo> (with foo being in hex).

It can also bee @foo,bar, it doesn *have* to match the exact content of
the reg property first entry. In fact it's not uncommon to use a 64-bit
value here on 64-bit processors and pci uses a different encoding scheme
(on real OFW at least) where they typically do @dev,fn

Yes, the fact that the unit address is not something deterministic is
and has always been a major PITA though.

Cheers,
Ben.


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