Skip to contentSkip to conversation

Some kconfig issues

DISCUSSION Jean-Luc Leger 3 participants 3 messages Dec 3, 2005 – Dec 5, 2005

lore
Share & tools
lore
#0 lore raw

Hi,

Here are some issues regarding undefined config options in linux-2.6.15-rc4. Most of these are obviously not yet defined config options, but as some are mispelled configs I thought it would be better to send the whole list.

Regards,

JL

---------------------------------------
FVR
from kernel/power/Kconfig:
config SOFTWARE_SUSPEND
bool "Software Suspend"
depends on PM && SWAP && (X86 && (!SMP || SUSPEND_SMP)) || ((FVR || PPC32) && !SMP)

440GR
from drivers/net/Kconfig:
config IBM_EMAC_PHY_RX_CLK_FIX
bool "PHY Rx clock workaround"
depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
-> maybe this is 440GP ?

IRTTY_OLD
from drivers/net/irda/Kconfig:
config DONGLE_OLD
bool "Old Serial dongle support"
depends on (IRTTY_OLD || IRPORT_SIR) && BROKEN_ON_SMP

NP405L
from drivers/net/Kconfig:
config IBM_EMAC_ZMII

        bool
        depends on IBM_EMAC && (NP405H || NP405L || 44x)
        default y

PALT_USRV
from drivers/serial/Kconfig:
config SERIAL_M32R_PLDSIO
bool "M32R SIO I/F on a PLD"
depends on SERIAL_M32R_SIO=y && (PLAT_OPSPUT || PALT_USRV || PLAT_M32700UT) default n
-> this is obviously PLAT_USRV

SPARC
from drivers/isdn/hisax/Kconfig
config HISAX_TELESPCI
bool "Teles PCI"
depends on PCI && (BROKEN || !(SPARC || PPC || PARISC || M68K))
-> is it SPARC32 || SPARC64 ?

NINO
from drivers/video/Kconfig
config FB_TX3912

        bool "TMPTX3912/PR31700 frame buffer support"
        depends on (FB = y) && NINO

VISWS
from drivers/video/Kconfig
config BUS_I2C

        bool
        depends on (FB = y) && VISWS
        default y

-> probably X86_VISWS

S390
from arch/h8300/Kconfig
config HW_CONSOLE

        bool
        depends on VT && !S390 && !UM
-> obviously useless in this file. UM too seems useless (or should be UML) 
from drivers/char/Kconfig
config HW_CONSOLE
        bool
        depends on VT && !S390 && !UML

from net/bluetooth/hidp/Kconfig
config BT_HIDP
tristate "HIDP protocol support" depends on BT && BT_L2CAP && (BROKEN || !S390)
-> probably ARCH_S390

And then, there are some from arch Kconfig files :

ARCH_NEXUSPCI in arch/arm/mm/Kconfig
ARCH_TBOX in arch/arm/mm/Kconfig
CPU_32v7 in arch/arm/mm/Kconfig
SA1100_PT_SYSTEM3 in arch/arm/Kconfig

H8002 in arch/h8300/Kconfig.cpu

GG2 in arch/m68k/Kconfig
PILOT5 in arch/m68knommu/Kconfig

ASH in arch/ppc/platforms/4xx/Kconfig and arch/powerpc/platforms/4xx/Kconfig CONFIG_PPC32 (should be PPC32) in arch/powerpc/Kconfig CONFIG_SMP (should be SMP) in arch/powerpc/Kconfig
VETH (is it ISERIES_VETH ?) in arch/powerpc/platforms/iseries/Kconfig

MPC1211 (is it SH_MPC1211 ?) in arch/sh/Kconfig

SPARC64_PAGE_SIZE_512K (should be SPARC64_PAGE_SIZE_512KB) in arch/sparc64/Kconfig

#1 lore raw

CONFIG_GG2 (was: Re: Some kconfig issues)

Quoted 5 lines · Jean-Luc Leger

Here are some issues regarding undefined config options in linux-2.6.15-rc4. Most of these are obviously not yet defined config options, but as some are mispelled configs I thought it would be better to send the whole list.

GG2 in arch/m68k/Kconfig

Indeed, Amiga Golden Gate II Zorro/ISA bridge support is only partially there, and cannot be selected.

Arno, do we still miss a lot?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

#2 lore raw

Re: CONFIG_GG2 (was: Re: Some kconfig issues)

Quoted 6 lines · Geert Uytterhoeven
Quoted 1 line

GG2 in arch/m68k/Kconfig

Indeed, Amiga Golden Gate II Zorro/ISA bridge support is only partially there, and cannot be selected.

Arno, do we still miss a lot?

No, not as far as I know.. I'll try to build 2.6 on my Amiga with the GG card soon and post the driver ont he list.

The 'driver' (if you can call it that) for the card pretty much does nothing anymore, just flip some bits on the card to enable it's interrupt forwarding and enabling or disabling the waitstates on the ISA BUS.

Because most i386/ISA drivers these days can handle shared/chained interrupt handlers like we always had on the m68k it's no longer needed to set up a secondary IRQ handling for the ISA drivers. (like I had to do for 2.2)

After that it's just a matter of some macro's for the byte-swapping of the ISA data and the address mangling for accessing the I/O and memory space.

Of course no DMA support and such, so no need to mess with that..

Bye, Arno.