ricardocrudo has quit [Remote host closed the connection]
vishnu_ has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 276 seconds]
<wens>
apritzel1: there should be some secure memory touch arbiter that controls non-secure access to various peripherals
tomboy64 has joined #linux-sunxi
nemunaire_ is now known as nemunaire
<vishnup>
apritzel1: I'm from India, however currently in Singapore
vishnu_ has quit [Quit: Leaving]
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 272 seconds]
Ueno_Otoko has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 245 seconds]
tomboy65 has joined #linux-sunxi
vishnu_ has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 272 seconds]
tomboy65 has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 255 seconds]
FDCX has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 250 seconds]
FDCX has quit [Ping timeout: 260 seconds]
TheSeven has quit [Ping timeout: 260 seconds]
TheSeven has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
p1u3sch1_ has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-sunxi
p1u3sch1 has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 260 seconds]
tomboy65 has quit [Ping timeout: 240 seconds]
Ueno_Otoko has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
vishnu_ has quit [Ping timeout: 250 seconds]
tomboy64 has joined #linux-sunxi
Deskwizard has quit [Ping timeout: 240 seconds]
vishnup has quit [Quit: Connection closed for inactivity]
tomboy65 has joined #linux-sunxi
FDCX has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 264 seconds]
vishnup has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 240 seconds]
IgorPec has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 240 seconds]
JohnDoe_71Rus has joined #linux-sunxi
orly_owl has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 240 seconds]
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 246 seconds]
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 260 seconds]
<mripard>
ssvb: so far, I've been running ar100-info
<mripard>
ssvb: I basically just memcpy the firmware to the SRAM, so there's no check for trusted code at this point
iamfrankenstein has quit [Quit: iamfrankenstein]
arossdotme has quit [Ping timeout: 256 seconds]
arossdotme has joined #linux-sunxi
reinforce has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
akaizen has joined #linux-sunxi
KotCzarny has quit [Quit: Reconnecting]
KotCzarny has joined #linux-sunxi
IgorPec has quit [Ping timeout: 246 seconds]
<vishnup>
mripard: a83t clock gates is similar to that of h3, as far as parent clocks are concern, except some clock indices are different, that can be easily managed in dts.
<vishnup>
just adding new compatible in clk-sun8i-bus-gates.c will be sufficient.
apritzel has joined #linux-sunxi
<vishnup>
clock indices which are different are within same parent.
xperia has joined #linux-sunxi
<mripard>
vishnup: so you have different parents from one bit to another, within the same register ?
apritzel has quit [Ping timeout: 246 seconds]
<vishnup>
mripard: yes, and it is same as h3. In gating reg0, index 17, index 29 belongs to AHB2 and others to AHB1.
<mripard>
hmmm
<mripard>
how did you find this out?
<mripard>
that's not what the BSP seems to be using
<xperia>
but for some strange reason my board does not boot when i flash it like i should. Did i compiled u-boot-sunxi the wrong way ? are the instructions to compile the bootloader in the link correct or it is something important missing? when i compare the u-boot image file that is shiped with the board and the one i build i get only 30% of the size. Any Advice about getting u-boot sunxi to compile...
<xperia>
...right highly appreciate.
<mripard>
vishnup: ah, no, my bad
<mripard>
vishnup: looking more into it, seems that you're right
<vishnup>
wens: jemk: Yes, for A83T also usb host is tied to AHB1 parent in sdk source.
<wens>
jemk: seems wierd that ohci and ehci have different parents
<jemk>
wens: yeah, very weird, and probably wrong, but how to find out?
<vishnup>
I'll keep as same as h3 for now. whenever we can confirm correct thing, we can change for both.
<jemk>
in a83 code all usb seems to have ahb1 parent
VargaD has quit [Ping timeout: 260 seconds]
VargaD has joined #linux-sunxi
arossdotme-planb has quit [Read error: Connection timed out]
arossdotme-planb has joined #linux-sunxi
<vishnup>
wens: As AHB2 clock source is ABH1, could that be reason for these inconsitensies?
vinifr has joined #linux-sunxi
<vishnup>
s/inconsitensies/inconsistencies
tomboy65 has quit [Ping timeout: 260 seconds]
<libv>
xperia: have you read the /topic?
tomboy64 has joined #linux-sunxi
ninolein has quit [Remote host closed the connection]
ninolein has joined #linux-sunxi
<xperia>
libv ahh okey guess should have asked to the u-boot channel. thanks for the tip!
<libv>
no
<libv>
you did not even bother to read our topic.
<libv>
you clearly missed that part that said "did you try looking at our wiki?"
<libv>
xperia: you seem to be quite capable of missing the obvious
<libv>
go to our wiki, at linux-sunxi.org and read up on the orange pi pc
<libv>
if our wiki is good enough already for h3, you should be able to work things out from there
<xperia>
look i can garantee that i have read everything. its not problem if the information is missing that i am looking for. btw. your orange pi pc config is crap and does not build anything that works.
<libv>
if not, you can identify what is missing and either ask back here or fill in the blanks yourself (and fill them in in the wiki as well)
<libv>
i am pretty sure that that guarantee is null and void if you used that link you posted
<plaes>
?
<plaes>
xperia: you said 'your orange pi pc config is crap...'
<libv>
SMD1: do not privmsg on questions that should be hitting the channel, especially not on "help me, help me" type questions
<libv>
SMD1: take it here
<plaes>
what config?
<libv>
also, i have h3 hw, i have not found the time to play with it yet
<libv>
but the answer is: go to the wiki
<libv>
if the wiki is unclear, either fix it, or ask here
<xperia>
Not sure why the linux.sunxi repo miss all this patches and files to get a working orange pi pc but i would not recommend the linux-sunxi repo to anyone.
<xperia>
to get a working build for the orange pi pc.
<libv>
the link to the manual build howto is pretty bad though
<plaes>
xperia: firstly, you followed unknown tutorial
<libv>
someone should change that to a H3 specific version
<plaes>
secondly, ypu should've used mainline u-boot
<SMD1>
libv: ok, sorry. I want to know the current status of H3 support by uboot and linux and issues with it, so I can try to help with something
<libv>
SMD1: go to our wiki, try to find the device you own
tomboy64 has quit [Ping timeout: 272 seconds]
<libv>
It says that under "Allwinner based devices"
<libv>
"If you are looking for support for your device from the sunxi community here, please take a look at our guide to identifying your device. If you cannot find your exact device, then you need to work through our new device howto to get it supported."
<plaes>
seems like we need #linux-sunxi-dev channel :)
<libv>
no
<libv>
never.
<libv>
-dev mailing lists and channels have always been a bad idea
<libv>
creates elitism and makes people loose focus from helping others
<plaes>
...for things like discussion about clock indices and gates ;)
<libv>
been there far too often these past... 12.5 years
<libv>
no, keep that here as well
<libv>
we just need to educate SMD1 and xperia
<plaes>
just joking
<xperia>
libv: plaes: thanks for the help especially the link to the wiki. now i read and understand what i did wrong. btw why such complicated why did you not use orangepi config as described?
<libv>
continue talking about clocks and gates
<libv>
xperia: because 1) linux-sunxi supports thousands of devices 2) mainline uses devicetree
<libv>
well, hundreds at least
<SMD1>
libv: it's orange pi pc. I just want to know what's under development so I wouldn't do double work.
<libv>
SMD1: did you try looking at our wiki?
<libv>
why are $shit_pi users like this?
<libv>
what do they fail to understand?
<xperia>
this is bad and compilcated. following the readme file i tryed to use orangepi and nothing else. this should be changed.
<libv>
xperia: no it is not.
<plaes>
xperia: which readme?
tomboy64 has joined #linux-sunxi
<libv>
xperia: our wiki is insanely good in comparison to everything else out there
<xperia>
it is i failed and this discusion is proof
<libv>
xperia: you just need to finally come to terms with that
<xperia>
the readme in the source repo
<libv>
xperia: what source repo?
<SMD1>
libv: sure. So I'm wondering if i.e. network or usb hosts or usm works let's say in uboot or someone needs to deal with it.
<xperia>
For all supported boards there are ready-to-use default
<xperia>
configurations available; just type "make <board_name>_defconfig".
<libv>
xperia: that is the standard uboot readme
<libv>
and will not be changed in a sunxi specific version
<xperia>
and it is incopatible with your wiki that require to use a different non orangepi def config board file
<libv>
xperia: which is why we have told you, a million times already, to look at our wiki.
<libv>
what do you fail to understand?
<plaes>
xperia: again, can you point out which wiki page you are talking about?
<SMD1>
libv: Maybe I just didn't clearly expressed my mind, but I'm asking for the current problems with supporting opi_pc in particular(yep, I've read the page about mainline intentions but I need more details) so I can choose one and try to fix it or help someone else. I suppose there should be some issue tracker or some coordinating person to get such info from. Thanks.
<libv>
SMD1: if so, feel free to add that to the H3 page
<libv>
it is a wiki.
<plaes>
xperia: `CROSS_COMPILE=armv7a-hardfloat-linux-gnueabihf- make orangepi_pc_defconfig` works for me nicely...
tomboy64 has quit [Ping timeout: 265 seconds]
<libv>
i cannot say this enough: use the wiki: read from it, find the holes, add to it.
<SMD1>
libv: but I don't know what to add, that's the question. I'm looking for someone or something tells me "hey, there is no $featurename working on h3 soc, plz implement it". Or am I supposed to ask this on wiki page?
<xperia>
plaes: it compiles but it does not work!
<libv>
the best thing i have done at my current customer is introduce a proper wiki
<libv>
SMD1: no, you should ask it here, but the first questions you asked were asked strangely, and came in the middle of xperia his stuff, and now it is lost in the noise.
<SMD1>
libv: sorry for that
<libv>
SMD1: ask again, clearly, when the noise dies down
<libv>
and then add that info straight into the wiki, so that no-one needs to ask that again :)
<plaes>
SMD1: there are mainline u-boot and kernel mainlining effort pages in our wiki
arossdotme has joined #linux-sunxi
arossdotme-planb has quit [Ping timeout: 240 seconds]
<plaes>
though, u-boot page is somewhat lacking in care...
<SMD1>
plaes: there is only "h3 support in 2016.01" and no doubts mainline uboot now works I believe. And I think I'm able to boot kernel and etc. But some features(network and etc) are either not supported or my config is wrong. That's what I'd like to know(and add to the wiki ofc): the list of (un)supported features and plans for them. There is something good for kernel, but not for uboot.
<libv>
we really need a manual_build_howto for each of the sdk versions, people should be told that when they work through the sdk
apritzel has joined #linux-sunxi
soderstrom has joined #linux-sunxi
arossdotme-planb has joined #linux-sunxi
arossdotme has quit [Ping timeout: 240 seconds]
soderstrom has quit [Ping timeout: 276 seconds]
yann|work has joined #linux-sunxi
<vinifr>
mripard, hi
vishnup has quit [Ping timeout: 250 seconds]
vishnup has joined #linux-sunxi
interrobangd has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
arossdotme has joined #linux-sunxi
arossdotme-planb has quit [Ping timeout: 260 seconds]
viccuad has joined #linux-sunxi
<plaes>
mripard: do you have branch with the A10 KMS v2 somewhere?
<plaes>
wip/drm-a33 ?
arossdotme has quit [Ping timeout: 264 seconds]
<wens>
plaes: seems like it
reinforce has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 272 seconds]
p1u3sch1 has joined #linux-sunxi
Deskwizard has joined #linux-sunxi
<mripard>
plaes: sunxi/wip/drm
<wens>
vishnup: i suggest you do clks and mmc before axp
<mripard>
vinifr: hi
mpmc has quit [Ping timeout: 250 seconds]
<plaes>
thanks :)
<vishnup>
wens: Okie, that good option. :) BTW mmc worked with my axp81x-mmc branch, it's bit ugly though
p1u3sch1 has quit [Ping timeout: 276 seconds]
<vishnup>
well, doesn't mmc need regulator node?
<wens>
vishnup: you can use fixed vcc3v0 from sunxi-regulators.dtsi, like we currently do for a23/a33/a80
<wens>
we replace them once we actually have pmic support
<montjoie>
anybody with an orangepipc under linux 3.4 that can dump memory (0x01C20000 from 0 to 0x304) ?
<apritzel>
yes, here we go: I have a shell prompt on the Pine64!
<apritzel>
# uname -rms: Linux 4.4.0-rc8 aarch64
<montjoie>
congrats, I wasnt believe that bootstrapping pine64 will be so fast
<wens>
congrats
<plaes>
o_O 4.4
<apritzel>
so fortunately the firmware situation isn't that bad: they enter the kernel in secure EL1, not EL3
<plaes>
is this mainline kernel?
<apritzel>
plaes: yes
<apritzel>
atm I hack the device tree into the u-boot prompt ;-)
<apritzel>
(with a script)
<apritzel>
because their DT is totally unusable with an upstream kernel
tkaiser has joined #linux-sunxi
\\Mr_C\\ has quit [Quit: .]
<apritzel>
so I glue the kernel and a slightly modified Debian installer initrd into an Android image, put that into one of the empty Android partitions and use their sunxi_flash command to load and boot
<wens>
no android fastboot?
<apritzel>
wens: tbh I haven't used that before, so hacking something onto the SD card was easier for me
xperia has quit [Read error: Connection timed out]
xperia has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
avph has joined #linux-sunxi
Supertanker2 has quit [Read error: Connection reset by peer]
reinforce has quit [Quit: Leaving.]
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
interrobangd has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
avph has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
rds has joined #linux-sunxi
interrobangd has quit [Read error: Connection reset by peer]
tucker has joined #linux-sunxi
Netlynx has quit [Quit: Leaving]
yann|work has quit [Ping timeout: 255 seconds]
tkaiser has joined #linux-sunxi
kaspter has quit [Ping timeout: 265 seconds]
vagrantc has joined #linux-sunxi
kaspter has joined #linux-sunxi
apritzel has joined #linux-sunxi
tkaiser has quit [Ping timeout: 245 seconds]
avph has quit [Ping timeout: 255 seconds]
tkaiser has joined #linux-sunxi
avph has joined #linux-sunxi
xperia has quit [Quit: ChatZilla 0.9.92 [Firefox 42.0/20151030075939]]
kaspter1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 265 seconds]
paulk-aldrin has quit [Remote host closed the connection]
kaspter1 has quit [Ping timeout: 265 seconds]
kaspter has joined #linux-sunxi
Rondom has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
iamfrankenstein has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 260 seconds]
iamfrankenstein1 is now known as iamfrankenstein
rds has quit [Quit: Page closed]
<ssvb>
SMD1: you asked about U-Boot on H3 yesterday and I already provided you with an answer about USB and Ethernet
<ssvb>
libv: the https://github.com/linux-sunxi/u-boot-sunxi repository's default branch should only contain README.md, explaining that the users should go to the wiki for further instructions
<ssvb>
we have discussed this with you and oliv3r some time ago, but no action had been taken
leio has quit [Ping timeout: 260 seconds]
iamfrankenstein has quit [Remote host closed the connection]