Skip to contentSkip to conversation

linux kernel config converter

DISCUSSION Giacomo Catenazzi 2 participants 4 messages Feb 21, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · Roman Zippel

Hi,

config: ULTRIX_PARTITION
define_bool

    default: y
    dep: ((!PARTITION_ADVANCED?) && DECSTATION=y)
Quoted 8 lines

bool
prompt: Ultrix partition table support
dep: PARTITION_ADVANCED?
help:
Say Y here if you would like to be able to read the hard disk partition table format used by DEC (now Compaq) Ultrix machines. Otherwise, say N.

From old discussion in kbuild list:
1) default: Eric proposed to include defaults in configuration, but it seems that is a bad things, and defaults should be arch specific. (I don't remember the discussion, but you can parse the kbuild list, torque.net time)
2) One of the problem in actual configure are the dependencies. FOO depend on BAR and BEER.
Wat are the possible value of FOO if BAR=m, BEER=y. In kernel we have some drivers thet need foo to be n or y, in other cases: n or m.
The logical operators hide the true dependency table. (don't expect developers read the docs: the logical operators seems like C operators, so they use like C, but they forget the third case (=m) ).

Do you use the python identation mode?

giacomo

#2 lore raw

Hi,

Quoted 4 lines · Giacomo Catenazzi

1) default: Eric proposed to include defaults in configuration, but it seems that is a bad things, and defaults should be arch specific. (I don't remember the discussion, but you can parse the kbuild list, torque.net time)

The defaults are just 1:1 representation of the current define_xxx statements. These can be of course later moved or depreciated or whatever.

Quoted 9 lines

2) One of the problem in actual configure are the dependencies. FOO depend on BAR and BEER.
Wat are the possible value of FOO if BAR=m, BEER=y. In kernel we have some drivers thet need foo to be n or y, in other cases: n or m.
The logical operators hide the true dependency table. (don't expect developers read the docs: the logical operators seems like C operators, so they use like C, but they forget the third case (=m) ).

For most cases I've seen it can be very simply defined with:

	(a && b && ...) = min(a, b, ...)
	(a || b || ...) = max(a, b, ...)
	for 'n'=0, 'm'=1, 'y'=2

I have to check the other cases and I haven't look too closely, yet, but e.g. in this case it goes wrong:

config: FB_MATROX_G450
dep_tristate
prompt: G450/G550 second head support
dep: (VT? && EXPERIMENTAL? && FB? && EXPERIMENTAL? && PCI? && FB_MATROX??!=n && FB_MATROX_G100?)

CONFIG_FB_MATROX_G450 can be defined to 'y' and CONFIG_FB_MATROX to 'm', the result is that the build goes wrong. By removing '!=n' above rule would produce the correct result.
Do you have some real examples?

Quoted 1 line

Do you use the python identation mode?

No python. Just c, flex and bison. :-)

bye, Roman

#3 lore raw
Quoted 5 lines · Roman Zippel

Hi,

On Thu, 21 Feb 2002, Giacomo Catenazzi wrote:

Quoted 8 lines
Quoted 5 lines

1) default: Eric proposed to include defaults in configuration, but it seems that is a bad things, and defaults should be arch specific. (I don't remember the discussion, but you can parse the kbuild list, torque.net time)

The defaults are just 1:1 representation of the current define_xxx statements. These can be of course later moved or depreciated or whatever.

Ok. But actually the defaults come mainly from config.def. The define_xxx are uset to set a symbols in some situations.

BTW for people who like the old configure (or fix it):
: if xxx
: define_bool CONFIG_FOO
: else
: bool CONFIG_FOO
: fi
is incorrect. You should revert the definition order (before bool than define_bool) else xconfig will break.

Quoted 11 lines
Quoted 10 lines

2) One of the problem in actual configure are the dependencies. FOO depend on BAR and BEER.
Wat are the possible value of FOO if BAR=m, BEER=y. In kernel we have some drivers thet need foo to be n or y, in other cases: n or m.
The logical operators hide the true dependency table. (don't expect developers read the docs: the logical operators seems like C operators, so they use like C, but they forget the third case (=m) ).

Quoted 4 lines

For most cases I've seen it can be very simply defined with:

	(a && b && ...) = min(a, b, ...)
	(a || b || ...) = max(a, b, ...)
	for 'n'=0, 'm'=1, 'y'=2

With this you have a value (i.e. n,m,y).
How is the actual symbol range?

CONFIG_FOO:
dep: (FREE? && BEER?)

how you tell configuration rools that
FOO can be only min/max of (FREE? && BEER?)

Quoted 1 line

Do you have some real examples?

No by hand. But I can search in rules.

Quoted 4 lines
Quoted 2 lines

Do you use the python identation mode?

No python. Just c, flex and bison. :-)

I mean: Do you use pythons mode to tell when a help description end (no tab: new symbol), few spaces:
is symbol help or configuration symbols)

giacomo

#4 lore raw

Hi,

Quoted 7 lines · Giacomo Catenazzi

How is the actual symbol range?

CONFIG_FOO:
dep: (FREE? && BEER?)

how you tell configuration rools that
FOO can be only min/max of (FREE? && BEER?)

I'm not sure I understand you correctly, but the symbol range in this example would be from 'n' to min(FREE, BEER).

Quoted 3 lines

I mean: Do you use pythons mode to tell when a help description end (no tab: new symbol), few spaces:
is symbol help or configuration symbols)

There is no new config specification yet, I just dump the information in the database in a somewhat readable format.

bye, Roman