[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6ir58jrXbFmBPWJ0ztUMPY2Y6P8ZixsbD=20+RmQUo+OSQ@mail.gmail.com>
Date: Tue, 29 May 2012 00:58:33 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Cherry-picking from Lukas' repo
2012/5/29 magnum <john.magnum@...hmail.com>:
> On 05/29/2012 12:40 AM, Lukas Odzioba wrote:
>> 2012/5/29 magnum <john.magnum@...hmail.com>:
>>> Not sure what you mean with earlier, but --device=list or
>>> --platform=list will call that.
>>
>> Thank you, I couldn't find it in ./john output:
>>
>> --platform=N (or =LIST) set OpenCL platform, default 0
>> --device=N set OpenCL device, default 0
>>
>> I thought that LIST means sth like 1,2 isn't it misleading for user?
>> Just asking.
>
> I just mimiced existing options, like --subformat=LIST. But hey, you
> have a point: If/when we are going to support multiple devices it could
> be given as eg. --device=0,1.
This looks natural, I like it.
> For now we could change the usage blob to
>
> --platform=N (or =LIST) set OpenCL platform, default 0 (or list them)
>
> Is that a little more clear? The 80 char line limit force us to be very
> terse. An alternative is:
Alternative is empty:) but your first proposition is fine.
Lukas
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
