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: <20110318232553.GA11422@opensource.wolfsonmicro.com>
Date:	Fri, 18 Mar 2011 23:25:53 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	andy.green@...aro.org
Cc:	Arnd Bergmann <arnd@...db.de>, Greg KH <greg@...ah.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	devicetree-discuss@...ts.ozlabs.org,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On Fri, Mar 18, 2011 at 09:33:00PM +0000, Andy Green wrote:

> Well: Greg was also reduced to explaining that device renaming in  
> userland was decided "a long time ago".  It's not argumentation, it is  
> an appeal to an alleged tradition.

The story with device renaming is fairly simple - nobody could agree on
what the ideal names should be and different userlands ended up wanting
different things so rather than try to keep everyone happy the kernel
picked the simplest policy possible and let userland override it to its
heart's content.

> You think that striving away to create this Device Tree description of a  
> specific board and maintaining it in a bootloader is LESS work somehow  
> that registering platform devices in an array in the board definition  
> file?  I think not.

It's more the fact that it can be distributed separately to the kernel
which reduces the pressure to mainline the basic board description stuff
for ongoing maintinance.
--
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