Skip to contentSkip to conversation

no modules :-)

DISCUSSION James 3 participants 3 messages Sep 25, 2010 – Sep 26, 2010

lore
Share & tools
lore

James

author
#0 lore raw

I don't like modules. :-)

What is pulling this in:

CONFIG_SCSI_WAIT_SCAN=m

I edited .config but make must have turned it back on.

#1 lore raw
Quoted 8 lines · On Sat, 25 Sep 2010 01:10:50 -0400 James wrote:

I don't like modules. :-)

What is pulling this in:

CONFIG_SCSI_WAIT_SCAN=m

I edited .config but make must have turned it back on. --

If you have SCSI enabled and MODULES enabled, this kconfig symbol will be enabled (=m) automatically. From drivers/scsi/Kconfig (with # comments):

config SCSI_WAIT_SCAN
tristate # No prompt here, this is an invisible symbol. default m
depends on SCSI
depends on MODULES

# scsi_wait_scan is a loadable module which waits until all the async scans are
# complete.  The idea is to use it in initrd/ initramfs scripts.  You modprobe
# it after all the modprobes of the root SCSI drivers and it will wait until
# they have all finished scanning their buses before allowing the boot to
# proceed.  (This method is not applicable if targets boot independently in
# parallel with the initiator, or with transports with non-deterministic target
# discovery schemes, or if a transport driver does not support scsi_wait_scan.)
#
# This symbol is not exposed as a prompt because little is to be gained by
# disabling it, whereas people who accidentally switch it off may wonder why
# their mkinitrd gets into trouble.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

#2 lore raw
In reply to James
Quoted 5 lines · James

I don't like modules. :-)

What is pulling this in:

CONFIG_SCSI_WAIT_SCAN=m

Disable modules and it will disappear. I believe it is related to CONFIG_SCSI_SCAN_ASYNC but take a look at commit 5e2fb917920c62c5ad260962471aeb578b52ac40 for some more details too...

Signature · 1 line
Sitsofe | http://sucs.org/~sits/