Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: linux-mips@linux-mips.org
Subject: more MIPS-related config variable issues, just FYI
Date: Fri, 25 Jul 2008 18:01:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807251758560.4566@localhost.localdomain> (raw)


  first, what i call "badref" config variables -- tests on what should
be config variables that are, in fact, not defined in any Kconfig
file:

>>>>> EXCITE_FCAP_GPI
arch/mips/basler/excite/excite_device.c:164:#if defined(CONFIG_EXCITE_FCAP_GPI) || defined(CONFIG_EXCITE_FCAP_GPI_MODULE)
arch/mips/basler/excite/excite_device.c:227:#endif /* defined(CONFIG_EXCITE_FCAP_GPI) || defined(CONFIG_EXCITE_FCAP_GPI_MODULE) */
>>>>> HT_LEVEL_TRIGGER
arch/mips/pmc-sierra/yosemite/irq.c:80:#ifdef CONFIG_HT_LEVEL_TRIGGER
arch/mips/pmc-sierra/yosemite/irq.c:109:#endif /* CONFIG_HT_LEVEL_TRIGGER */
>>>>> PCMCIA_XXS1500
arch/mips/au1000/xxs1500/board_setup.c:55:#ifdef CONFIG_PCMCIA_XXS1500
>>>>> PMCTWILED
arch/mips/pmc-sierra/msp71xx/msp_setup.c:233:#ifdef CONFIG_PMCTWILED
arch/mips/pmc-sierra/msp71xx/msp_hwbutton.c:35:#ifdef CONFIG_PMCTWILED
arch/mips/pmc-sierra/msp71xx/msp_hwbutton.c:85:#ifdef CONFIG_PMCTWILED
arch/mips/pmc-sierra/msp71xx/msp_hwbutton.c:97:#ifdef CONFIG_PMCTWILED
arch/mips/configs/msp71xx_defconfig:934:CONFIG_PMCTWILED=y
>>>>> RM9K_GE
arch/mips/basler/excite/excite_device.c:314:#if defined(CONFIG_RM9K_GE) || defined(CONFIG_RM9K_GE_MODULE)
arch/mips/basler/excite/excite_device.c:367:#endif /* defined(CONFIG_RM9K_GE) || defined(CONFIG_RM9K_GE_MODULE) */
>>>>> SIBYTE_BCM1480_PROF
arch/mips/sibyte/bcm1480/irq.c:445:#ifdef CONFIG_SIBYTE_BCM1480_PROF
arch/mips/sibyte/bcm1480/irq.c:452:#ifdef CONFIG_SIBYTE_BCM1480_PROF
>>>>> SOC_AU1000_FREQUENCY
arch/mips/au1000/common/time.c:202:#ifdef CONFIG_SOC_AU1000_FREQUENCY
arch/mips/au1000/common/time.c:203:		cpu_speed = CONFIG_SOC_AU1000_FREQUENCY;
arch/mips/au1000/common/setup.c:59:#ifdef CONFIG_SOC_AU1000_FREQUENCY
arch/mips/au1000/common/setup.c:60:		cpufreq = CONFIG_SOC_AU1000_FREQUENCY / 1000000;
>>>>> SOUND_AU1X00
arch/mips/au1000/common/setup.c:101:#if defined(CONFIG_SOUND_AU1X00) && !defined(CONFIG_SOC_AU1000)
>>>>> SQUASHFS
arch/powerpc/configs/ppc6xx_defconfig:2962:CONFIG_SQUASHFS=m
arch/mips/pmc-sierra/msp71xx/msp_prom.c:46:#ifdef CONFIG_SQUASHFS
arch/mips/pmc-sierra/msp71xx/msp_prom.c:552:#ifdef CONFIG_SQUASHFS
arch/mips/configs/msp71xx_defconfig:1300:CONFIG_SQUASHFS=y
arch/mips/pmc-sierra/msp71xx/msp_prom.c:554:		/* Get SQUASHFS size */

  and, additionally, "badref" config variables that occur solely in
Makefiles:

===== MSPETH =====
./arch/mips/pmc-sierra/msp71xx/Makefile:obj-$(CONFIG_MSPETH) += msp_eth.o
===== USB_MSP71XX =====
./arch/mips/pmc-sierra/msp71xx/Makefile:obj-$(CONFIG_USB_MSP71XX) += msp_usb.o

  whether any of the above is an issue is entirely up to you.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

                 reply	other threads:[~2008-07-25 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.10.0807251758560.4566@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox