<sjoerd>
mmind00: do you happen to know of any known issues with the network driver on the rock that could be related to that ^
<mmind00>
sjoerd: not really ... I know rperier was also looking at the arc-emac ... what kernel version are you on?
<sjoerd>
as it says 4.2.0-rc4-next-20150728+
dlezcano has joined #linux-rockchip
<sjoerd>
to yesterdays linux-next with my spdif patches
<sjoerd>
had it playing back internet radio for the last day or so
wildea01 has joined #linux-rockchip
<rperier>
yeah, I confirm, we have two issues in arc-emac: packets are lost sometimes and this panic
<rperier>
I think that it's a bug in the core driver (and not in the platform one)
<mmind00>
the Chromebook flip looks really cool btw :-D
premoboss has quit [Remote host closed the connection]
<sjoerd>
rperier: good to know, did you make any progress on tracking it down thusfar or just something you've seen before?
_whitelogger____ has joined #linux-rockchip
<sjoerd>
I see
<sjoerd>
the decision to go for 3188 vs 3288 is still open so we may or may not spent some time to dig into that one depending
<rperier>
Not sure but, I think that... both (the crash and packet lost) are the same bug : in one case the rx fifo is full, which throws a skb_panic... in the second case there are lost packets... something plays on how fast packets are received... this is also why I thought to a clk issue
<sjoerd>
I see
<sjoerd>
I havne't really seen the lost packets issue
<rperier>
Try to boot your rootfs via nfs :)
<rperier>
or just try to download a zImage via tftp
<sjoerd>
hehe
<rperier>
(via ssh everything seems to work fine)
<sjoerd>
rperier: do those things trigger both bugs or just hte lost packets one?
<rperier>
both bugs but the crash is not deterministic at all
<rperier>
lost packets happen more often (at least here)
<sjoerd>
ok
<sjoerd>
they may well happen here every so often but i may not notice thusfar
markm_ has quit [Ping timeout: 246 seconds]
markm has joined #linux-rockchip
em|biketron has joined #linux-rockchip
ssvb has joined #linux-rockchip
tizbac has quit [Ping timeout: 244 seconds]
rperier has quit [Ping timeout: 246 seconds]
rperier has joined #linux-rockchip
tizbac has joined #linux-rockchip
rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
rperier has quit [Changing host]
rperier has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
<apritzel>
mmind00: do you know about the usage of the SRAM on the RK3288?
<apritzel>
mmind00: I see that the first bytes are used for SMP, but are there other users?
<mmind00>
apritzel: suspend code uses the rockchip,rk3288-pmu-sram (different sram block)
Bludot has quit [Remote host closed the connection]
<apritzel>
IC, what is about this rk3288-ddr-sram in the DT?
<apritzel>
cannot find anything in the upstream tree
<mmind00>
apritzel: the ddr-frequency code uses parts of it when changing the ram freq ... the solution from the chromeos tree arch/arm/mach-rockchip/embedded/* was not really accepted, so it is currently limited to the chromeos tree
<mmind00>
apritzel: I think the way forward would probably be to resurrect the "physical independent executable" code from Russ Dill at some point
<apritzel>
mmind00: OK, so I better stay out of it. I am investigating adding PSCI support to u-boot and looking for some SRAM to put the secure monitor in
<apritzel>
mmind00: what do you mean by that PIE code?
<apritzel>
using DT even for u-boot itself seems like a good thing, it allows us to tweak those SRAM nodes depending on U-Boot's own requirements
<mmind00>
apritzel: psci also does suspend, right? ... so I guess you take the pmu-sram? ... which currently holds the kernel-side suspend code
<apritzel>
mmind00: haven't checked whether the psci u-boot actually supports suspend, maybe it's a trivial implementation
<mmind00>
apritzel: in any case ... that first part currently labeled as "smp-sram" is special to the core bringup, as it either contains the first-instruction address or the jump address for the bootrom
<apritzel>
mmind00: ... which is what I don't need in the kernel anymore once it uses PSCI ;-)
<mmind00>
apritzel: yep, but your psci implementation will need it
<apritzel>
mmind00: so I plan to grab this for the u-boot SMP pen and remove all the rk3066-smp nodes from the DT
<rperier>
amstan: do you know why does chromeos kernel use the "3.8" wireless subsystem ? other ones are buggy ?
<rperier>
I mean, there are 3 different ones :D
<mmind00>
apritzel: sounds good
<rperier>
I first try to understand how it is handled in a working kernel before porting these stuffs to mainline
arokux has quit [Remote host closed the connection]
arokux has joined #linux-rockchip
apritzel has quit [Ping timeout: 264 seconds]
arnd has quit [Read error: Connection reset by peer]
Bludot has joined #linux-rockchip
arnd has joined #linux-rockchip
jas-hacks has joined #linux-rockchip
VargaD has quit [Ping timeout: 244 seconds]
VargaD has joined #linux-rockchip
GriefNorth has quit [Quit: Konversation terminated!]
markm has quit [Read error: Connection reset by peer]
markm has joined #linux-rockchip
<amstan>
rperier: not sure, try asking dianders
markm has quit [Ping timeout: 240 seconds]
naobsd has quit [Quit: naobsd]
<dianders>
rperier: No good reason other than that WiFi team liked to use the same version for the same part. ...so we used 3.8 wireless for Marvel 8897 before, so we are using it again even though the rest of the kernel moved forward...
markm has joined #linux-rockchip
<rperier>
oh just for that, okay. I thought that it was for a technical reason (I mean, like buggy subsystem or something)
gb_master has joined #linux-rockchip
mrueg has quit [Ping timeout: 256 seconds]
gb_master has quit [Quit: Leaving]
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
gb_master has joined #linux-rockchip
mrueg has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
GTRsdk has quit [Remote host closed the connection]
markm has quit [Ping timeout: 240 seconds]
jas-hacks has left #linux-rockchip [#linux-rockchip]
markm has joined #linux-rockchip
gb_master has quit [Quit: Leaving]
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
gb_master has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
gb_master has quit [Remote host closed the connection]