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
markm has quit [Ping timeout: 255 seconds]
markm has joined #linux-rockchip
cheetahw26 has quit [Quit: ChatZilla 0.9.91.1 [Firefox 32.0.2/20140917194002]]
naobsd has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
markm has quit [Ping timeout: 265 seconds]
<rperier> amstan: hehe, still need to backport edp driver (until it is merged in mainline) to check that this part works fine, the rest seems ok :)
<rperier> (modulo some bugs in next... but that's next...)
<rperier> (linux-next I meant)
<rperier> hi all btw
<sjoerd> ooi does anyone happen to know of hand how similar the lcd controllers are on RK31xx and RK32xx ?
<mmind00> sjoerd: the lcd controllers themselfs are quite similar ... the big difference is memory management
<mmind00> sjoerd: i.e. rk32xx uses an iommu, where the older ones do not
<mmind00> sjoerd: and the driver currently can only handle the iommu-path ... would probably need something cma-based for the others
<sjoerd> I see
<sjoerd> mmind00: thanks!
<mmind00> sjoerd: ah forgot to mention ... the output encoders connected to the lcd controllers are different too
<mmind00> sjoerd: aka stuff like hdmi etc is created by external chips on the rk3188
<sjoerd> Nod
<sjoerd> it's a RK616 or somesuch on the rock pro i have here
<mmind00> yep, or an IT-something on the earlier ones
<sjoerd> yup
* sjoerd is looking a bit into how hard it would be to get that all going
<sjoerd> not having to do a driver for the lcd part form scratch is at least very helpful :)
<mmind00> sjoerd: hehe ... having iommu and non-iommu allocation both supported in a driver is also already done in some other drm drivers, so you can get inspiration ;-)
* sjoerd was happy to discover that most of the audio output enablement is rather lowhanging fruit already
<sjoerd> mmind00: Yeah exynos does that indeed
<sjoerd> as one example
<mmind00> sjoerd: the hard part will probably be trying to manage two possible failing components (encoder
<mmind00> + lcdc)
<sjoerd> Yes
<sjoerd> That's always the fun if iti doesn't work with these things isn't it
<sjoerd> "something somewhere is wrong"...
<mmind00> yep :-)
<mmind00> sjoerd: anyway, https://github.com/mmind/linux-rockchip/commits/devel/lcdc-workbench contains some old things, where I at least compared the register sets a bit ... and I think rperier also did some first steps in this area
<rperier> indeed , I did
<rperier> few months ago
<rperier> https://github.com/rperier/linux-rockchip/tree/topic/drm-noiommu <--- you can look at this branch
<mmind00> rperier: when is the speedy v2 patch coming? :-D
<naobsd> it might be nice if someone support lcdc and hdmi bridge on u-boot too ;)
<sjoerd> It might be nice if rk3188 worked with upstream u-boot first :p
<naobsd> where can I buy my spare time? :)
<sjoerd> If you find out, do tell
<naobsd> by 1click
<rperier> mmind00: I will try to do it this noon (or this evening in the worst case), I don't do rockchip stuffs at work (unfortunately) :)
<mmind00> rperier: great
<rperier> :)
markm has joined #linux-rockchip
markm has quit [Ping timeout: 256 seconds]
markm has joined #linux-rockchip
wildea01 has joined #linux-rockchip
sunilmohan_w has quit [Ping timeout: 244 seconds]
sunilmohan_w has joined #linux-rockchip
xLinuxBot has joined #linux-rockchip
<rperier> don't compute Doug remarks about node names and "_" instead of "-"... I mean... everything in the dts for jerry is named with "_"...
naobsd has quit [Quit: naobsd]
nighty-_ has joined #linux-rockchip
Boohbah has quit [Ping timeout: 272 seconds]
Boohbah has joined #linux-rockchip
<mmind00> rperier: "edp_hpd: edp_hpd" -> "edp_hpd: edp-hpd"
<mmind00> rperier: the one with the ":" is the node reference with a "_", node-names normally have a "-"
<mmind00> rperier: but the epd should stay out for the time being anyway
<mmind00> rperier: I'm with Doug on this, to add epd stuff to all boards once the epd driver lands ... from what I've heard, shouldn't be long now for the merged driver to appear (aka exynos is using a similar edp IP)
<rperier> oh I totally agree about edp, I was just wondering what he meant for the naming issue
vetkat has quit [Quit: Bye bye]
cristian_c has joined #linux-rockchip
vetkat has joined #linux-rockchip
naobsd has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
arnd has quit []
arnd has joined #linux-rockchip
ganbold has quit [Ping timeout: 255 seconds]
arokux has quit [Remote host closed the connection]
arokux has joined #linux-rockchip
<rperier> mmind00: if I remember correctly, you have a not completly stable wifi for veyron in your devel/somewhat-stable branch ? no?
<mmind00> rperier: correct
<mmind00> rperier: the mwifiex can connect but when it is supposed to start transmitting real data it somehow dies
<rperier> mhhhh....I will try on my veyron and try to investigate
<rperier> I mean, if you don't plan to do it yourself of course
<rperier> that's a good way to learn how wifi really works in the kernel
<rperier> sorry if my sentences are not very clear... my brain itself is not really clear... I had an hard student night yesterday... I am not completly... "fresh" ... (tiny hangover) :/
<rperier> :D
<cristian_c> hello
<cristian_c> I'd like to access to mount user readable/writable nand partition (i.e. /sdcard)
<cristian_c> I think loop* block files are related to mtd partitions and I think I could mount /system or /sdcard , mtdblock8 and mtdblock9, respectively (they are ext4 the first one and vfat the second one). So, I'd like to know if maybe I've to enable some CONFIG options in the kernel configuration file or to something else. Any ideas?
GriefNorth has joined #linux-rockchip
GriefNorth has quit [Client Quit]
GriefNorth has joined #linux-rockchip
<amstan> mmind00: i remember steev and leming dealing with that a while ago on 3.14, but they fixed it eventually
<steev> amstan: nah, mwifiex is just a shitty driver.
<steev> amstan: my "workaround" is s2r and resume
<amstan> but it works fine for me on jerry right now
<amstan> oh yeah.. broadcom doesn't resume properly
<steev> i don't have a jerry
<amstan> rperier: you'll be the one having fun with that, speedy is broadcom afaik
<steev> yeah, i've noticed that with minnie
<leming> the main issue came from using the 3.14 drivers instead of 3.8
<steev> the 3.8 stack is heavily patched to work
cristian_c has quit [Quit: Bye]
<rperier> amstan: what do you mean ? all veyron don't have the same chipset for wifi ?
<mmind00> rperier: sorry, I'm back now ... I currently don't plan on spending larger amounts of time on wifi at the moment
<mmind00> rperier: yep, some are Marvell based and some use a Broadcom module
<rperier> arf... I see ^^
markm has quit [Remote host closed the connection]
<rperier> I want to use my wifi on speedy so I will try my best
<mmind00> rperier: see the mail from Michael Trimarchi ... who seems to have wrangled the broadcom chips a bit already
cristian_c has joined #linux-rockchip
GriefNorth has quit [Quit: Konversation terminated!]
<amstan> rperier: arch's kernel/drivers should work
<amstan> rperier: for broadcom, as long as you don't expect it to work after a resume
nighty-_ has quit [Quit: Disappears in a puff of smoke]
xLinuxBot has quit [Ping timeout: 255 seconds]
leming has quit [Ping timeout: 255 seconds]
cristian_c has quit [Quit: Bye]
nighty^_ has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
karlp has quit [Ping timeout: 256 seconds]
nighty^ has quit [Read error: Connection reset by peer]
karlp has joined #linux-rockchip
nashpa has quit [Quit: Going away]
nashpa has joined #linux-rockchip
markm has joined #linux-rockchip
leming has joined #linux-rockchip