On 12-07-26 01:02 PM, Randy Dunlap wrote:
> The added y/n/m are clear, but the "!FRV FRV" is confusing,
> isn't it?
>
>
Is this notation clear ?
Kernel support for ELF binaries (BINFMT_ELF)
type: boolean
unknown property: symbol
dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
prompt: Kernel support for ELF binaries
dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
default: y
dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
If not, could you suggest a better way to represent this information?
Thanks.
On 08/07/2012 09:08 AM, Salar Ali Mumtaz wrote:
> On 12-07-26 01:02 PM, Randy Dunlap wrote:
>
>> The added y/n/m are clear, but the "!FRV FRV" is confusing,
>> isn't it?
>>
>>
>
> Is this notation clear ?
>
> Kernel support for ELF binaries (BINFMT_ELF)
>
> type: boolean
> unknown property: symbol
> dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
> prompt: Kernel support for ELF binaries
> dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
> default: y
> dep: ( MMU [=y] && (BROKEN [n] || !FRV [= ""]) ) [=y]
In Kconfig language, is "" the same as 'n' ?
If so, I'm OK with your proposal above.
> If not, could you suggest a better way to represent this information?
>
> Thanks.
thanks,
--
~Randy
On 12-08-07 12:55 PM, Randy Dunlap wrote:
> In Kconfig language, is "" the same as 'n' ?
> If so, I'm OK with your proposal above.
>
So a colleague of mine tested this and came up with a conclusion that expressions in Kconfig can only deal with boolean or tristate operands and no casting is made with strings. Using any string operand as part of a boolean expression is simply a type error and Kconfig probably marks such operand as 'n', regardless of its value.
On 08/09/2012 11:54 AM, Salar Ali Mumtaz wrote:
> On 12-08-07 12:55 PM, Randy Dunlap wrote:
>
>> In Kconfig language, is "" the same as 'n' ?
>> If so, I'm OK with your proposal above.
>>
>
>
> So a colleague of mine tested this and came up with a conclusion that expressions in Kconfig can only deal with boolean or tristate operands and no casting is made with strings. Using any string operand as part of a boolean expression is simply a type error and Kconfig probably marks such operand as 'n', regardless of its value.
>
My question was about FRV, which is a boolean,
but still did not display as 'n' in your example.
--
~Randy
On 12-08-10 08:39 PM, Randy Dunlap wrote:
> On 08/09/2012 11:54 AM, Salar Ali Mumtaz wrote:
>
>> On 12-08-07 12:55 PM, Randy Dunlap wrote:
>>
>>> In Kconfig language, is "" the same as 'n' ?
>>> If so, I'm OK with your proposal above.
>>>
>>
>>
>> So a colleague of mine tested this and came up with a conclusion that expressions in Kconfig can only deal with boolean or tristate operands and no casting is made with strings. Using any string operand as part of a boolean expression is simply a type error and Kconfig probably marks such operand as 'n', regardless of its value.
>>
>
>
> My question was about FRV, which is a boolean,
> but still did not display as 'n' in your example.
>
>
FRV is not a boolean.
On 08/15/2012 09:32 AM, Salar Ali Mumtaz wrote:
> On 12-08-10 08:39 PM, Randy Dunlap wrote:
>> On 08/09/2012 11:54 AM, Salar Ali Mumtaz wrote:
>>
>>> On 12-08-07 12:55 PM, Randy Dunlap wrote:
>>>
>>>> In Kconfig language, is "" the same as 'n' ?
>>>> If so, I'm OK with your proposal above.
>>>>
>>>
>>>
>>> So a colleague of mine tested this and came up with a conclusion that expressions in Kconfig can only deal with boolean or tristate operands and no casting is made with strings. Using any string operand as part of a boolean expression is simply a type error and Kconfig probably marks such operand as 'n', regardless of its value.
>>>
>>
>>
>> My question was about FRV, which is a boolean,
>> but still did not display as 'n' in your example.
>>
>>
>
> FRV is not a boolean.
Hm, why do you say that? Please explain.
from arch/frv/Kconfig:
config FRV
bool
default y
--
~Randy