Randy.Dunlap wrote:
Is there a simple, clean way to assign one tristate value to
another one? Instead of having to do something like:
if [ $CONFIG_PARPORT_PC = y ]; then
define_tristate CONFIG_PARPORT_PC_CML1 y
else
if [ $CONFIG_PARPORT_PC = m ]; then
Sam Ravnborg wrote:
On Tue, Aug 27, 2002 at 02:24:40AM +0200, Roman Zippel wrote:
Hi Roman, I really haven't had time to look at your release properly
yet, sorry. I did notice though that the converter issues warnings
for dead code and comparisons of boolean variables to m, which I
thought
Randy.Dunlap wrote:
On Sat, 24 Aug 2002, Greg Banks wrote:
| Peter Samuelson wrote:
|
|http://www.alphalink.com.au/~gnb/gcml2/
Thanks. I'm trying it out now.
BTW Greg, your checker web page spells 'dependency' as
'dependancy' in a few places.
Damn. It's a good thing I didn't
Roman Zippel wrote:
Hi,
On Thu, 22 Aug 2002, Greg Banks wrote:
Why do you want to do the parser/syntax switch separately? Why do you want
to write and test a parser just to be throw it away again?
So that the changes have some chance of getting past Linus.
Sorry, but that's
Peter Samuelson wrote:
There are lots of instances of things like
if [ $CONFIG_FOO = y -o $CONFIG_FOO = m ]; then
dep_tristate 'Bar' CONFIG_BAR $CONFIG_FOO
...
fi
which can be replaced by
dep_if CONFIG_FOO
tristate 'Bar' CONFIG_BAR
...
dep_fi
Yes,
Peter Samuelson wrote:
My current implementation of if_dep is *not*, as previously theorised,
a drop-in two-way replacement for adding dependencies to the end of
dep_* statements. I currently have it short-circuiting, so statements
are in effect *not* executing in the 'n' case (or the 'm'
G'day,
gcml2 is (among other things) a Linux kconfig language syntax
checker. Version 0.7 is available at
http://sourceforge.net/project/showfiles.php?group_id=18813release_id=106023
and
http://www.alphalink.com.au/~gnb/gcml2/download.html
There's also an online summary of the warnings and
Roman Zippel wrote:
The problem here is one should consider, how all these little changes will
help to solve the big problems. Do they allow to more easily fix the big
problems or have these changes to be dumped again?
I believe fixing the existing rules within the existing syntax is an
Kai Germaschewski wrote:
On Thu, 15 Aug 2002, Peter Samuelson wrote:
The more I think about it, the more I think the default if_dep should
do the m-restricting thing. That way:
dep_bool FOO1 BAR BAZ
dep_mbool FOO2 BAR BAZ
dep_tristate FOO3 BAR BAZ
is exactly equivalent
Peter Samuelson wrote:
[Kai Germaschewski]
I didn't look into like choice statements, but I'd hope it's
possible to add dependencies to them, too, for consistency.
I agree. Actually, if we're changing 'choice' anyway, it should be
redesigned. Status quo takes three arguments:
Peter Samuelson wrote:
My main goal is to make it easier to write Config.in files, by making
the syntax and semantics less awkward. [...]
* The current 'if' statement is really ugly and unintuitive,[...]
Agreed.
* Current 'if' semantics are hard to get right in many common cases.[...]
Brendan J Simon wrote:
Greg Banks wrote:
[*] almost enough because I haven't implemented an 'else'
directive. It would be trivial, but I'm not sure what to call it.
'else' itself is a shell primitive, so the shell-based parsers
(Configure, Menuconfig) wouldn't like
Peter Samuelson wrote:
[Giacomo A. Catenazzi]
I don't like calling it or... It is error prone because it is a non
binary system,
thus can confuse the lazy developers.
[...]But
nobody thinks of max as an infix operator, and infix is IMO the most
natural way to express a
Roman Zippel wrote:
Hi,
(Could you please fix your mailer? linux-m68k.org.com does not really
exist.)
I believe the problem is upstream of the machine I control. I'll see what I can do.
That's fine with me, but nonetheless I'd really like to know where it will
go to. Just fixing the
Peter Samuelson wrote:
[Greg Banks]
[...CONFIG_SERIAL and CONFIG_PCMCIA warnings...]
Hmmm, either I missed those in your earlier messages, or you didn't
post them.
Probably I didn't post them. What I posted was a small subset of the full log.
+ dep_tristate ' I2C bit-banging
Roman Zippel wrote:
Hi,
On Tue, 13 Aug 2002, Peter Samuelson wrote:
Mutating the language, long-term, so that it looks less like sh [...]
That doesn't solve any of the more fundamental problems.
Correct, it doesn't.
1) We still have 3 config parsers, which produce slightly
Peter Samuelson wrote:
[Greg Banks]
+2 CONFIG_KMOD
+2 CONFIG_MODULES
+2 CONFIG_MODVERSIONS
2 CONFIG_RTC
What does that mean? All I did there was to combine two toplevel
menus into one. Did this do something bad?
Apparently
Peter Samuelson wrote:
I've come up with syntax I think I'm happy with. It supports most of
the current [ ] based if statement semantics, can be implemented in
shell, and (most importantly for me) drops those $ signs. This lays
the groundwork for stuff like better error checking and auto
Roman Zippel wrote:
On Tue, 13 Aug 2002, Greg Banks wrote:
The problem is deciding what the original rules were supposed to mean, and
then reproducing that behaviour exactly in the new language. The alternative
is fixing the problems as we convert, but then we end up with CML2
Peter Samuelson wrote:
[...] what would be
*really* nice would be a way to determine that a particular forward
declared symbol is actually a never-in-this-arch declared symbol.
Ok, here it is.
Greg.
--
the price of civilisation today is a courageous willingness to prevail,
with force,
Sam Ravnborg wrote:
On Tue, Aug 13, 2002 at 01:23:19PM +1000, Greg Banks wrote:
977missing-experimental-tag
113spurious-experimental-tag
145variant-experimental-tag
30 inconsistent-experimental-tag
13 missing-obsolete-tag
41 spurious-obsolete-tag
25
Kai Germaschewski wrote:
So you agree a bit of spring cleaning wouldn't hurt, right? ;)
Absolutely, and I have a catalogue of dust puppies to help that process ;-)
Okay. Let me first state that I do not really have the time to get
involved currently. ISDN4Linux and other pending
Kai Germaschewski wrote:
On Wed, 14 Aug 2002, Greg Banks wrote:
Peter Samuelson wrote:
[Greg Banks]
Does complete mean all the ports have also made the change and
been merged back?
[...]
Actually I suspect it would be more like the C99 thing: after the new
syntax
Peter Samuelson wrote:
You're willing to potentially perturb 2.4?
This stuff is trivial enough, and easy enough to test, that I think it
could go in 2.4, yes.
I think you're underestimating the Gordian knot that is the CML1 corpus.
Obviously xconfig would need to be dealt with
in
Peter Samuelson wrote:
[...]CONFIG_BLK_DEV_IDESCSI[...]
That one example is more than enough to convince me *not* to try
changing the ignore empty deps rule for 2.4. 2.5 is a different
matter, though..
Ah, good.
This is like the Stanford checker stuff. These are bugs. You have
Roman Zippel wrote:
Most should be fixable. The biggest problem are recursive references like
this:
if [ OLD != y ]; then
tristate NEW
fi
if [ NEW != y ]; then
tristate OLD
fi
[...]It's possible to fix this:
tristate DRV
if [ DRV == y ]; then
choice OLD NEW
fi
if [ DRV
Roman Zippel wrote:
I only used it as an example, because my tool has problems to
automatically convert this construct into something useful (e.g. because
of CONFIG_WILLOW in 2 seperate choice statements).
You too? I had to rewrite my branch merging code to make CONFIG_WILLOW fit.
Greg.
Peter Samuelson wrote:
[Greg Banks]
Ah, glad you asked, see attached output from the latest version of gcml2
(not yet released).
Thank you thank you thank you! Exactly what I wanted!
Pleased to be of service ;-)
Now, while some (perhaps a lot) of these instances will break
G'day,
I like the basic idea here, and I'm pleased that someone has the courage to
tackle some of the brokenness of the kconfig language (if only because it
will provide me with a precedent when I try to submit some of my patches ;-).
I was a bit worried when I first saw the patch (after all,
Peter Samuelson wrote:
[Russell King]
Erm, !n == n ???
Duh. I need some serious sleep. That wasn't the only semantically
significant typo in my post, only the worst. Obviously, !n == y.
So what is ! ?
Greg.
--
the price of civilisation today is a courageous willingness to prevail,
G'day,
The entire ipv6 subsystem is marked EXPERIMENTAL in net/Config.in.
A raft of symbols in net/ipv6/netfilter/Config.in don't reflect
this in their banners.
diff -ruN linux-2.5.24+patches5/net/ipv6/netfilter/Config.in
linux-2.5.24/net/ipv6/netfilter/Config.in
---
G'day,
Symbol CONFIG_M68KFPU_EMU_EXTRAPREC for m68k port depends on
CONFIG_EXPERIMENTAL but does not say so in its banner.
diff -ruN linux-2.5.24+patches5/arch/m68k/config.in linux-2.5.24/arch/m68k/config.in
--- linux-2.5.24+patches5/arch/m68k/config.in Sun Jun 30 20:27:22 2002
+++
G'day,
Symbols CONFIG_PARPORT_AMIGA and CONFIG_PARPORT_MFC3 for m68k port depend
on CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.24+patches5/arch/m68k/config.in linux-2.5.24/arch/m68k/config.in
--- linux-2.5.24+patches5/arch/m68k/config.in Sun Jun 30 20:27:22
G'day,
Symbols CONFIG_PARPORT_ATARI, CONFIG_PRINTER and CONFIG_PARPORT_1284 for
m68k port depend on CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.24+patches5/arch/m68k/config.in linux-2.5.24/arch/m68k/config.in
--- linux-2.5.24+patches5/arch/m68k/config.in Sun
G'day,
Symbol CONFIG_EVB_PCI1 for mips port depends on
CONFIG_EXPERIMENTAL but does not say so in its banner.
diff -ruN linux-2.5.24+patches5/arch/mips/config.in linux-2.5.24/arch/mips/config.in
--- linux-2.5.24+patches5/arch/mips/config.in Sun Jun 30 20:27:22 2002
+++
G'day,
Symbol CONFIG_AMIGA_PCMCIA for m68k port depends on
CONFIG_EXPERIMENTAL but does not say so in its banner.
diff -ruN linux-2.5.24+patches5/arch/ppc/config.in linux-2.5.24/arch/ppc/config.in
--- linux-2.5.24+patches5/arch/ppc/config.inSun Jun 30 20:27:22 2002
+++
G'day,
Symbol CONFIG_RTC for sbus drivers depends on
CONFIG_EXPERIMENTAL but does not say so in its banner.
diff -ruN linux-2.5.24+patches5/drivers/sbus/char/Config.in
linux-2.5.24/drivers/sbus/char/Config.in
--- linux-2.5.24+patches5/drivers/sbus/char/Config.in Sun Jun 30 20:27:23 2002
+++
G'day,
Symbol CONFIG_LLC depends on CONFIG_EXPERIMENTAL but does not say
so in its banner.
diff -ruN linux-2.5.24+patches5/net/Config.in linux-2.5.24/net/Config.in
--- linux-2.5.24+patches5/net/Config.in Sun Jun 30 20:27:23 2002
+++ linux-2.5.24/net/Config.in Sun Jun 30 20:42:38 2002
@@ -64,7
G'day,
Symbols CONFIG_ECONET_AUNUDP, CONFIG_ECONET_NATIVE, CONFIG_WAN_ROUTER,
CONFIG_NET_FASTROUTE, and CONFIG_NET_HW_FLOWCONTROL depend on
CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.24+patches5/net/Config.in linux-2.5.24/net/Config.in
---
G'day,
As the symbol CONFIG_OBSOLETE is used in 6 places, we might as well
give it a non-empty value.
diff -ruN linux-2.5.24+patches5/init/Config.in linux-2.5.24/init/Config.in
--- linux-2.5.24+patches5/init/Config.inSun Jun 30 20:27:23 2002
+++ linux-2.5.24/init/Config.in Sun Jun 30
G'day,
Symbol CONFIG_EXT3_FS doesn't depend on CONFIG_EXPERIMENTAL but claims
to in its banner.
diff -ruN linux-2.5.24+patches5/fs/Config.in linux-2.5.24/fs/Config.in
--- linux-2.5.24+patches5/fs/Config.in Sun Jun 30 20:27:23 2002
+++ linux-2.5.24/fs/Config.in Sun Jun 30 22:14:55 2002
@@
G'day,
Symbols CONFIG_USB_STORAGE_DATAFAB, CONFIG_USB_STORAGE_HP8200e,
CONFIG_USB_STORAGE_SDDR09, CONFIG_USB_STORAGE_SDDR55, and
CONFIG_USB_STORAGE_JUMPSHOT depend on CONFIG_EXPERIMENTAL but
do not say so in their banners.
diff -ruN linux-2.5.24+patches5/drivers/usb/storage/Config.in
G'day,
Symbols CONFIG_FB_PM2_FIFO_DISCONNECT, CONFIG_FB_PM2_PCI, CONFIG_FB_PM2_CVPPC,
depend on CONFIG_EXPERIMENTAL but do not say so in
their banners.
diff -ruN linux-2.5.24+patches5/drivers/video/Config.in
linux-2.5.24/drivers/video/Config.in
---
G'day,
Symbols CONFIG_FB_MATROX_MILLENIUM, CONFIG_FB_MATROX_MYSTIQUE,
CONFIG_FB_MATROX_G100, CONFIG_FB_MATROX_I2C, CONFIG_FB_MATROX_MAVEN,
CONFIG_FB_MATROX_G450, CONFIG_FB_MATROX_MULTIHEAD, CONFIG_FB_ATY_CT,
CONFIG_FB_SIS_300, and CONFIG_FB_SIS_315 depend on CONFIG_EXPERIMENTAL
but do not say so
G'day,
As the symbol CONFIG_VISWS is used in 18 places, we might as well
give it a non-empty value.
diff -ruN linux-2.5.24+patches5/arch/i386/config.in linux-2.5.24/arch/i386/config.in
--- linux-2.5.24+patches5/arch/i386/config.in Sun Jun 30 20:27:22 2002
+++ linux-2.5.24/arch/i386/config.in
Tom Rini wrote:
On Sun, Jun 30, 2002 at 08:15:55PM +1000, Greg Banks wrote:
G'day,
1/3 definitions of CONFIG_BLK_DEV_FD have trivially different banners.
[Rusty: this is the one davem didn't like, rejigged to remove PC
from one case instead of add it to the other 2].
Ick
Sam Ravnborg wrote:
On Fri, Jun 28, 2002 at 05:42:53PM +1000, Greg Banks wrote:
[...] kbuild-2.5 does not replace something simple with
something complex, instead it replaces something complex and broken with
something of greater complexity and not broken. [...]
About current kbuild
Sam Ravnborg wrote:
Every CML program
-
There are 3 CML programs within the kernel tree (Configure, menuconfig
and xconfig). To me the best thing that could happen was that they
disappeared, being replaced by a single config tool - that provided
the same type of
G'day,
1/3 definitions of CONFIG_BLK_DEV_FD have trivially different banners.
[Rusty: this is the one davem didn't like, rejigged to remove PC
from one case instead of add it to the other 2].
diff -ruN linux-2.5.24+patches4/drivers/block/Config.in
linux-2.5.24/drivers/block/Config.in
---
Some CML1 rule contributors seem to think that the bool statement
takes a third argument which is the default value. It doesn't.
diff -ruN linux-2.5.24+patches4/arch/ia64/config.in linux-2.5.24/arch/ia64/config.in
--- linux-2.5.24+patches4/arch/ia64/config.in Sun Jun 30 19:45:22 2002
+++
Some CML1 rule contributors seem to think that the bool statement
takes a third argument which is the default value. It doesn't.
diff -ruN linux-2.5.24+patches4/arch/sh/config.in linux-2.5.24/arch/sh/config.in
--- linux-2.5.24+patches4/arch/sh/config.in Sun Jun 30 19:45:23 2002
+++
Some instances of the bool statement have what appear to be
dependencies like dep_bool after the 2nd argument, which are
silently ignored by all current parsers. I have either trimmed
the arguments or converted the bool to dep_bool as seemed
appropriate.
diff -ruN
Some instances of the bool statement have what appear to be
dependencies like dep_bool after the 2nd argument, which are
silently ignored by all current parsers. I have either trimmed
the arguments or converted the bool to dep_bool as seemed
appropriate.
diff -ruN
The convention is that symbols that depend on $CONFIG_EXPERIMENTAL are
marked in the banner with the string (EXPERIMENTAL). There are some
cases where that string is correctly used but is Capitalised instead of
uppercase.
diff -ruN linux-2.5.24+patches4/drivers/net/irda/Config.in
G'day,
I'll just briefly unlurk on the subject of kbuild before getting back
to the kconfig bughunt.
Sam Ravnborg wrote:
On Mon, Jun 24, 2002 at 08:49:34AM +1000, Keith Owens wrote:
[...]
There is absolutely no requirement that all kernel developers uses
the same SCM system.
Agreed.
Sam Ravnborg wrote:
On Wed, Jun 26, 2002 at 12:36:11AM +1000, Greg Banks wrote:
I think the problem of Makefile bits in shadow trees is really
quite difficult. Keith's solution of pre-processing Makefiles and
Makefile.appends from all the shadow trees into a combined Makefile
doesn't
G'day,
A couple of people have asked me how I'm finding all the kconfig
problems for which I've been submitting trivial patches, so I thought
I'd post a few words about the tool I'm using.
I've written a CML1 parsing backend for gcml2, my C implementation
of CML2. Getting a bison parser to
Three symbols CONFIG_SCSI_CUMANA_1, CONFIG_SCSI_ECOSCSI, and CONFIG_SCSI_OAK1
depend on CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.21+patches3/drivers/acorn/scsi/Config.in
linux-2.5.21/drivers/acorn/scsi/Config.in
---
Use of the $ARCH variable is undocumented; the alpha port defines the
bool constant CONFIG_ALPHA for this purpose.
diff -ruN linux-2.5.21+trivial/drivers/char/ftape/Config.in
linux-2.5.21/drivers/char/ftape/Config.in
--- linux-2.5.21+trivial/drivers/char/ftape/Config.in Wed Jun 12 17:34:51
Use of the $ARCH variable is undocumented; the alpha port defines the
bool constant CONFIG_ALPHA for this purpose.
diff -ruN linux-2.5.21+trivial/fs/partitions/Config.in
linux-2.5.21/fs/partitions/Config.in
--- linux-2.5.21+trivial/fs/partitions/Config.inWed Jun 12 17:34:51 2002
+++
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
diff -ruN linux-2.5.21+trivial/drivers/fc4/Config.in linux-2.5.21/drivers/fc4/Config.in
---
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
diff -ruN linux-2.5.21+trivial/drivers/sbus/char/Config.in
linux-2.5.21/drivers/sbus/char/Config.in
---
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
diff -ruN linux-2.5.21+trivial/drivers/video/Config.in
linux-2.5.21/drivers/video/Config.in
---
The default value specified as the last word of the choice statement
should be a unique abbreviation of one of the sub-prompts. Using one
of the sub-symbols is not legal. Fix 'Nino Model Number'.
[Rusty: this is 2/3 partial resends of 'PATCH: kconfig choice defaults (1/2)']
diff -ruN
The default value specified as the last word of the choice statement
should be a unique abbreviation of one of the sub-prompts. Using one
of the sub-symbols is not legal. Fix 'Type of PHY'.
[Rusty: this is 3/3 partial resends of 'PATCH: kconfig choice defaults (1/2)']
diff -ruN
Symbol CONFIG_SOFTWARE_SUSPEND depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches3/drivers/video/Config.in
linux-2.5.21/drivers/video/Config.in
--- linux-2.5.21+patches3/drivers/video/Config.in Sun Jun 16 14:15:27 2002
+++
G'day,
The word EXPERIMENTAL in the banner for symbol CONFIG_HPT34X_AUTODMA
was almost spelled right.
diff -ruN linux-2.5.21+patches2/drivers/ide/Config.in
linux-2.5.21/drivers/ide/Config.in
--- linux-2.5.21+patches2/drivers/ide/Config.in Sun Jun 16 14:13:21 2002
+++
G'day,
The arch-determining symbol CONFIG_SH in drivers/mtd/maps/Config.in
should be CONFIG_SUPERH.
(sigh, I patched the line above this a few days ago and missed this).
diff -ruN linux-2.5.21+patches2/drivers/mtd/maps/Config.in
linux-2.5.21/drivers/mtd/maps/Config.in
---
G'day,
Symbol CONFIG_ZNET depends on CONFIG_OBSOLETE, but its banner says it
depends on CONFIG_EXPERIMENTAL.
diff -ruN linux-2.5.21+patches2/drivers/net/Config.in
linux-2.5.21/drivers/net/Config.in
--- linux-2.5.21+patches2/drivers/net/Config.in Sun Jun 16 14:13:20 2002
+++
G'day,
Symbol CONFIG_FMV18X depends on CONFIG_OBSOLETE but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/net/Config.in
linux-2.5.21/drivers/net/Config.in
--- linux-2.5.21+patches2/drivers/net/Config.in Sun Jun 16 14:13:20 2002
+++ linux-2.5.21/drivers/net/Config.in
G'day,
Ok, this time I'll send the right patch.
Symbol CONFIG_H8 depends on CONFIG_OBSOLETE but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/char/Config.in
linux-2.5.21/drivers/char/Config.in
--- linux-2.5.21+patches2/drivers/char/Config.inSun Jun 16
G'day,
Symbol CONFIG_SK_G16 depends on CONFIG_OBSOLETE but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/net/Config.in
linux-2.5.21/drivers/net/Config.in
--- linux-2.5.21+patches2/drivers/net/Config.in Sun Jun 16 14:13:20 2002
+++ linux-2.5.21/drivers/net/Config.in
G'day,
Symbol CONFIG_CYCLOMX_X25 depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/net/wan/Config.in
linux-2.5.21/drivers/net/wan/Config.in
--- linux-2.5.21+patches2/drivers/net/wan/Config.in Sun Jun 16 14:15:16 2002
+++
G'day,
Two symbols CONFIG_PLX_HERMES and CONFIG_PCI_HERMES depend on
CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.21+patches2/drivers/net/wireless/Config.in
linux-2.5.21/drivers/net/wireless/Config.in
--- linux-2.5.21+patches2/drivers/net/wireless/Config.in
G'day,
Three symbols CONFIG_BLK_DEV_ATARAID, CONFIG_BLK_DEV_ATARAID_PDC, and
CONFIG_BLK_DEV_ATARAID_HPT depend on CONFIG_EXPERIMENTAL but do
not say so in their banners.
diff -ruN linux-2.5.21+patches2/drivers/ide/Config.in
linux-2.5.21/drivers/ide/Config.in
---
G'day,
Symbol CONFIG_ISDN_DRV_TPAM depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/isdn/tpam/Config.in
linux-2.5.21/drivers/isdn/tpam/Config.in
--- linux-2.5.21+patches2/drivers/isdn/tpam/Config.in Sun Jun 16 14:13:21 2002
+++
G'day,
Symbol CONFIG_JFFS2_FS_NAND depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/fs/Config.in linux-2.5.21/fs/Config.in
--- linux-2.5.21+patches2/fs/Config.in Sun Jun 16 14:13:21 2002
+++ linux-2.5.21/fs/Config.in Sun Jun 16 15:00:25 2002
G'day,
Symbol CONFIG_LDM_PARTITION depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/fs/partitions/Config.in
linux-2.5.21/fs/partitions/Config.in
--- linux-2.5.21+patches2/fs/partitions/Config.in Sun Jun 16 14:15:16 2002
+++
G'day,
Symbol CONFIG_MIDI_EMU10K1 depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/sound/oss/Config.in linux-2.5.21/sound/oss/Config.in
--- linux-2.5.21+patches2/sound/oss/Config.in Sun Jun 16 14:13:21 2002
+++ linux-2.5.21/sound/oss/Config.in
G'day,
Two symbols CONFIG_ROADRUNNER and CONFIG_ROADRUNNER_LARGE_RINGS depend
on CONFIG_EXPERIMENTAL but do not say so in their banners.
diff -ruN linux-2.5.21+patches2/drivers/net/Config.in
linux-2.5.21/drivers/net/Config.in
--- linux-2.5.21+patches2/drivers/net/Config.in Sun Jun 16 14:13:20
G'day,
Symbol CONFIG_SONYPI depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/char/Config.in
linux-2.5.21/drivers/char/Config.in
--- linux-2.5.21+patches2/drivers/char/Config.inSun Jun 16 14:15:16 2002
+++
G'day,
Symbol CONFIG_SOUND_RME96XX depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/sound/oss/Config.in linux-2.5.21/sound/oss/Config.in
--- linux-2.5.21+patches2/sound/oss/Config.in Sun Jun 16 14:13:21 2002
+++ linux-2.5.21/sound/oss/Config.in
G'day,
Symbol CONFIG_VIDEO_MEYE depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.
diff -ruN linux-2.5.21+patches2/drivers/media/video/Config.in
linux-2.5.21/drivers/media/video/Config.in
--- linux-2.5.21+patches2/drivers/media/video/Config.in Sun Jun 16 14:13:20 2002
+++
G'day,
The convention is that symbols that depend on $CONFIG_EXPERIMENTAL are
marked in the banner with the string (EXPERIMENTAL). There are 4 cases
where that string is correctly used but is lowercase instead of uppercase.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/arm/config.in
G'day,
1/3 definitions of 64-bit CONFIG_BINFMT_ELF have trivially different banners.
1/3 definitions of CONFIG_BINFMT_ELF32 have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/ppc64/config.in
linux-2.5.21/arch/ppc64/config.in
---
G'day,
1/2 definitions of CONFIG_NUMA have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/mips64/config.in
linux-2.5.21/arch/mips64/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/mips64/config.inWed Jun 12 17:50:30
2002
+++
G'day,
1/5 definitions of CONFIG_PREEMPT have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/sparc64/config.in
linux-2.5.21/arch/sparc64/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/sparc64/config.in Wed Jun 12 17:50:30
2002
+++
G'day,
1/3 definitions of CONFIG_PSMOUSE have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/mips/config.in
linux-2.5.21/arch/mips/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/mips/config.in Wed Jun 12 17:50:30 2002
+++ linux-2.5.21/arch/mips/config.inWed
G'day,
1/17 definitions of CONFIG_SCSI have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/arm/config.in
linux-2.5.21/arch/arm/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/arm/config.in Wed Jun 12 17:50:30 2002
+++ linux-2.5.21/arch/arm/config.in Fri Jun
G'day,
2/4 definitions of CONFIG_SOFT_WATCHDOG have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/m68k/config.in
linux-2.5.21/arch/m68k/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/m68k/config.in Wed Jun 12 17:50:30 2002
+++ linux-2.5.21/arch/m68k/config.in
G'day,
1/14 definitions of CONFIG_SOUND have trivially different banners.
diff -ruN linux-2.5.21+trivial+arch+cerf/arch/arm/config.in
linux-2.5.21/arch/arm/config.in
--- linux-2.5.21+trivial+arch+cerf/arch/arm/config.in Wed Jun 12 17:50:30 2002
+++ linux-2.5.21/arch/arm/config.in Fri
G'day,
The config language is *not* shell. The construct [ foo ] || [ bar ]
is legal in shell but not in the config language, where we should use
the equivalent [ foo -o bar ]
diff -ruN linux-2.5.20-orig/arch/ia64/config.in linux-2.5.20/arch/ia64/config.in
---
G'day,
The format for the choice statement is:
choice 'prompt' {sub-prompt sub-symbol}* default-value
and the following is *not* legal config language (note the
positioning of the closing double quote):
choice 'prompt' {sub-prompt sub-symbol}* default-value
It only happens to work because of
G'day,
Two symbols used in drivers/net/wan/Config.in are misspelled.
CONFIG_PPP_MULTLINK should be CONFIG_PPP_MULTILINK
CONFIG_PPP_SYNCTTY should be CONFIG_PPP_SYNC_TTY
diff -ruN linux-2.5.20-orig/drivers/net/wan/Config.in
linux-2.5.20/drivers/net/wan/Config.in
---
G'day,
The config language is *not* shell. Sprinkling around stray semicolons is
legal in shell but not in the config language.
diff -ruN linux-2.5.20-orig/drivers/s390/Config.in
linux-2.5.20-test/drivers/s390/Config.in
--- linux-2.5.20-orig/drivers/s390/Config.inWed Jun 12 02:07:13 2002
G'day,
Removed a spurious menu definition which was both a duplicate and
had no matching endmenu.
diff -ruN linux-2.5.20-orig/arch/ppc/8260_io/Config.in
linux-2.5.20/arch/ppc/8260_io/Config.in
--- linux-2.5.20-orig/arch/ppc/8260_io/Config.inMon Apr 15 05:18:43 2002
+++
G'day,
Here's the SuperH patches for kbuild-2.5 upgraded to 2.3 (kernel 2.5.12).
There's no functional change except that 2.5.12 is even less broken
so the hacks patch is gone.
I'll update to 2.4 (2.5.13) sometime after 2.5.13 is merged into LinuxSH.
Greg.
--
the price of civilisation today
G'day,
Here's the SuperH patches for kbuild-2.5 upgraded to 2.2 (kernel 2.5.10).
There's no functional change except that 2.5.10 is slightly less broken
than 2.5.8 so the hacks patch is smaller.
I just noticed that 2.3 is out...sigh if I'd started an hour earlier
perhaps this message wouldn't
G'day,
Here's the patches to support the SuperH architecture in kbuild 2.5.
The patches are against kbuild-2.5 2.1 (Linux 2.5.8). See the README
for details. I'll start work on upgrading to kbuild-2.5 (Linux 2.5.10)
in the next couple of days.
Remaining issues:
* I can't figure out if
Keith Owens wrote:
Here's the patches to support the SuperH architecture in kbuild 2.5.
kbuild-2.5-core-8 would be better, it has a couple of bug fixes from -6.
Coming up in the next few days.
While we're here, can you shed some light on this issue?
If I apply the SuperH kbuild patch to
1 - 100 of 111 matches
Mail list logo
