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
<mmind00> although I also don't see anything helpful there ... that nice status register seems to have appeared in the newer socs
<bryanp_> Looks like boot mode register might be telling enough for me but not 100%. As long as I can rule out that we called a restart or the kernel did for some reason the status of 6 should specify a watchdog reboot
levd has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Client Quit]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 276 seconds]
levd1 is now known as levd
cnxsoft has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 250 seconds]
levd1 has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd1 is now known as levd
Sadneophyte has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd1 is now known as levd
amstan_ has joined #linux-rockchip
<Sadneophyte> I have been using alarm on a rk3288 asus c201p for a couple months now, and I was getting tired of the SDcard wait times, What are the opinions here about installing it to the eMMC? Do I need to worry about libreboot or uboot? Where can I read about the correct way to deal with all the chromeos partitions, can anyone think of a good install guide which can be adapted?
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
Sadneophyte has quit [Ping timeout: 252 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 268 seconds]
levd1 is now known as levd
Sadneophyte has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 268 seconds]
levd1 is now known as levd
Sadneophyte has quit [Ping timeout: 252 seconds]
pozzoni has quit [Ping timeout: 260 seconds]
pozzoni has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 260 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
JohnDoe_71Rus has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 260 seconds]
levd1 is now known as levd
wadim_ has joined #linux-rockchip
amstan_ has quit [Ping timeout: 248 seconds]
amstan_ has joined #linux-rockchip
amstan_ has quit [Ping timeout: 248 seconds]
mrjay has joined #linux-rockchip
mrjay has quit [Client Quit]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 268 seconds]
levd1 is now known as levd
levd has quit [Ping timeout: 264 seconds]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd1 is now known as levd
cnxsoft has quit [Remote host closed the connection]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 is now known as levd
afaerber has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 is now known as levd
<afaerber> mmind00: seeing that you canceled your 4.6 pulls, do you plan to start queuing the initial GeekBox patches?
<afaerber> the whole net discussion is slowly moving towards fixes in the driver, not affecting my patches
<mmind00> afaerber: merge-window is open, so arm-soc won't take new features till rc1 ... and yep the network discussion seems pretty limited to the actual driver
<afaerber> mmind00: any other comments beyond the documentation?
<afaerber> for example, are you okay with Julien's proposed cleanups for the other boards?
<afaerber> I am hesitant to adopt that new EV code if the other boards don't
<afaerber> I don't even know how to test it
<mmind00> is anybody using that at all? :-) [just grepped through the kernel but failed to find any user of that]
<afaerber> maybe systemd or X11?
<afaerber> matthias_bgg: didn't you use evtest or something for power key testing recently? :)
<mmind00> yeah, I see some users in the input subsystem ... but it seems nobody on the devicetree side is using that currently
<matthias_bgg> afaerber, yes "evtest --grab /dev/input/eventX" should show you any event coming from the input system
<mmind00> afaerber: pcf50633-input.c even uses both EV_KEY and EV_PWR for its power-key
<mmind00> quite strange
<afaerber> matthias_bgg: do the trees you've worked with use linux,input-type = <EV_PWR> or just linux,code = <KEY_POWER>? does it make a difference anywhere?
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 260 seconds]
levd1 is now known as levd
<matthias_bgg> afaerber, do you know how to decipher the dts in proc?
<matthias_bgg> hexdump -Cv /proc/device-tree//soc@0/gpio-keys/button@1/linux\,code
<matthias_bgg> 00000000 00 00 00 74 |...t|
<afaerber> so 74 = 116 = KEY_POWER
levd has quit [Ping timeout: 244 seconds]
vev has joined #linux-rockchip
<vev> #libreidea is looking for voluntary devs to help us on idea creation tools - join us! - libreidea.org
vev has left #linux-rockchip ["Leaving"]
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 246 seconds]
libv_ is now known as libv
<afaerber> mmind00: have you noticed the /memory dtc warnings?
<afaerber> I'm wondering whether the plan is to add @0 (or @0,0 or something)
<mmind00> which warnings ... when I was compiling dtbs in my branches for 4.6 there were none
<afaerber> linux-next
<afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-evb-act8846.dtb
<afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
<afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-geekbox.dtb
<afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-geekbox-landingship.dtb
<afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
<afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
<afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-r88.dtb
<afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
<mmind00> I remember seeing people also complain about other things the updated dtc created
<mmind00> so I guess this will get addressed before hitting mainline (hopefully)
<afaerber> well, I am wondering about whether I need to make changes to my geekbox .dts that is not yet in the tree, when sending v4
<mmind00> afaerber: the memory nodes follow the general description in the ePAPR (I'm at least 80% sure :-) )
<afaerber> mmind00: I checked booting booting-without-of.txt and that mentions @0 somewhere
<afaerber> To define the physical memory layout of your board, you should
<afaerber> create one or more memory node(s). You can either create a single
<afaerber> node with all memory ranges in its reg property, or you can create
<afaerber> several nodes, as you wish. The unit address (@ part) used for the
<afaerber> full path is the address of the first range of memory defined by a
<afaerber> given node. If you use a single memory node, this will typically be
<afaerber> @0.
<mmind00> and my memory is bad it seems ... ePAPR also has the @0
<afaerber> but then again it goes on to talk about "the /soc<SOCname> node" which we all use as just /soc too
<mmind00> I do think @0 would be the correct implementation though
<mmind00> (meaning @start-address, which is 0 on the rk3368)
<afaerber> yeah, I did check that :)
<afaerber> so... should I just adopt that for the GeekBox patch or also convert the existing boards?
JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
cnxsoft1 has joined #linux-rockchip
bryanp_ has quit [Ping timeout: 276 seconds]
cnxsoft has quit [Ping timeout: 252 seconds]
cnxsoft1 is now known as cnxsoft
bryanp has joined #linux-rockchip
<mmind00> afaerber: however you like :-) ... if you're not doing it, I guess it will be me doing the conversion
dlezcano has quit [Quit: Leaving]
dlezcano has joined #linux-rockchip
<afaerber> mmind00: prepended it
<afaerber> I guess we don't need to backport that, so I skipped looking up Fixes headers
cnxsoft has quit [Quit: cnxsoft]
JohnDoe_71Rus has joined #linux-rockchip
afaerber has quit [Quit: Ex-Chat]
wadim_ has quit [Remote host closed the connection]
sunilmohan has quit [Ping timeout: 264 seconds]
sunilmohan_ has joined #linux-rockchip
sunilmohan has joined #linux-rockchip
sunilmohan has joined #linux-rockchip
sunilmohan_ has quit [Ping timeout: 244 seconds]
matthias_bgg has quit [Ping timeout: 244 seconds]
matthias_bgg has joined #linux-rockchip
afaerber has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
ganbold has quit [Ping timeout: 244 seconds]
paulk-collins has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
afaerber has quit [Quit: Ex-Chat]
paulk-collins has quit [Read error: Connection reset by peer]
paulk-collins has joined #linux-rockchip
akaizen has joined #linux-rockchip
matthias_bgg has left #linux-rockchip ["Leaving"]
akaizen has quit [Remote host closed the connection]
vickycq has quit [Ping timeout: 246 seconds]
vickycq has joined #linux-rockchip
bbelos has quit [Ping timeout: 276 seconds]
bbelos has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
afaerber has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
<bryanp> Anyone here have any experience with LAN8720 and warm restart not reiniting the device properly?
<naobsd> bryanp: which board/kernel?
<bryanp> its 3.0.8+ on something sort of like a minix neo x5
<bryanp> rk3066
cosm has joined #linux-rockchip
paulk-collins has quit [Quit: Quitte]
<naobsd> hmmm less experience with that kernel... :(
<naobsd> are you using stock kernel?
<naobsd> at least you have to use the kernel configured for your board
XPLOD6K has joined #linux-rockchip
<naobsd> then you need to check emac(vmac?) driver which does phy reset properly
naobsd has quit [Remote host closed the connection]
cosm has quit [Ping timeout: 276 seconds]
naobsd has joined #linux-rockchip
linux-rockchip has quit [Remote host closed the connection]
linux-rockchip has joined #linux-rockchip
ganbold has joined #linux-rockchip
<bryanp> Whoops sorry got stuck on recovery repacking and been focused
<bryanp> I am running a kernel config'd for my board but there must be a kernel driver but. rk_29 vmac + generic phy driver
<bryanp> bug* excuse my typo
nighty-_ has quit [Remote host closed the connection]
cosm has joined #linux-rockchip