IRC log of #cubox of Tue 19 Feb 2013. All times are in CET < Back to index

00:24 mhoney cubox!
01:02 Coburn CUBOX
01:02 Cobur 01:02 * Coburn says CUBOX to the tune of the SEGA bootup logos
01:04 DHowett that brings back memories. maaaan.
01:21 bencoh great, makes wanna turn the sega on, now.
02:52 Coburn :D
10:12 `jpi rabeeh:are you there ? :)
10:12 rabeeh here
10:12 rabeeh `jpi: pong
10:13 `jpi ok can i get the datasheet 88SV581x-V7 PJ4 ARM v7 SheevaTM CPU Core
10:13 `jpi or is it under some sort of NDA ?
10:13 rabeeh let me check
10:13 rabeeh i think it's public
10:13 rabeeh did u check the Marvell site?
10:14 `jpi well google didnt help me
10:14 rabeeh http://www.marvell.com/application-processors/armada-500/
10:14 rabeeh the processor internals is not there
10:14 rabeeh but the functional spec for the whole chip is there
10:14 rabeeh what are you looking for exactly?
10:14 `jpi yes exactly
10:14 rabeeh maybe i can answer
10:15 `jpi not much i just wanted to look into the internals maybe
10:16 `jpi is there anything specific to cpu core that might be needed for porting ?
10:17 `jpi the ethernet and serial drivers are not a problem, (can use kirkwood code)
10:18 rabeeh the cpu is ARMv7 instruction set wise
10:18 rabeeh there are differences i the l2 cache
10:18 `jpi it is documneted in the functional spec ?
10:18 rabeeh nop.
10:18 rabeeh probably not
10:19 rabeeh i'm searching the kernel code if there is a real difference
10:19 `jpi how did you do it ?
10:19 `jpi ok
10:19 rabeeh arch/arm/mm/cache-tauros2.c
10:19 rabeeh (that's for the L2 cache)
10:20 `jpi ok
10:20 `jpi ah yes the code also mentions the datasheet
10:20 `jpi probably under NDA :(
10:21 `jpi ok the shouldn't be difficult to translate the code
10:21 `jpi can you make this clear in the wiki page please ?
10:22 rabeeh ok
10:22 rabeeh it's barebox related - right?
10:22 `jpi nah plan9
10:22 rabeeh oh
10:23 `jpi actually plan9 has a kirkwood port
10:23 `jpi so the drivers shouldn't be issue
10:23 rabeeh yes. most of them
10:23 rabeeh except the headful stuff
10:23 `jpi the graphics driver needs to be done and
10:24 `jpi ok any way i can get access to these documents or simply go by linux code ?
10:25 rabeeh i think easiest is porting the code; i don't think there is much of that.
10:25 rabeeh at the beginning ofcourse you can get the port done with the L2 cache just to get things up and running
10:26 `jpi ok, thanks
10:26 `jpi i kinda don't like the code done by marvel LSP
10:27 `jpi i will get started then :)
10:28 rabeeh which one?
10:29 rabeeh https://github.com/rabeeh/linux/blob/master/arch/arm/mm/cache-tauros2.c
10:29 rabeeh ?
10:29 `jpi no i mean the mv_hal sys and stuff on your branch
10:30 rabeeh ?
10:30 rabeeh are you looking for the Marvell original 2.6.32.9?
10:30 `jpi yes i was looking at that
10:30 rabee 10:30 * rabeeh hates hals
10:30 rabeeh but thats the original code
10:30 `jpi :)
10:30 rabeeh the one i pointed you to is 100% hal-less
10:31 `jpi i guess the code on offcial branch would also be sufficient
10:31 rabeeh you choose; but the code i pointed you to is the upstream code and works without issues
10:32 `jpi ok
15:04 dv_ rabeeh: ping
15:05 rabeeh dv_ piong
15:05 dv_ do you know of this cubox kernel? https://github.com/vDorst/linux
15:05 dv_ it is the one arch linux arm uses
15:05 dv_ and includes your patches it seems
15:06 rabeeh it's an old one; original was more advanced but i think i took all patches
15:08 dv_ so I should use yours, not this one?
15:09 dv_ (I mean this one: https://github.com/rabeeh/linux )
15:10 rabeeh what is the kernel arch typically uses?
15:10 rabeeh my tree is 3.6.9
15:10 rabeeh and looking for DT based tree
15:14 dv_ https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-cubox/PKGBUILD
15:14 dv_ its the one I told you about earlier
15:15 dv_ I am trying to create a cubox meta layer for yocto, since the existing ones didn't work for me
15:15 dv_ thats why I ask for a tree. I think I'll use yours.