ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
akazien has quit [Remote host closed the connection]
akazien has joined #linux-rockchip
akazien has quit [Ping timeout: 265 seconds]
naobsd has joined #linux-rockchip
akazien has joined #linux-rockchip
akazien has quit [Remote host closed the connection]
akazien has joined #linux-rockchip
<naobsd> hmm, Cortex-A7
<naobsd> oh, greate, RK3126 is pin-to-pin compat RKxx26
<naobsd> new gen low-end A7 dual/quad and high-end A17(A12?) quad family?
Astralix has joined #linux-rockchip
Astralix1 has quit [Ping timeout: 250 seconds]
GriefNorth has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
PaowZ_ has joined #linux-rockchip
mrcan has joined #linux-rockchip
mrcan has joined #linux-rockchip
<rperier> what is supposed to be the orange led on LAN8720A ? (the ethernet controller on marsboard and radxa)
<naobsd> rperier: link up? (just guessing, no confirmation)
<naobsd> maybe: link speed (10/100)
hipboi has quit [Ping timeout: 265 seconds]
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
hipboi has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
<rperier> naobsd: link up is the green led (on the left). It is powered on and does not blink, the orange led (on the right) is blinking all the time without transmission
<rperier> there is an issue somewhere but I don't understand why
<rperier> that's the same phy on rock and mars. on rock the orange led does not blink like that
<naobsd> ah
<naobsd> rperier: about orange on RR, are you sure that no packet inc. broadcast is arrived?
<naobsd> it seems "active" led on my RR ES, blinking is not constant
wildea01 has joined #linux-rockchip
<AstralixNB> good morning
<AstralixNB> rperier, die you just print the config registers of the phy? May be there is a bit set wrong?
<AstralixNB> die == did
<AstralixNB> And as there may have been changes on the clock tree, please check that the clock out of the RK SOC is set to real 50MHz and not 50.1 or 49.96MHz like mmind00 and I had it in the early times of clock tree.
<rperier> AstralixNB: not yet
<AstralixNB> I am not sure but I think you can request some of the PHX status registers by ip command... Or you just add some kprintf. But first of all check the clock tree.
<rperier> perhaps it has something to do with the clock yes...
<naobsd> rperier: did you see LAN8720A datasheet?
<rperier> yes, I did read that "it is link speed for 100mbps" ... did not help so much (perhaps I missed something). I only used the datasheet for rk3066 and for marsboard for now
AstralixNB1 has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
<naobsd> I cannot understand circuit well, but it seems LED is connected differently between RR and marsboard
mrcan_ has joined #linux-rockchip
<naobsd> ah, just pulled down...
mrcan has quit [Ping timeout: 244 seconds]
<hramrach_> what is the memory performance of the rk*26 chips? Anyone has any idea?
<hramrach_> do they have limited bus width or something compared to the 'full' chips?
naobsd has quit [Quit: Page closed]
<hramrach_> hmm, 3066 has 32bit memory interface according to datasheet
mrcan__ has joined #linux-rockchip
mrcan_ has quit [Ping timeout: 246 seconds]
mrcan_ has joined #linux-rockchip
mrcan__ has quit [Ping timeout: 255 seconds]
mrcan has joined #linux-rockchip
mrcan_ has quit [Ping timeout: 260 seconds]
Avasz has joined #linux-rockchip
Avasz has joined #linux-rockchip
bengal_ has joined #linux-rockchip
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-rockchip
bengal_ has quit [Ping timeout: 240 seconds]
Avasz has quit [Remote host closed the connection]
dlezcano has joined #linux-rockchip
<hramrach_> so 3166 might be nice cheap SoCs depending on the other components included
<hramrach_> ewh, wrong chips
<hramrach_> hmm, search for 3026 datasheet gives 3066 datasheet. Not a well known SoC then I guess
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
naobsd has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
hipboi has quit [Read error: Connection reset by peer]
nighty^ has joined #linux-rockchip
hipboi has joined #linux-rockchip
dlezcano has quit [Ping timeout: 260 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 260 seconds]
dlezcano has joined #linux-rockchip
<rperier> I am reading datasheet for lan8720a in details, I have probably missed something
<rperier> (I am a sw/system guy originally not an hw guy, so I still learn about this part)
<rperier> for now that's not too hard
VargaD_ has joined #linux-rockchip
bengal_ has joined #linux-rockchip
VargaD has quit [Ping timeout: 265 seconds]
VargaD_ is now known as VargaD
<AstralixNB1> rperier, I did some phy driver coding for other operating systems some time ago. If I can help, just ask
<AstralixNB1> but you're right, eth phy isn't that complicated.
AstralixNB1 has quit [Quit: Leaving.]
nighty^ has quit [Ping timeout: 272 seconds]
nighty^ has joined #linux-rockchip
bengal_ has quit [Quit: Leaving]
bengal has joined #linux-rockchip
phaedrus424 has joined #linux-rockchip
nighty^ has quit [Ping timeout: 272 seconds]
wildea01 has quit [Quit: leaving]
nighty^ has joined #linux-rockchip
<phaedrus424> Anyone up for a quick a RK3188 question?
<rperier> mhhh.... linux-next requires gcc >= 4.9 now... I will need to switch from "daisy" to "dizzy"... awesome v_V
<hramrach_> phaedrus424: you can possibly get an answer only if you ask the question
<Astralix1> hramrach_ good point
<phaedrus424> hramrach_: heh, fair point - was just checking to see if anyone was awake :)
<phaedrus424> I'm running an omegamoon 3.0.36 kernel on an MK902 right now, using it as a router, very stable and very happy with it
<Astralix1> phaedrus424: lot of people read backlog and answer later. So you should check this too
<phaedrus424> Astralix1: OK, thanks
<phaedrus424> I'm interesting in upgrading the kernel to something less ancient in the hope that I can get the onboard wireless working reliably in AP mode
<phaedrus424> Just wondering if anyone has suggestions about versions, repositories, etc. that would be worth a try
<Astralix1> If you only use it for server services, but no guy, you can try mainline
<phaedrus424> Astralix1: really? That would definitely make life easier ...
<Astralix1> rperier, do I read you correct? gcc 4.9 for linux-next?
akazien_ has joined #linux-rockchip
<Astralix1> the mainline isn't perfect and you should ask mmind00 or rperier which exact repo you should use. But I had my radxa rock running this kernel for quite a while.
<Astralix1> It is defintely not a copy, compile, flash job. You may need to setup your device tree corectly
akazien has quit [Ping timeout: 272 seconds]
dlezcano has quit [Remote host closed the connection]
<phaedrus424> Astralix1: OK, sounds like something of a project then, but I'll definitely look into it ..
<Astralix1> quptime
<Astralix1> ups... wrong keyboard ;)
akazien_ is now known as akaizen
<akaizen> anyone know how to compile the SDK for different wifi chips (android 4.4 kitkat)?
phaedrus424 has quit [Quit: Leaving]
TC has joined #linux-rockchip
TC is now known as phaedrus424
phaedrus424 has quit [Read error: Connection reset by peer]
<Astralix1> akaizen, there was sort of an auto-detection mechanism in RK WiFi drivers.
<akaizen> Astralix1: I'm using the Radxa 4.4 SDK and there is a wifi+bt.mk file which was modified to the correct broadcom chip, but wifi doesnt work through android but is working via terminal
<Astralix1> I has been a while since I was in that code but they start a driver from the USB or SDIO part to detect the chip, then export its name somwhere in /sys/
<akaizen> so it seems the correct driver is loaded by not passed to android
<Astralix1> With this export they then decice which radio binary and radio control file (.txt) must be loaded.
phaedrus424 has joined #linux-rockchip
<Astralix1> They use only one driver (wasn't it the broadcom ddriver?) to load ANY of the chips
<akaizen> oh, ive seen realtek, broadcom, rk
<Astralix1> So it doesn't matter if the driver is called broadcom, you must figure out if the binaries loaded to the radio are the right ones.
<Astralix1> The driver will even load an atheros binary to an atheros chip, even the driver itself is still named broadcom
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
phaedrus424 has quit [Read error: Connection reset by peer]
phaedrus424 has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
akaizen has joined #linux-rockchip
akaizen has quit [Read error: No route to host]
akaizen has joined #linux-rockchip
bengal has quit [Quit: Leaving]
arokux2 has joined #linux-rockchip
phaedrus424 has quit [Quit: Leaving]
nighty^ has quit [Quit: Disappears in a puff of smoke]
<akaizen> @Astralix1 - I think the right binary is loaded since iwlist works
<akaizen> Can you point me to what files i should be looking at?
naobsd has quit [Quit: Page closed]
arokux2 has quit [Remote host closed the connection]