Ah... I see what happened. CONFIG_USB_STORAGE must depend on CONFIG_SCSI.
That is, if CONFIG_SCSI=m, then CONFIG_USB_STORAGE must be either n or m.
If CONFIG_SCSI is y, then CONFIG_USB_STORAGE may be either y, n, or m. If
CONFIG_SCSI is n, then CONFIG_USB_STORAGE must be n.
Basically, the restrictions in Config.in were relaxed too much.
Matt Dharm
On Fri, May 19, 2000 at 07:35:32AM -0700, Dunlap, Randy wrote:
> Yep, I broke it. This didn't even cross my mind.
>
> Matthew D., can you tell me/us what CONFIG_USB_STORAGE
> needs to be dependent upon when building in-kernel?
>
> Is it $CONFIG_BLK_DEV_IDESCSI or $CONFIG_BLK_DEV_SD
> or $CONFIG_SCSI or $CONFIG_CHR_DEV_SG (generic) or
> <some of these OR-ed together>?
>
> Thanks,
> Randy
>
>
> > drivers/usb/usbdrv.o: In function `us_detect':
> > drivers/usb/usbdrv.o(.text+0xdb43): undefined reference to
> > `scsi_register'
> > drivers/usb/usbdrv.o: In function `storage_probe':
> > drivers/usb/usbdrv.o(.text+0xf5cb): undefined reference to
> > `scsi_register_module'
> >
> > CONFIG_BLK_DEV_IDESCSI=m
> > CONFIG_SCSI=m
> > CONFIG_BLK_DEV_SD=m
> > CONFIG_SD_EXTRA_DEVS=40
> > CONFIG_USB=y
> > CONFIG_USB_DEBUG=y
> > CONFIG_USB_DEVICEFS=y
> > CONFIG_USB_UHCI=m
> > CONFIG_USB_UHCI_ALT=m
> > CONFIG_USB_OHCI=y
> > CONFIG_USB_SCANNER=y
> > CONFIG_USB_STORAGE=y
> > CONFIG_USB_STORAGE_DEBUG=y
> > CONFIG_USB_HID=m
> > CONFIG_INPUT_KEYBDEV=y
> > CONFIG_INPUT_MOUSEDEV=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> > CONFIG_INPUT_EVDEV=y
--
Matthew Dharm Home: [EMAIL PROTECTED]
Senior Engineer, QCP Inc. Work: [EMAIL PROTECTED]
C: Like the Furby?
DP: He gives me the creeps. Think the SPCA will take him?
-- Cobb and Dust Puppy
User Friendly, 1/2/1999
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
