Re: [regression] build failure with staging driver winbond phy

[Martin Steigerwald]

Am Thursday 17 February 2011 schrieb Martin Steigerwald:
> Hi!
> 
> linux-2.6 as of ee715087024b91a6ceb85ba2d02f6c35d354a48c.
> 
> martin@shambhala:~/Computer/Shambhala/Kernel/2.6.38/linux-2.6> LANG=C
> make-kpkg --append-to-version -tp42 --revision 1 --initrd --rootcmd
> fakeroot linux_{image,doc,headers,source}
> [...]
> Root device is (253, 0)
> Setup is 13724 bytes (padded to 13824 bytes).
> System is 2763 kB
> CRC 115d526c
> Kernel: arch/x86/boot/bzImage is ready  (#3)
> make[1]: Leaving directory
> `/home/martin/Computer/Shambhala/Kernel/2.6.38/linux-2.6'
> /usr/bin/make  EXTRAVERSION=-rc5-tp42  ARCH=i386 \
>                              modules
> make[1]: Entering directory
> `/home/martin/Computer/Shambhala/Kernel/2.6.38/linux-2.6'
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CC [M]  drivers/staging/winbond/phy_calibration.o
> drivers/staging/winbond/phy_calibration.c: In function
> '_tx_iq_calibration_winbond':
> drivers/staging/winbond/phy_calibration.c:986: error: implicit
> declaration of function 'msleep'
> drivers/staging/winbond/phy_calibration.c: In function
> 'adjust_TXVGA_for_iq_mag':
> drivers/staging/winbond/phy_calibration.c:1555: error: implicit
> declaration of function 'udelay'
> make[4]: *** [drivers/staging/winbond/phy_calibration.o] Error 1
> make[3]: *** [drivers/staging/winbond] Error 2
> make[2]: *** [drivers/staging] Error 2
> make[1]: *** [drivers] Error 2
> make[1]: Leaving directory
> `/home/martin/Computer/Shambhala/Kernel/2.6.38/linux-2.6'
> make: *** [debian/stamp/build/kernel] Error 2
> 
> I already disabled CONFIG_IR_WINBOND_CIR, but it doesn't seem to help:
> 
> martin@shambhala:~/Computer/Shambhala/Kernel/2.6.38/linux-2.6> grep
> "WIN.*BOND" .config
> # CONFIG_PATA_WINBOND is not set
> # CONFIG_PATA_WINBOND_VLB is not set
> # CONFIG_IR_WINBOND_CIR is not set
> 
> Any advice on which kernel option to disable in order to build this
> again?
> 
> No problem with 2.6.37, but maybe it didn't have this driver.

Ping. Anyone who has a hint? My only idea for now is to exclude all 
stagings drivers from being build

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Attachment: signature.asc
Description: This is a digitally signed message part.