DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
dandon has quit [Remote host closed the connection]
Textmode has joined #qi-hardware
_whitelogger has joined #qi-hardware
_whitelogger has joined #qi-hardware
pcercuei has quit [Ping timeout: 264 seconds]
kyak has quit [Read error: Operation timed out]
wolfspraul has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
lindi-_ is now known as lindi-
wej_ has joined #qi-hardware
wej has quit [Ping timeout: 245 seconds]
kyak has joined #qi-hardware
jekhor has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
wej_ has quit [Read error: Connection reset by peer]
wej has joined #qi-hardware
ffio has joined #qi-hardware
dandon has joined #qi-hardware
wej has quit [Ping timeout: 264 seconds]
panda|x201 has quit [Remote host closed the connection]
wej has joined #qi-hardware
panda|x201 has joined #qi-hardware
freespace has quit [*.net *.split]
rozzin has quit [*.net *.split]
freespace has joined #qi-hardware
rozzin has joined #qi-hardware
panda|x201 has quit [Quit: Leaving]
panda|x201 has joined #qi-hardware
rz2k has joined #qi-hardware
lekernel has joined #qi-hardware
porchao has joined #qi-hardware
jekhor has quit [Ping timeout: 276 seconds]
wolfspraul has quit [Ping timeout: 245 seconds]
wolfspraul has joined #qi-hardware
ffio_ has joined #qi-hardware
ffio has quit [Ping timeout: 248 seconds]
pcercuei has joined #qi-hardware
Textmode has quit [Quit: Ex-Chat]
lekernel has quit [Read error: Operation timed out]
lekernel has joined #qi-hardware
FDCX has joined #qi-hardware
viric_ has joined #qi-hardware
jekhor has joined #qi-hardware
viric_ has quit [Ping timeout: 240 seconds]
jekhor has quit [Ping timeout: 264 seconds]
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 268 seconds]
wej has quit [Ping timeout: 245 seconds]
viric_ has joined #qi-hardware
Freemor has quit [Remote host closed the connection]
jekhor has joined #qi-hardware
viric_ is now known as viric
Freemor has joined #qi-hardware
jekhor has quit [Read error: Connection reset by peer]
kilae has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]]
wej has joined #qi-hardware
_ffio_ has joined #qi-hardware
ffio_ has quit [Ping timeout: 264 seconds]
rz2k has quit []
<apelete> Hello
<apelete> larsc: are you there ?
<larsc> yes
<apelete> Hi
<larsc> hi
<apelete> I'm trying to test the musb glue layer skeleton I' ve written: http://seketeli.fr/git/~apelete/qi-kernel.git/commit/?h=jz4740-udc
<apelete> when I load it nothing happens
<larsc> did you create a platform device for it in qi_lb60.c?
<apelete> no, should I ?
<larsc> yes, or better just change the name of the jzudc device
<larsc> in arch/mips/jz4740/platform.c
<apelete> I don't get it. qi_lb60.c seems to be asoc related, why should I create a platform device there ?
<larsc> board-qi_lb60.c, sorry
<apelete> in board-qi_lb60.c, I found:
<apelete> static struct platform_device *jz_platform_devices[] __initdata = {
<apelete> &jz4740_udc_device,
<apelete> which correspond to the following in arch/mips/jz4740/platform.c:
<apelete> struct platform_device jz4740_udc_device = {
<apelete> .name= "jz-udc",
<apelete>
<larsc> yes, replace "jz-udc" with "musb-jz4740"
<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
<DocScrutinizer05> might be wrong though
lekernel has quit [Quit: Leaving]
<DocScrutinizer05> http://processors.wiki.ti.com/index.php/Category:DaVinci_Linux looks actually not too bad
pcercuei has quit [Ping timeout: 240 seconds]
pcercuei has joined #qi-hardware
Textmode has joined #qi-hardware
<mth> apelete: we've got a JZ4770 kernel here that uses the musb driver: https://github.com/gcwnow/linux
<mth> the 4770 version can do OTG, which I guess the 4740 version cannot, so it's probably not exactly the same
<mth> the glue is slightly cleaned up compared to Ingenic's code, but it's not great yet
<mth> it does work reliably though