<Tony_>
naobsd, I can login in after reboot. ubuntu:ubuntu
<Tony_>
naobsd, the problem is show when it's resume.
<naobsd>
sorry, no idea
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 256 seconds]
<Tony_>
naobsd, okay, thank you anyway. it is a known bug.
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<ganbold__>
naobsd: pong
<naobsd>
firefly shipping will be delayed
<ganbold__>
how long?
<naobsd>
not sure
<ganbold__>
well, not sure what to do
<ganbold__>
if it is unknow then maybe it is better to cancel it
<ganbold__>
sorry for trouble
<naobsd>
well
<naobsd>
if it's too late to transfer to your wife, I can send it EMS or something like that
<naobsd>
in this case you need to wait some more days
<naobsd>
cost shouldn't be so high
<ganbold__>
I see
<ganbold__>
ok, then will wait
<ganbold__>
thanks a lot
<naobsd>
but if you want to get it more early, I can cancel "2 firefly" and we can reorder individually
<naobsd>
firefly adjusted shipping cost
<naobsd>
well
<naobsd>
checking
<naobsd>
oh
<naobsd>
they added another way, air mail, sing post (for jp)
<naobsd>
for mongolia, only DHL, $48.84
<ganbold__>
yeah, just saw it
<ganbold__>
I've never thought getting free board makes some problems
<naobsd>
I think ( $37(to JP) + $??(to you) ) / 2 is still cheaper
<naobsd>
hehe
<ganbold__>
:)
<ganbold__>
anyhow it seems it is better wait to reach the board to you :)
<ganbold__>
I'm not in a hurry so no problem
<naobsd>
I see
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<rperier>
naobsd: this is for all firefly boards ?
<naobsd>
rperier: I thought so, but you didn't get email from firefly/aliexpress?
<rperier>
no, I already paid for shipment
<naobsd>
rperier: check email and/or aliexpress order status
RayFlower has quit [Quit: RayFlower]
<naobsd>
rperier: me too
<rperier>
the state is "provider is processing your order"
<naobsd>
rperier: it's not payment issue
<rperier>
I am on aliexpress
<rperier>
"provider is processing your order"
<rperier>
and no email
<naobsd>
when time limit expire in your order?
<naobsd>
for my order, it was today. they asked me to extend it, so I did it
<rperier>
naobsd: 5 days
<naobsd>
rperier: probably it's the reason you didn't get email
<naobsd>
all I can say is my firefly was not shipped today
<rperier>
what does the mail from firefly say ?
<ganbold__>
they send such email to me too
<ganbold__>
should I extend it ?
<rperier>
naobsd: payment deadline is 16 th december
<rperier>
so perhaps we have to wait until the 16th december...
<rperier>
and order deadline is tomorrow... so perhaps everything will be process by the firefly company once the deadlines will expire... don't know ^^
RayFlower has joined #linux-rockchip
<naobsd>
ganbold__: I think you don't have active order. I guess firefly sent email both me and you because my order is for us
<ganbold__>
yeah
<naobsd>
rperier: I recommend to click "extend" before order deadline ;)
<rperier>
naobsd: yeah, this is what I planned to do, don't worry :)
<rperier>
(just in case...)
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
Tony__ has joined #linux-rockchip
c0d3z3r0_ has joined #linux-rockchip
levd1 has quit [*.net *.split]
Tony_ has quit [*.net *.split]
c0d3z3r0 has quit [*.net *.split]
ganbold__ has quit [*.net *.split]
c0d3z3r0_ is now known as c0d3z3r0
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 245 seconds]
apritzel has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
levd has joined #linux-rockchip
RayFlower has joined #linux-rockchip
levd1 has quit [Ping timeout: 258 seconds]
<Tony__>
time go home, bye everybody.
<Astralix1>
Have a nice ride :)
linuxium has joined #linux-rockchip
levd1 has joined #linux-rockchip
<Tony__>
;P
Tony__ has quit [Quit: Leaving]
GriefNorth has quit [Ping timeout: 264 seconds]
<apritzel>
Hi guys, anyone is knowing about upstreaming effort for u-boot RK32xx support?
wildea01 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
<linuxium>
Saw the news on Firefly re news on giveaways ... well done to both Firefly and those who have 'won' one ... anyone know the difference between the prototype and mass production boards? Does this now mean the prototype is obsolete?
GriefNorth has joined #linux-rockchip
<linuxium>
Also, still trying to find out the difference between Beelink (Netxeon) v2.0 and v3.0 PCBA if anyone knows?
<linuxium>
And, as a final question asking your views, Chipspark seems relatively new so has anyone any experience of them?
levd1 has quit [Ping timeout: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 244 seconds]
cnxsoft has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Danukeru has quit [Ping timeout: 250 seconds]
Danukeru has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
cnxsoft has quit [Ping timeout: 245 seconds]
hipboi has quit [Ping timeout: 256 seconds]
linuxium has quit [Ping timeout: 246 seconds]
antoinemaillard has joined #linux-rockchip
<mmind00>
apritzel: I think there is currently no effort in this area to get rockchip support into core uboot
<apritzel>
mmind00: I was afraid you would be saying that ...
<apritzel>
lets see if I can spare some time for this
<apritzel>
rkchrome/uboot.git from github somehow works for me, but is not even remotely upstreamable as it stands
faddat has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
antoinemaillard_ has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 250 seconds]
antoinemaillard_ is now known as antoinemaillard
cnxsoft has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
hipboi has joined #linux-rockchip
ganbold_ has quit [Ping timeout: 245 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
GriefNorth has quit [Ping timeout: 258 seconds]
antoinemaillard has joined #linux-rockchip
linuxium has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
<faddat>
howdy! Is there a sage here who can help me through my first kernel build? Have looked @ web site & reference materials, have one lingering question: Do I need to do anything much different if I want 3.18?
neyder_ has joined #linux-rockchip
<neyder_>
helllo to all
<faddat>
hey neyder
<faddat>
how are ya?
<neyder_>
sad. i can't compile for my device :8
<neyder_>
but don give up
<faddat>
What's your device?
<faddat>
I've got....
<neyder_>
RK3188 XT-Q7-V10
cnxsoft has quit [Quit: cnxsoft]
<neyder_>
WLAN: RTL8188
<neyder_>
LAN: RTL8201F
<neyder_>
Bluetooth: Mediatek MT6622
<neyder_>
none of them work
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Client Quit]
antoinemaillard has quit [Ping timeout: 245 seconds]
antoinemaillard has joined #linux-rockchip
<rperier>
mmind00: apparently, the regression for ethernet is caused by the gate "hclk_emem_peri", adding "CLK_IGNORE_UNUSED" to its flag, seems to fix the issue
<mmind00>
rperier: great find ... it seems Julian did find a similar regression for the usb ... so maybe you could send a patch too
<rperier>
there is any way to enable them "dynamically" ?
<rperier>
(I don't know if it does make sense...)
<mmind00>
rperier: in the future yes, but these clocks are part of the interconnect (peripherals <-> core) which nobody really looked at yet
<mmind00>
and of course, a regression-fix for 3.19-rc1+ needs to be the smallest change possible to fix the issue
<rperier>
of course
<rperier>
I will send this patch this evening, and then I will start to work on a dts file for RR Pro
<rperier>
(I received the board yesterday)
<mmind00>
rperier: ok great
linuxium has quit [Ping timeout: 246 seconds]
<faddat>
neyder
<faddat>
just so happens I've something similar
<faddat>
ls 6x v12
<faddat>
mmind: you've a firefly/
<faddat>
?
<faddat>
and if you've a firefly, do you also have any 3288 *tablet* at your disposal?
Tony__ has joined #linux-rockchip
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
<mmind00>
faddat: you forget the "00" ... an irc-ping only works with the full name (aka mmind00) ... I don't have a rk3288 tablet ... I'm currently working with a rk3288 eval-baord from rockchip ... I don't have a firefly yet, but are supposed to get one
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
<faddat>
Gotcha-- I am trying to figure out if it's possible to repurpose a 3288 tab-- what I've in mind, basically newer linux & android and MAYBE ubuntu touch-- would require a full recompile AFAIK
RayFlower has joined #linux-rockchip
field^Mop has joined #linux-rockchip
Tony__ has quit [Quit: Leaving]
field^Mop has quit [Ping timeout: 272 seconds]
naobsd has joined #linux-rockchip
<mmind00>
faddat: it's always possible to repurpose things, but I'm not sure what your question for me was
<naobsd>
faddat: I just saw your mail on google groups
<naobsd>
faddat: linux-rockchip is developers' community, it's totally different to web forums
<faddat>
sorry, is there any sort of globally applicable set of compile parameters, etc, that I could be somewhat assured would work on a tablet platform? naobsd: sorry, I am not sure i get your meaning?
<naobsd>
faddat: for example, we never discuss things like "if you could build an image for Firefly (beta), you could run that image in any 3288 TV box"
<faddat>
why wouldn't you?
<naobsd>
because we know different hardware is different
maz has joined #linux-rockchip
<wildea01>
maz: welcome to the party
<mmind00>
faddat: I don't know what you mean with a "globally applicabe set of compile parameters" ... I don't do any userspace stuff, so I don't think I'll be able to help you there
<naobsd>
we talk technical thing
<maz>
wildea01: saw some light, decided to enjoy the show...
<faddat>
I wasn't sure if the hardware is in fact different or not-- so thanks for the info
<naobsd>
we don't think just "full recompile" is enough to make things work. we know we need to write code to make it work.
<faddat>
I am kinda trying to change that(or at least the volume of code you might need to write) across several device platforms from several cpu mfgrs.... what is it precisely you're trying to say here, rather obtusely? Might be nice to expand access to device customization so that customers can explore new concepts & computing paradigms on their own, I think.
<naobsd>
faddat: are you Linux kernel developer?
<faddat>
No. I make tools for people who build linux kernels.
<naobsd>
faddat: can I see your tools?
<faddat>
Good god kid, I"m trying to make a script. I'm going to need information before I can do that.
jas-hacks has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
<faddat>
And.... frankly, no-- I have a pile of spaghetti at the moment. If you'd like to login to my pile of spaghetti and help me to figure out how to get every noodle straight, well then be my guest. I'm trying to bring multiplatform development/customization tools to more people. Help, or not-- I'm certainly not 1337 developer like some here. I don't like to program C as a rule.
RayFlower has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
<naobsd>
faddat: so, if you can find things like "globally applicable set of compile parameters, etc", you can make a script for "multiplatform development/customization tools to more people"
<naobsd>
?
<jas-hacks>
hi all, should be getting a firefly soon, want to find out the state of linux support for rk3288 ?
<faddat>
I am not claiming to be or trying to be a kernel developer. I'm trying to be an enabler of people less skilled than me, so far, far less skilled than the people I"ve met here today, in whose presence I tremble....
<naobsd>
hmm
<faddat>
I'm not really trying to focus on what my users are or are not-- I"m trying to give them an onramp
<naobsd>
it's difficult to say what I want to say "precisely"
<faddat>
Well, if the HW is different
<faddat>
then there isn't going to be any globally applicable set of parameters etc
Danukeru has quit [Ping timeout: 250 seconds]
<faddat>
so it would have to be per-device, so I've extracted one piece of info, that's good
<naobsd>
all I can say is, here is technical community
<naobsd>
jas-hacks: mainline linux is getting better day to day
<jas-hacks>
I'm trying to determine if there is kms/dri2 driver available and what binary blobs it needs to run
<naobsd>
in mainline? in 3.14 for chrome/chromium os?
<jas-hacks>
anywhere?
<naobsd>
ah, drm driver for rk3288 is already merged in linux-next, so true for both...
<jas-hacks>
looks like your getting support from rockchip looking at the mailing list
RayFlower has quit [Quit: RayFlower]
<naobsd>
me? no. I'm just an individual, I have no relation to rockchip
<jas-hacks>
I meant some of the patches seem to be from rockchip
<naobsd>
well, there are some rockchip people in linux-rockchip infradead ML, if you make/send a patch to that ML, you may be able to get support from rockchip
<naobsd>
linux-rockchip infradead ML and here are not same
<naobsd>
some people on here join that ML
<naobsd>
anyone can join that ML
<rperier>
mmind00: my comment was not a prose-confirmation, I just meant that "it does not work for me too" :D
<rperier>
however I can test and confirm that it fixes the issue
<naobsd>
is there anyone who got problem with "clk: rockchip: add ROCKCHIP_PLL_SYNC_RATE flag to some plls" commit? only me/rayeager2 board?
<mmind00>
rperier: hehe ... yep ... as it should go into 3.19-rc kernels, factual confirmation is always good to have
<naobsd>
I have to revert that commit, otherwise kernel boot stops at
<mmind00>
naobsd: pll not locking in time looks like something deeper ... this commit probably only exposes it :-)
<naobsd>
rockchip_pll_wait_lock: timeout waiting for pll to lock
<rperier>
do you mean that we absolutely need to add these tags to fixes which will go to -rc kernels ?
<naobsd>
mmind00: oops. clk/pll things are really difficult for me...
<rperier>
mhh apparently yes... m'okay, good to know, be will careful next time
<mmind00>
rperier: no ... it's not absolutely necessary
<rperier>
but it's a good thing to have it anyway, right ?
<rperier>
(it depends on maintainers opinions and feels probably)
<mmind00>
rperier: correct ... and there might come cases where it is not that obvious like in our two cases that a fix is right/needed
<rperier>
yep, makes sense
<mmind00>
jas-hacks: core drm driver will most likely make it into 3.19
<naobsd>
mmind00: I think drm userland interface is same as chromeos 3.14 kernel, right? (i.e. libdrm is also available)
<jas-hacks>
has anyone verified drm in 3.14?
<naobsd>
I cannot find any reason that chrome os developers made/committed non-working code...
<naobsd>
I think, verified first, then commited
gb_master has joined #linux-rockchip
<naobsd>
(but I'm not chrome os developer, I don't know what they did. I saw only videos on youtube...)
<naobsd>
hm, let's try emac on rayeager2...
<naobsd>
px2
<naobsd>
julien's patch fixes usb, and rperier's fixes emac, righ
<naobsd>
I need both, right?
<naobsd>
let's try...
<rperier>
if these parts of the clk tree are used by your board, yes you should
<naobsd>
rperier: I see
<rperier>
did you add support for emacs in the px2 ? (you need to add pinctrl topology and explain to the kernel which pins to use to be able to connect to the phy ethernet and works with it)
<rperier>
s/emacs/emac/
<naobsd>
rperier: default pinctrl setting in rk3066a.dts should be enough
<naobsd>
rperier: I cannot see any special pin
<naobsd>
ah, sorry, there is reset pin, but I already found it, it should work