<naobsd>
my miniroot is not buildroot, just a rootfs with busybox
dlezcano has quit [Ping timeout: 260 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<Linux_Bot>
naobsd: i also thought the same.
<Linux_Bot>
naobsd: anyway thanks for the information. any plan do config on buildroot for 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 quit [Ping timeout: 260 seconds]
naobsd has quit [Ping timeout: 246 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
Tony_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd>
I am _not_ using buildroot, sorry.
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
<amstan>
RayFlower: internet problems?
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<naobsd>
oh
<naobsd>
u-boot for rk3288 is now based on 2014.10
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<amstan>
?
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
Bludot has joined #linux-rockchip
<Tony_>
I can't find option "Use appended device tree blob to zImage" in 3.0 version kernel.
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<Tony_>
could I enable CONFIG_ARM_APPENDED_DTB in 3.0.36 version kernel ?
<karlp>
you don't need an option.
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<karlp>
just do cat arch/arm/boot/zImage arch/arm/boot/dts/rk3066a-minix-neo-x5mini.dtb > zImage_with_dtb
<karlp>
rkcrc -k zImage_with_dtb kernel.img
<karlp>
that sort of thing is all I've ever done.
<Tony_>
really ? and I used the rk3188 not rk3066.
<karlp>
same shit
<karlp>
appended really is literal :)
Avagetto has joined #linux-rockchip
<naobsd>
RK 3.0 kernel supports dts???
* karlp
shrugs.
<karlp>
I just wanted to say that "appended" means just that
<naobsd>
on kernel which supports dts/dtb, you can do "cat zImage dtb > out" at any time but if zImage doesn't have CONFIG_ARM_APPENDED_DTB, "cat zImage dtb > out" is useless
<naobsd>
cat doesn't need CONFIG_ARM_APPENDED_DTB to make output, but zImage needs CONFIG_ARM_APPENDED_DTB to use appended dtb
lioka has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
<Tony_>
naobsd, I think so too, and 3.0.36 don't support CONFIG_ARM_APPENDED_DTB is ensure ?
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 258 seconds]
<naobsd>
Tony_: why do you think rk 3.0 supports dts/dtb? it's just not supported. no need to care about CONFIG_* for dts/dtb
akaizen has joined #linux-rockchip
<Tony_>
I knew it can works fine without supporting dts/dtb. I just want to do it.(try it).
<naobsd>
Tony_: then please try it, no need to ask someone because no one try it
<Tony_>
CONFIG_ARM_APPENDED_DTB is supported from 3.2. I will try to merge them.
<Tony_>
Actually, I do want to use mainline kernel, because I can learn the new feature about kernel such as dts/dtb etc, but the mainline kernel missed so many driver about my board.
<Tony_>
So, I think about that why not to try add dts/dtb support on 3.0.38 which is stable on my board.
<naobsd>
"learn new feature" and "missed many driver" are independent
<naobsd>
you mixed 2 different thing
<naobsd>
please try it, but you need to do everything
<Tony_>
naobsd, You are right after careful consideration. they are independent. and I was anxious for success.
<Tony_>
naobsd, could you tell me that how to start from linux-next ? there no rockchip_defconfig or radxa_defconfig.
<Avagetto>
naobsd tell me please, do I understand correctly that rootfs is run in a LXC container using an initramfs?
<Tony_>
<naobsd> , okay.
<naobsd>
Avagetto: what system are you asking?
<Avagetto>
i ask about miniroot .
<Avagetto>
Ubuntu for example
<naobsd>
my miniroot? my miniroot doesn't use lxc. my miniroot is not ubuntu.
<naobsd>
well
<naobsd>
LXC is a set of kernel features and a set of tools to access kernel features
<naobsd>
my miniroot is neither kernel nor ubuntu. LXC related thing is not included.
<naobsd>
just "not included". I don't say my miniroot blocks LXC to run. you can do it yourself.
<Avagetto>
ok, i understand. sorry for the incorrect question
<naobsd>
if you asked how to make rootfs for LXC, lxc-create does it well. but lxc-create doesn't know my miniroot because my miniroot is not a part of LXC.
<naobsd>
my miniroot is just a my initramfs
<Avagetto>
I just don't quite understand how it works Initramfs. So I was thinking that she needed to run containers. As in virtual machines. Now I understand what was wrong. Will seek information on the Internet to understand how it works and what is needed. thanks thanks =)
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
<rperier>
Linux_Bot: that's not a big problem. So, you seems to use the mainline branch apparently
<rperier>
I will explain you how to build a kernel containing a initramfs, then you can create a boot.img from this image and flash it with upgrade_tool
<rperier>
open meta-rockchip/machine/include/rockchip.inc and remove IMAGE_CLASSES and IMAGE_FSTYPES
<rperier>
open build/conf/local.conf and add INITRAMFS_IMAGE = "core-image-minimal-initramfs"
<rperier>
then if you launch "bitbake virtual/kernel" your kernel will automatically use this initramfs and add it into the kernel
<rperier>
don't forget to check your kernel configuration with "bitbake -c menuconfig virtual/kernel" (adapt it to your needs)
<naobsd>
sounds nice :)
<rperier>
an important thing: core-image-minimal-initramfs does not create /dev/console and /dev/null , see USE_DEVFS variable in yocto (to create /dev statically)
<rperier>
(or create it by hand)
<rperier>
(from the recipe)
<naobsd>
"mount -t devtmpfs devtmpfs /dev" from init is not enough?
<rperier>
no because it does not create these files
<rperier>
this is what I did when I had the problem, I mounted devtmpfs and "sh" crashed because /dev/console was not found. So my kernel failed with "attempted to kill init"
<naobsd>
I only does it in my miniroot...
<naobsd>
btw
<naobsd>
such a tool which makes working system should be used more. many people mysteriously believe "only existing/provided rootfs image/whole system image can be used"
<rperier>
mhhh not sure if I tried with core-image-minimal-initramfs... just in case Linux_Bot try like that without USE_DEVFS and check if the kernel is able to start init and a shell or not
<naobsd>
existing image is just a sample, not mysteric item ;)
RayFlower_ has quit [Quit: RayFlower_]
<naobsd>
I also not sure about yocto thing. I should try myself
<naobsd>
btw
<naobsd>
who is the neo-technologies? (just curious)
<rperier>
naobsd: I am co-maintainer with Julien CHAVEAU, neo-technologies is his company.
<naobsd>
rperier: focusing embedded linux development?
<naobsd>
sorry, just a curious, no specific question
<rperier>
focusing on embedded developement, embedded linux , yes apparently
<naobsd>
rperier: I see, thanks
<naobsd>
rperier: I'm not sure about yocto project. your meta-rockchip will(can) be merged to upstream?
<naobsd>
or any external community need to maintain it?
<rperier>
naobsd: we need to improve some stuffs with mainline and to merge the mainline branch onto the master branch, and we will announce the project on the ML. And perhaps it might be hosted on git.yoctoproject.org
<rperier>
for now it is references on layers.openembedded.org
<rperier>
referenced*
<naobsd>
rperier: I see, sounds nice :)
<rperier>
naobsd: feel free to send us patches if you're interested ;)
<naobsd>
I see :)
<rperier>
for example, if you want to work on fbturbo with mainline. It would be nice ! :)
<naobsd>
well, lcdc and hdmi should be first ;)
<rperier>
right
<rperier>
(phy-usb and hdmi are in my todolist)
<Tony_>
naobsd, I don't know how to make a initramfs.cpio.
<Tony_>
kernel said it needs initramfs_data.cpio.gz.
<Tony_>
I got a initramfs.cpio.
<naobsd>
Tony_: do you have any ramdisk?
<naobsd>
gzip it
<Tony_>
likely boot.ing ?
<Tony_>
boot.img ?
<naobsd>
no rk header
<rperier>
naobsd: are you sure that hdmi does not work on the rock ?
<Tony_>
No, I haven't before. I had one on other board long long ago.
<rperier>
I doubt now...
<naobsd>
rperier: I think any rk lcdc code is not merged yet
<rperier>
mhhh
<rperier>
this is the driver rk1000, right ?
<rperier>
(something like that)
<naobsd>
rperier: rock is rk3188, it66121 i2c driver is needed
<naobsd>
^rk lcdc + hdmi
<naobsd>
oops. we need rk lcdc and hdmi driver
<naobsd>
rk1000 is analog video
<naobsd>
we don't need hdmi driver if we use 24bit(or less) RGB LCD module
<mrueg>
Isn't there a iommu driver also missing?
<naobsd>
only for rk3288? I'm not sure about iommu
<naobsd>
and I think RK people is working for rk3288
<rperier>
there is an iommu driver for rk3288, not sure if it is compatible with older SoCs...
<mmind00>
mrueg: rk3188 and earlier don't have iommus at all ... the Rockchip drm driver needs an additional dma-mapping path for it to support earlier socs
wildea01 has joined #linux-rockchip
<mmind00>
see drivers/gpu/drm/exynos/exynos_drm_{dmabuf,iommu}.c for reference
<mmind00>
rperier: also ^^
naobsd has quit [Quit: Page closed]
antoinemaillard has joined #linux-rockchip
Tony_ has quit [Quit: Leaving]
<rperier>
thanks for these information Heiko, looking
<wildea01>
mmind00: missed the start of that, but bear in mind that we're trying to rework a bunch of the dma-mapping/iommu glue atm
<wildea01>
Marek has patches for exynos
<wildea01>
(I've been dragging my feet a bit)
<mmind00>
wildea01: :-D ... I think Laurent said something similar in his dma-mapping talk at ELCE on better integration between the two
<wildea01>
mmind00: oh wow, that's the simplest page table format I've ever seen!
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
<wildea01>
mmind00: the current driver will be pretty slow though -- it uses strongly-ordered memory for everything (so also won't be cache coherent)
Tony__ has joined #linux-rockchip
<rperier>
mmind00: I think that drm and lcd/hdmi have higher priorities than phy-usb . I think that I will start to port the drm to older SoCs first and then backport the driver for hdmi (or lcd). phy-usb is still in my todolist, I will work on it later
<rperier>
mmind00: great, I will have a look at it
<rperier>
I mean, usb works, so even if phy-usb support is missing it is not a real blokcing task :)
<rperier>
however, nothing works in the graphical stack for older socs
<rperier>
I also think that working on the graphical stack will be hard and fun... that's exciting :D
<mmind00>
rperier: just beware that you have at the beginning two non-working components (lcd-controllers + output controller [hdmi, tv, etc])
Avagetto has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
hipboi_ has quit [Ping timeout: 265 seconds]
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
hipboi_ has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
eebrah_ has quit [Client Quit]
eebrah has quit [Remote host closed the connection]
eebrah has joined #linux-rockchip
nighty^ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
Avagetto has quit [Ping timeout: 244 seconds]
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
hipboi_ has quit [Ping timeout: 256 seconds]
<rperier>
do you suggest a particular order ? If I port the drm I might use fbdev to test the output .I mean, I need it to test output no ?
RayFlower_ has quit [Read error: Connection reset by peer]
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]
dlezcano has joined #linux-rockchip
hipboi_ has joined #linux-rockchip
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 265 seconds]
GriefNorth has quit [Ping timeout: 265 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<mmind00>
rperier: it's more difficult than that ... the drm code that will hopefully reach 3.19 only handles the core video-output-processor blocks
<mmind00>
rperier: this then gets handled by output transceivers for hdmi, display-port, tv or whatever
<mmind00>
rperier: on the radxa rock you have either the it66121 for hdmi (old boards) or rk616 for hdmi+lvds (new version) + rk1000 for tv-out
<mmind00>
rperier: and finally the rk3066 again contains a hdmi-ip inside the soc again [but it's a completely different one]
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 272 seconds]
dlezcano has joined #linux-rockchip
<rperier>
so I should patch the drm to support rk3188 and then gets this handled by it66121 (I have the old radxa rock, not radxa rock pro) ?
<rperier>
(as old SoCs are not supported by drm...)
dlezcano has quit [Ping timeout: 272 seconds]
dlezcano has joined #linux-rockchip
<karlp>
rperier: what exactly does "phy-usb" support mean? vs "usb works" ?
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<rperier>
karlp: a phy-usb driver might help to control advanced settings for the usb phy, sleep mode, regulator, use HSIC between usb host controller and the phy and so on, actually it works but it is a basic support
<rperier>
on rk30xx SoCs you can interact with the phy through the GRF, a phy-usb driver would change settings using the GRF
<rperier>
it would improve some stuffs
<rperier>
(I describe it in general, things might vary between platforms)
c0d3z3r0 has quit [Ping timeout: 272 seconds]
<mmind00>
rperier: yep something like this ... with the added obstacle that basic hdmi drivers alone very often are >= 50kb of code it seems, and the driver for the it66121 in the old rockchip kernels explicitly states its license as "Proprietary and Confidential"
<rperier>
oh shit ^^
<rperier>
(for its license)
<rperier>
unfortunately I don't have a radxa rock pro ^^
RayFlower_ has quit [Quit: RayFlower_]
<rperier>
mhhhh.... in this case, this is probably better to port cross-board (i.e cross radxa board) driver to mainline. The candidate would be rk1000...
<mmind00>
rperier: but in general my plan was to first wait till I see something on the then supported components ... because currently there is nothing to see on rk3288 in mainline too
<rperier>
ah you already work on this
<rperier>
don't compute, rk1000 is also used by rk3288 ?
<mmind00>
rperier: partially ... the Netxeon R89 uses it for tv-output
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
<mmind00>
rperier: so my planned ordering was rk3288-drm+hdmi -> rk1000 -> rk3188-drm -> it66121 ... so that always only one of the two components per board is working
<rperier>
I see
<rperier>
Unfortunately I cannot help on rk3288 (I don't have one)
<rperier>
No ways to parallelize tasks betweens SoCs ? There is nothing I can do on rk3288
Avagetto has joined #linux-rockchip
<rperier>
well, even If I understand your point of view
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
<rperier>
mmind00: in your ordering list , for hdmi, it would make more sense to support rk616 with the last RR pro instead of it66121... no ?
<mmind00>
ideally both :-) ... my old Radxa uses the it66121, so that would be something I'd look at [if I'd get this far at all]
Avagetto1 has joined #linux-rockchip
dlezcano has quit [Ping timeout: 250 seconds]
Avagetto has quit [Read error: Connection reset by peer]
Avagetto1 has left #linux-rockchip [#linux-rockchip]
dlezcano has joined #linux-rockchip
<rperier>
I have an old RR too
<rperier>
that's just to clarify things
<rperier>
you already have a lot of work with rk3288... so ideally I will help with rk3188 (this is a good way to learn a lot of things too)
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
<mmind00>
rperier: sure this wasn't meant to stop you :-) ... just to list where we stand and what already exist in some way
RayFlower_ has joined #linux-rockchip
<mmind00>
rperier: i.e. the rk1000 is way smaller in terms of functionality (compared to a hdmi-tx), so it may be a god idea to start with this one
<mmind00>
rperier: and it seems radxa published a datasheet of it
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 250 seconds]
bengal has joined #linux-rockchip
gb_master has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
RayFlower_ has quit [Remote host closed the connection]
<rperier>
mmind00: so you suggest that I might start to work on rk1000 ? ok, sounds a good plan
<mmind00>
rperier: yep ... you could take my mfd stub as starting point and there is also some sort ... I've also just pushed the tv-encoder mfd-cell to github
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
AstralixNB has quit [Quit: Leaving.]
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
<rperier>
mmind00: ok will have a look at it, thanks !
<rperier>
I am installing my new "war machine" (my new laptop) right now
dlezcano has quit [Ping timeout: 272 seconds]
dlezcano has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
RayFlower_ has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
tonikasch has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
c0d3z3r0 has quit [Client Quit]
c0d3z3r0 has joined #linux-rockchip
c0d3z3r0 has quit [Remote host closed the connection]
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
Astralix1 has quit [Read error: Connection reset by peer]
antoinemaillard has quit [Ping timeout: 244 seconds]
antoinemaillard has joined #linux-rockchip
tonikasch has quit [Remote host closed the connection]
gb_master has quit [Remote host closed the connection]
Astralix has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 244 seconds]
antoinemaillard has joined #linux-rockchip
antoinemaillard 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
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
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
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano 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
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
bengal has quit [Quit: Leaving]
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano 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]