<mmind00>
amstan: i.e. we know that it works, and this way the clock ids will be in 3.19-rc1 already
<mmind00>
amstan: and of course even if all patches were ready at the same time, they would still go through different trees (clk, arm-soc, mmc) - it would be different if there would be no user on the horizon at all
RayFlower has quit [Read error: Connection reset by peer]
field^Mop has joined #linux-rockchip
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
field^Mop has quit [Ping timeout: 245 seconds]
cosm has quit [Ping timeout: 258 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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
lioka has joined #linux-rockchip
cosm has joined #linux-rockchip
levd has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
nighty-_ has quit [Remote host closed the connection]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 245 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
levd has quit [Ping timeout: 272 seconds]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
<amstan>
mmind00: sent
levd has quit [Remote host closed the connection]
levd 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
levd1 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
levd has quit [Ping timeout: 264 seconds]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
markm__ has joined #linux-rockchip
markm_ has quit [Ping timeout: 255 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
RayFlower has quit [Read error: Connection reset by peer]
naobsd has quit [Quit: Page closed]
RayFlower has joined #linux-rockchip
Tony_ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 272 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 256 seconds]
cnxsoft has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 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
naobsd 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: 255 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
RayFlower_ has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
irsol_ has joined #linux-rockchip
mrcan__ has joined #linux-rockchip
arokux1 has joined #linux-rockchip
RayFlower has quit [Ping timeout: 264 seconds]
eebrah has quit [Ping timeout: 264 seconds]
irsol has quit [Ping timeout: 264 seconds]
mrcan_ has quit [Ping timeout: 264 seconds]
arokux has quit [Ping timeout: 264 seconds]
RayFlower_ is now known as RayFlower
irsol_ has joined #linux-rockchip
irsol_ has quit [Changing host]
irsol_ is now known as irsol
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
naobsd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
levd1 has quit [Remote host closed the connection]
levd has joined #linux-rockchip
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: 264 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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 265 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 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
antoinemaillard has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 264 seconds]
antoinemaillard has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 255 seconds]
field^Mop has joined #linux-rockchip
levd has quit [Quit: levd]
<naobsd>
I want to know (roughly), who want Firefly board, for what?
antoinemaillard 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
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
wildea01 has joined #linux-rockchip
antoinemaillard_ has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 240 seconds]
antoinemaillard_ is now known as antoinemaillard
mrcan__ is now known as mrcan
<Tony_>
naobsd, free ? I want to one. :P for developing.
Tony_ has quit [Remote host closed the connection]
<AstralixNB>
Firefly board?
<AstralixNB>
Is this getting the channel of giveaways?
<AstralixNB>
I am interested for plain linux, linux desktop and chromeos development
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd>
just asking for now. if no one want, there is no reason to ask.
<naobsd>
and here is developers' community, Firefly board is dev board, "for development" is very natural like as breathing ;)
<AstralixNB>
You are right.
<AstralixNB>
But it is a bit problematic to tell specific parts... The overall Interest is to build a working linux desktop unit.
<naobsd>
ah, last message was for Tony :)
<naobsd>
and "for what" imply "for community", not "for my private project"
<AstralixNB>
Ah, but you're right anyway. Even porting linux is still a not so specific thing
<naobsd>
linux(kernel?), linux desktop, and chromeos sounds good
<naobsd>
"linux" is not so specific, but it should be ok. no need to promise specific goal, I'm just asking
<AstralixNB>
Lot of really good guys are at the kernel porting thing. And it is hard to catch up with them if you only can code at night times.
<AstralixNB>
But packing everything into an image, provide images for NAND, eMMC and SD is quite a work
<AstralixNB>
Cool
<naobsd>
yes but personally
<naobsd>
making new distribution is not my preference
<naobsd>
I like "add support new board to major distribution"
<AstralixNB>
No. Not a new distry, but uprgrading existent distris to full support of these boards
<AstralixNB>
This is what I meant.
<naobsd>
it should be upstreamed (if upstream accept it), otherwise it will be one more "old, not maintained someone's personal distro" in future...
<AstralixNB>
Hmmm... not sure
<AstralixNB>
I use radxa with ports.ubuntu.com and added all security and update cahnnels.
<AstralixNB>
So I am always up to date
<naobsd>
me too.
<naobsd>
bebause it's ubuntu
<naobsd>
what I talked is *untu for (some not so major board)
<AstralixNB>
What is somet8imes a bit tricky, is the kernel and WiFi as you need to use the right GPIOs and have to tweak udev or such things.
<naobsd>
tweak is always needed even for x86 PC :)
<AstralixNB>
Right, but you cannot do all of them. I prefer ubuntu/lubuntu, but 90% of the things will work out for any other distri too
<AstralixNB>
So If we share our knowledge, someone else could do xubuntu or even debian or slackware
<naobsd>
I tried gentoo and arch on RR too. if my memory is correct, no special hack is needed
<AstralixNB>
The major part will be adding hw-decoding and 2D/3D support of MALI.
<AstralixNB>
And this is a big bunch of work as there are now different approaches for all this Effects Support for X
field^Mop has quit [Ping timeout: 264 seconds]
<AstralixNB>
wayland and other servers probably will need some hand crafting of whatever RK will provide to us
<naobsd>
it's our common todo, not distro specific.
<AstralixNB>
sure
<naobsd>
anyway
<naobsd>
noted: "Astralix: linux, chromeos"
<naobsd>
:)
<naobsd>
3.14 kernel for chromeos should have drm support and there is userland mali library configured for linux/x11.
<AstralixNB>
nice :) Thanks
<naobsd>
it should be good for Linux desktop too
<AstralixNB>
Yes, I follow these activities
field^Mop has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<mmind00>
naobsd: I would of course also be interested in a firefly :-) [and obviously general mainline-kernel work]
antoinemaillard has quit [Quit: antoinemaillard]
<naobsd>
noted "mmind00: mainline"
<wildea01>
mmind00: what's the soc/cpu on firefly?
<mmind00>
wildea01: rk3288
<wildea01>
mmind00: with the same bootloader as the board we have atm?
<mmind00>
wildea01: just in the form-factor similar to the Radxa board, so a lot more portable than the evbs
<wildea01>
ah, ok
<mmind00>
wildea01: I would guess that they'll use a similar uboot-version
<naobsd>
Firefly uses u-boot from Rockchip's Android SDK
<rperier>
naobsd: I might a want a firefly too for mainline (if possible)
<naobsd>
noted "rperier: mainline"
antoinemaillard has joined #linux-rockchip
<rperier>
naobsd: did the firefly company contact you ?
<naobsd>
I sometimes ask them some things
<wildea01>
naobsd: so that uboot still enters the kernel in svc mode, right?
<naobsd>
include "giving away", but nothing is decided yet
<naobsd>
wildea01: CONFIG_ARMV7_VIRT is not enabled (is it enough? I don't have enough knowledge about it)
<wildea01>
naobsd: yeah, that would need to be enabled
<wildea01>
naobsd: there was an erratum on the early a17 which caused issues with jtag at hyp mode, so I think the rockchip bootloader engineers struggled to get it working
<naobsd>
wildea01: and some SoC specific implementation is needed to enable it, right? I think build was failed if just enable it
<wildea01>
naobsd: yes, you need to implement some callbacks to secondary CPU handling and stuff iirc
<wildea01>
the allwinner platforms should have support in upstream uboot, so that would be a good reference
<naobsd>
is CONFIG_ARMV7_PSCI and CONFIG_ARMV7_VIRT independent?
<naobsd>
yes, I know sunxi code in upstream u-boot
<naobsd>
RK's u-boot is 2014.10 based
<wildea01>
I'd need to check the sources; I haven't looked at uboot for a few months
<wildea01>
you probably need PSCI to get the secondary cores into hyp mode inside uboot
<naobsd>
well
<naobsd>
PSCI is required for SMP under hyp mode? or current SMP support in kernel can be used for hyp mode too?
<naobsd>
(if virt timer/counter is configured correctly)
<naobsd>
(I guess PSCI is better, just curious these 2 are independent or not)
<naobsd>
these 2: virt timer/counter and psci
<wildea01>
naobsd: I think the kernel will barf if the secondary core enters at a different mode to the primary core
<naobsd>
well
<naobsd>
should I note "wildea01: virtualization in kernel/u-boot" ? ;)
<wildea01>
hehe, if you like, although I already have one of the dev boards
<naobsd>
I'm just asking, I cannot promise anything anyway ;)
<naobsd>
I'm not sure we can get RK3288 TRM from firefly (I guess no)
<naobsd>
so what we can do is limited
<AstralixNB>
I am pretty sure that some people supporting mainline or other open designs already have access to TRM
<naobsd>
yes, I heard about it
<naobsd>
but Firefly is not Rockchip, they will not give it
<naobsd>
(I'm not asking "some people" to give it)
<AstralixNB>
But many companies designing hardware with the SOC never got the TRM.
<naobsd>
yup
<AstralixNB>
They all just reference to the reference boards and try to keep everything close to these demo kits
<naobsd>
I just want to clear what I said "want a board"? :)
<naobsd>
not "want support?" "want docs?"
<AstralixNB>
But this should not be a problem. RK open source guys are know to work without any detailed information :)
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
eebrah_ is now known as eebrah
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
naobsd has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 245 seconds]
<naobsd>
oh, drm, finally
<naobsd>
+ dw_hdmi, we can use hdmi out?
naobsd has quit [Quit: Page closed]
field^Mop has quit [Ping timeout: 256 seconds]
<rperier>
how is it possible to power a board through usb and to see nothing displayed about this on in lsusb ?
<rperier>
(even if I probe the bus with libusb the connection is not seen at all)
<rperier>
I have an usb hub which supports "ganged port switching", I am able to cut the power for the usb serial, and it works fine... not for the usb which supplies the board
<rperier>
:/
<rperier>
(that's my RR which is powered through the usb otg port)
naobsd has joined #linux-rockchip
<naobsd>
only VCC and GND are connected?
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
cnxsoft has quit [Quit: cnxsoft]
<rperier>
naobsd: no I am using a usb otg to host cable from a phone, it's a normal cable... and... this is the same cable I use to flash the NAND too
<rperier>
I should at least see something in lsusb... with a vendor and a product ID, something which proves that it is connected to the usb bus
<rperier>
(however, I should try with the power supply shipped with the RR, the green cable)
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<mmind00>
rperier: you'll probably only see anything if a gadget driver is enabled on the board-side [g_ether, g_storage or whatever is in these days]
<rperier>
or dwc2 gadget ?
<rperier>
yeah, I was looking for usb gadget on google because I thought it has something to do with it (I was not sure before your confirm it)
<rperier>
:)
<rperier>
however... If I remember correctly... I had a vendor and a product Id with the power supply cable shipped with the RR... (so it would be seen by the host side). Anyway, I will test both
lioka has joined #linux-rockchip
lioka has quit [Changing host]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 250 seconds]
crash911 has joined #linux-rockchip
<crash911>
hi @ all
<crash911>
hi i curently try to compile a cross compiler tool-chain for rk3188 so i need to find the kernel headers in the linux source can somone please point me in the right direction?
<mmind00>
rperier: the dwc2 is the gadget controller (and host and otg) ... but you still need a gadget driver implementing your desired gadget functionality
<crash911>
ok never mind i found what i was looking for
<mmind00>
rperier: and the vendor/product id seems to be bound to the gadget-driver (see for example drivers/usb/gadget/legacy/ether.c)
<crash911>
hmm i just love git repos and good wikis
<crash911>
good bye and a nice evenning @ all
crash911 has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
bengal has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 264 seconds]
<naobsd>
rperier: I thought you talked about mask rom or loader mode
gb_master has joined #linux-rockchip
<naobsd>
gadget driver is required
FreezingCold has joined #linux-rockchip
gb_master has quit [Remote host closed the connection]
gb_master has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
bengal has quit [Ping timeout: 258 seconds]
RayFlower has joined #linux-rockchip
Bludot has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
bengal has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
RayFlower has left #linux-rockchip [#linux-rockchip]
_whitelogger has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 272 seconds]
field^Mop has joined #linux-rockchip
RayFlower has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
bengal has quit [Ping timeout: 272 seconds]
bengal has joined #linux-rockchip
bengal has quit [Ping timeout: 240 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 255 seconds]
Bludot has quit [Quit: Connection closed for inactivity]
gb_master has quit [Remote host closed the connection]
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 258 seconds]
FreezingCold has joined #linux-rockchip
<field^Mop>
gb_master: hm, that's interesting. can you provide any details about your pl2303?
<field^Mop>
rperier: what naobsd probably meant was: on the device that is connected via usb but not showing up (or existing) by usb, the only pins connected of the usb socket on the device are vcc and gnd. that way, the device is a dumb one, barely able to suck power via the usb cord (even if that is a off-the-shelf standard usb cord)
<field^Mop>
rperier: is that applying to your usb device? as i have no clue about your usb device i can only guess what your situation actually is like and then jump to conclusions/hypotheses
bengal 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
field^Mop has quit [Ping timeout: 245 seconds]
pirmar has joined #linux-rockchip
pirmar has quit [Client Quit]
bengal has quit [Remote host closed the connection]