pcercuei has quit [Read error: Connection reset by peer]
wolfspraul has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
kristianpaul has quit [Ping timeout: 240 seconds]
kristianpaul has joined #qi-hardware
kristianpaul has joined #qi-hardware
viric has joined #qi-hardware
wpwrak has joined #qi-hardware
kanzure_ has joined #qi-hardware
kanzure_ has quit [Client Quit]
kristianpaul has quit [Ping timeout: 246 seconds]
kristianpaul has joined #qi-hardware
kristianpaul has quit [Ping timeout: 246 seconds]
kristianpaul has joined #qi-hardware
kristianpaul has joined #qi-hardware
<wpwrak>
hmm, seems that the new USB connector will only reach me next week :( looks as if fedex have either reduced their flight frequency to argentina or the plane has a new schedule, missing the latest drop from digi-key
kristianpaul has quit [Ping timeout: 240 seconds]
FDCX has quit [Read error: Connection reset by peer]
FDCX has joined #qi-hardware
dos1 has quit [Quit: Kabum!]
dos1 has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
FDCX has quit [Read error: Operation timed out]
FDCX has joined #qi-hardware
FDCX has quit [Remote host closed the connection]
wej has quit [Ping timeout: 264 seconds]
rz2k has quit []
kristianpaul has joined #qi-hardware
wej has joined #qi-hardware
FDCX has joined #qi-hardware
Jay7 has quit [Ping timeout: 260 seconds]
porchaso0 has quit [Read error: Connection reset by peer]
viric has quit [Ping timeout: 240 seconds]
porchao has joined #qi-hardware
Jay7 has joined #qi-hardware
viric has joined #qi-hardware
<apelete>
Hello
<apelete>
mth: are you there ?
<apelete>
mth: still debugging the musb driver for jz4740, I added a check to make the probe fail on !pdata like you suggested
<apelete>
(I guess I should push these into git anyway, even if it's not working yet...)
<apelete>
mth: ah, I see, I also need to have a "static struct musb_hdrc_config" and "static struct musb_hdrc_platform_data" in order to define "struct platform_device jz4740_whatever", isn't that so ?
<mth>
yes, and an associated struct platform_device as well
<mth>
the name of the platform device should match the name of your driver
Jay7 has quit [Read error: Operation timed out]
<apelete>
mth: ok. where do I find all the data to fill these struct members ?
<apelete>
I guess I need some sort of detailed datasheet...
Jay7 has joined #qi-hardware
wolfspraul has quit [Quit: leaving]
viric has quit [Remote host closed the connection]
viric has joined #qi-hardware
<apelete>
time to get some sleep (12:30 AM here in france)
<apelete>
mth: thanks for your time and insight, will let you know how it goes