<apelete>
okay, so I don't need to modifiy drivers/usb/musb/Makefile and drivers/usb/musb/Kconfig to add rules for musb-jz4740 ?
<apelete>
because all the musb glue layers seem to have some sort of configuration options in those latter files
<apelete>
and they (the other musb glue layers) all depend on the USB_MUSB_HDRC kernel config parameter
<apelete>
I compiled musb-jz4740 out of tree and loaded it, but nothing happened. so I think I'm missing the corresponding USB_MUSB_HDRC driver in the kernel: I think musb-jz4740 should be used by USB_MUSB_HDRC driver
<apelete>
larsc: am I mistaking here ?
<larsc>
yes, you need to load the musb module as well
pcercuei has quit [Read error: Operation timed out]
<apelete>
ok. so I need to modify drivers/usb/musb/Makefile and drivers/usb/musb/Kconfig as well, because the musb module cannot be activated in the menuconfig without a platform glue layer
<apelete>
larsc: I do not know what to put in the drivers/usb/musb/Kconfig for musb-jz4740 exactly, I explain:
<apelete>
let's take for instance the platform glue layer config section of a TI controller in drivers/usb/musb/Makefile and drivers/usb/musb/Kconfig:
<apelete>
choice
<apelete>
<apelete>
prompt "Platform Glue Layer"
<apelete>
config USB_MUSB_DAVINCI
<apelete>
tristate "DaVinci"
<apelete>
depends on ARCH_DAVINCI_DMx
<apelete>
<apelete>
<apelete>
larsc: it depends on ARCH_DAVINCI_DMx. what should musb-jz4740 depends on ?
<apelete>
I'm thinking of something like ARCH_MIPS maybe, but not sure about that
<apelete>
s/ config section of a TI controller in drivers/usb/musb/Makefile and drivers/usb/musb/Kconfig / config section of a TI controller indrivers/usb/musb/Kconfig /
pcercuei has joined #qi-hardware
jekhor has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
<larsc>
depends on MACH_JZ4740 should work
<apelete>
ok thanks
<apelete>
larsc: I won't bother you longer, will try those modifications first and see what happens :)
<apelete>
thanks a lot for your time
wolfspraul has quit [Quit: leaving]
<larsc>
no problem
_ffio_ has quit [Quit: WeeChat 0.4.1]
porchao has quit [Quit: Leaving...]
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
<DocScrutinizer05>
MUSB WAAAAAH!!!
<DocScrutinizer05>
don't tell me JZ4740 is using the fsckdup mentalgrafucks musb core
<DocScrutinizer05>
had my year of torture trying to fix stuff in drivers for that crap
<DocScrutinizer05>
ask PaulFertser what he thinks about musb-hdrc ;-P
<DocScrutinizer05>
ARCH_DAVINCI is OMAP36xx, no?
<DocScrutinizer05>
actually Nokia's idea of a OMAP36xx platform
<DocScrutinizer05>
afaik
<larsc>
davinci is davinci
<DocScrutinizer05>
anyway DAVINCI been the codename for the N9(50) prototypes at Nokia
<larsc>
they sometimes share IP cores between davinci and omap though
<DocScrutinizer05>
so what's the "top" meaning of davinci term? A SoC, a platform, a project, a son of flying spaghetti monster?
<larsc>
family of SoCs
<DocScrutinizer05>
mhm
<DocScrutinizer05>
thanks
<DocScrutinizer05>
right, I seem to recall something at TI's website