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:	Tue, 18 Jan 2011 22:26:15 +0800
From:	Thomas Chou <thomas@...ron.com.tw>
To:	Walter Goossens <waltergoossens@...e.nl>
CC:	Grant Likely <grant.likely@...retlab.ca>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org, nios2-dev@...c.et.ntust.edu.tw,
	linux-input@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org
Subject: Re: [PATCH] alter_ps2: Add devicetree support

On 01/18/2011 07:27 AM, Walter Goossens wrote:
>> so, instead of trying to us a 'generic' value like "altera,altera_ps2"
>> which has a bunch of ambiguity about which hardware actually
>> implements the behaviour, the values "altera,altera_ps2-1" and
>> "altera,altera_ps2-3" become the de-facto 'generic' values without any
>> messiness or ambiguity about what they mean.
>>
>> Plus, each .dts file still specifies the exact version that is
>> implemented on the board so that the driver can still fixup
>> version-specific bugs if any are discovered in the future.
>>
> Ahh ok.
> That does look like a good solution. I'll try and cook something up for
> that.

Hi Walter,

Can we use "kind" and "version" attribute of a sopcinfo file to build 
the match string? This way, your dts converter won't need update for 
each new component.

eg,

kind="altera_avalon_spi" version="9.0" ==> "altera","avalon-spi-9.0"

kind="altera_up_avalon_ps2_classic" version="6.1" ==>
   "altera","up-avalon-ps2-classic-6.1"

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