Turl changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
dev1990 has quit [Remote host closed the connection]
akaizen has quit [Remote host closed the connection]
khuey|away is now known as khuey_
ninolein has quit [Ping timeout: 246 seconds]
naobsd has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
robogoat has joined #linux-sunxi
TheSeven has quit [Disconnected by services]
[7] has joined #linux-sunxi
traeak has quit [Ping timeout: 246 seconds]
traeak has joined #linux-sunxi
akaizen has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
premoboss has quit [Ping timeout: 272 seconds]
naobsd has quit [Ping timeout: 246 seconds]
premoboss has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
TheLinuxBug has quit [Ping timeout: 246 seconds]
kaspter has quit [Ping timeout: 240 seconds]
TheLinuxBug has joined #linux-sunxi
naobsd has joined #linux-sunxi
domidumont has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
cubeast has joined #linux-sunxi
domidumont has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
reinforce has joined #linux-sunxi
IgorPecovnik has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
reinforce has joined #linux-sunxi
akaizen has joined #linux-sunxi
petr has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
IgorPecovnik has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-sunxi
Igorpec3 has joined #linux-sunxi
florian_ has joined #linux-sunxi
f15h has joined #linux-sunxi
pietrushnic has joined #linux-sunxi
f15h has quit [Quit: Leaving]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
HeHoPMaJIeH has quit [Remote host closed the connection]
HeHoPMaJIeH has joined #linux-sunxi
camh has quit [Quit: WeeChat 1.0.1]
MaDMaLKaV has quit [Ping timeout: 244 seconds]
avph has joined #linux-sunxi
MaDMaLKaV has joined #linux-sunxi
camh has joined #linux-sunxi
premoboss has quit [Remote host closed the connection]
kaspter has quit [Read error: Connection reset by peer]
ricardocrudo has joined #linux-sunxi
kaspter has joined #linux-sunxi
domidumont has quit [Ping timeout: 246 seconds]
FR^2 has joined #linux-sunxi
avph has quit [Read error: Connection reset by peer]
kaspter has quit [Remote host closed the connection]
avph has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
orbifx has joined #linux-sunxi
orbifx has quit [Client Quit]
naobsd has quit [Remote host closed the connection]
db260179 has joined #linux-sunxi
<db260179> Hi all, I'll ask the question, hopefully someone can answer - regarding the A20 GMAC and its interaction with external PHY
<db260179> Does the A20 GMAC have rx_coe feature?
<db260179> My main interest with this is due to trying to understand what is causing the Lamobo R1 to have 50% speed when doing speed tests. This board has a Broadcom BCM53125 IC chip and is used as a PHY to the GMAC. Setting TX_Delays seemed to affect its speed - trying to understand if the issue lies with the GMAC or the Broadcom chip
db260179 has left #linux-sunxi [#linux-sunxi]
db2601799 has joined #linux-sunxi
<db2601799> Hi all, I'll ask the question, hopefully someone can answer - regarding the A20 GMAC and its interaction with external PHY
<db2601799> Does the A20 GMAC have rx_coe feature? 10:39:03
<db2601799> My main interest with this is due to trying to understand what is causing the Lamobo R1 to have 50% speed when doing speed tests. This board has a Broadcom BCM53125 IC chip and is used as a PHY to the GMAC. Setting TX_Delays seemed to affect its speed - trying to understand if the issue lies with the GMAC or the Broadcom chip
<NiteHawk> db2601799: A20 GMAC uses the stmmac driver. http://lxr.free-electrons.com/source/Documentation/networking/stmmac.txt gives me the impression that rx_coe is supported
pekka30 has quit [Quit: Leaving.]
<db2601799> Yeh, just wondering why it hasnt been enabled in the stmmac glue - drivers/net/ethernet/stmicro/stmmac/dwmac-sunxi.c
<db2601799> the /proc/softirqs for the RX are extremely high compared to the TX irqs. This makes me think that the effiency of toe could be used for the RX?
<NiteHawk> i have no idea. dwmac-sunxi.c comment says "hardware features were copied from Allwinner drivers.", so it may just be 'their way' of doing it and was never questioned/verified...
<db2601799> Anyone has any suggestions in what area to look at regarding performance issues related to a GMAC using external PHY (like stmmac to b53) - PCB distance is one, but i'm thinking a DMA or TOE could have an impact on buffering?
avph has quit [Ping timeout: 264 seconds]
khuey_ is now known as khuey|away
avph has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
avph has quit [Client Quit]
<plaes> db2601799: please try mailinglist
<plaes> with possible CC to linux-netdev
<db2601799> Ok, just thougt I try my luck here first
<db2601799> thanks anyway
db2601799 has left #linux-sunxi [#linux-sunxi]
premoboss has joined #linux-sunxi
philectro has joined #linux-sunxi
sehraf2 has joined #linux-sunxi
sehraf2 has left #linux-sunxi [#linux-sunxi]
sehraf has joined #linux-sunxi
TheLinuxBug has quit [*.net *.split]
_massi has quit [*.net *.split]
xenoxaos has quit [*.net *.split]
captainigloo has quit [*.net *.split]
sehraf has left #linux-sunxi [#linux-sunxi]
captainigloo has joined #linux-sunxi
xenoxaos has joined #linux-sunxi
_massi has joined #linux-sunxi
TheLinuxBug has joined #linux-sunxi
sehraf_ has joined #linux-sunxi
enrico_ has quit [Quit: Bye]
_massi has quit [Remote host closed the connection]
\\Mr_C\\ has joined #linux-sunxi
domidumont has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
vishnup has joined #linux-sunxi
premoboss has quit [Quit: Sto andando via]
Igorpec3 has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-sunxi
kaspter has quit [Ping timeout: 264 seconds]
afaerber has quit [Remote host closed the connection]
cubeast has quit [Quit: Leaving]
T0mW has joined #linux-sunxi
hero616 has joined #linux-sunxi
<bmeneg> hello all, is it possible to remove the UDISK NAND partition before I create a .img file for LiveSuit?
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
Igorpec3 has joined #linux-sunxi
orly_owl has quit [Ping timeout: 240 seconds]
naobsd has joined #linux-sunxi
orly_owl has joined #linux-sunxi
mcan has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
<fullstop> bmeneg: do you still wish to use the udisk?
<fullstop> I was somewhat lazy here and just made my udisk as small as possible. I don't need it.
<bmeneg> fullstop, no I don't. I usually resize it too, but I would like to make an .img alredy without it.
<bmeneg> already*
afaerber has joined #linux-sunxi
<fullstop> I seem to recall having some problems removing it completely, but I don't remember what they were. Best of luck!
<bmeneg> fullstop, :-D thanks.
JohnDoe_71Rus has joined #linux-sunxi
reinforce has joined #linux-sunxi
domidumont has quit [Read error: Connection reset by peer]
fathead has joined #linux-sunxi
xandey has joined #linux-sunxi
rZr has left #linux-sunxi [#linux-sunxi]
AlexDaniel has joined #linux-sunxi
hero616 has quit [Remote host closed the connection]
<AlexDaniel> Hi! I'm trying to build everything for A13-SOM, so I'm following this: https://linux-sunxi.org/Olimex_A13-SOM , the problem is that olimex_a13_som.fex file is missing. Where can I get it? Do I even need it? I've found this pull request https://github.com/linux-sunxi/sunxi-boards/pull/30 which has that file, but I'm still confused. What should I do?
<libv> AlexDaniel: take the one from the pull request for now, i will try to fix this in a bit
<libv> thanks for reporting this
<AlexDaniel> oh great
<AlexDaniel> that sounds promising!
<AlexDaniel> when building u-boot, should I use “sunxi” branch or mirror/next?
bonbons has joined #linux-sunxi
<AlexDaniel> oh, it looks like I should use mainline u-boot
<AlexDaniel> ok
<libv> AlexDaniel: but the fex file is still relevant if you wish to use sunxi-3.4 and we definitely need to carry it in our repo
<AlexDaniel> libv: um, do I want to use sunxi-3.4 or not? I'm not quite sure
<AlexDaniel> last time I tried to build it I simply couldn't
<AlexDaniel> at the same time, sunxi-next compiled just fine
<AlexDaniel> Still couldn't boot my stuff :(
<AlexDaniel> but now I'm trying again, so…
<libv> AlexDaniel: tbh, it's been way too long since i actively built anything sunxi, so i wouldn't know whether sunxi-3.4 still builds or not
<libv> i expect that we would have heard more people scream loudly about it failing to build though
<AlexDaniel> libv: I'm on debian unstable, it doesn't.
<libv> on top of that, simply throwing your hands up and stating "it's crap, it doesn't build" without quantifying that in any way is not very goal oriented
<AlexDaniel> libv: you are right :)
<AlexDaniel> libv: one more thing, this page https://linux-sunxi.org/Olimex_A13-SOM states that I should use OLIMEX-A13-SOM target
<AlexDaniel> but *** Can't find default configuration "arch/../configs/OLIMEX-A13-SOM_defconfig"!
<libv> for sunxi uboot?
<libv> or for mainline uboot?
<AlexDaniel> mainline
<AlexDaniel> olimex wiki says that I should use A13-OLinuXinoM_defconfig
<libv> does the device page mention mainline uboot support?
<AlexDaniel> so, should I just edit https://linux-sunxi.org/Olimex_A13-SOM page?
<libv> "No mainline U-Boot support available."
<AlexDaniel> libv: interestingly, it doesn't. But it is probably wrong
<AlexDaniel> 2.2. Building mainline u-boot
<AlexDaniel> it seems like there are new boards with samsung ram, which are somehow supported in mainline
<libv> AlexDaniel: i am extremely weary of wiping all different board variations under one has-been board name
<libv> AlexDaniel: it perhaps is a good idea to add a new target, but you would have to ask the people involved with sunxi mainline support about it
<libv> as said, i have not actively done anything in a while
kz1 has joined #linux-sunxi
ssvb has joined #linux-sunxi
<AlexDaniel> ok, so trying compile sunxi-3.4
<AlexDaniel> the first error that pops up is include/linux/compiler-gcc.h:103:30: fatal error: linux/compiler-gcc5.h: No such file or directory
<AlexDaniel> one of the comments makes sense: echo "#include <linux/compiler-gcc4.h>" > include/linux/compiler-gcc5.h
<AlexDaniel> now, after applying that fix, it still fails. And here is the log: https://files.progarm.org/sunxi-3.4_log
<AlexDaniel> And it actually solves the problem!
<AlexDaniel> by “solves” I mean that the error is gone
<AlexDaniel> I don't know if it breaks anything
<AlexDaniel> libv: is it a little bit mre goal oriented? :)
<AlexDaniel> more*
<AlexDaniel> what can I do? Is there any other information I should provide?
<AlexDaniel> or should I make a pull request?
fathead has quit [Quit: leaving]
florian_ has quit [Ping timeout: 250 seconds]
<ssvb> AlexDaniel: if you want to make the sunxi-3.4 kernel compile with gcc5, then you are welcome to submit patches
<AlexDaniel> OK
<AlexDaniel> however, there are many pull requests that are not accepted
<AlexDaniel> if I make a pull request with what I've just described, will anybody merge it?
<ssvb> AlexDaniel: you can also always downgrade the compiler if you suspect some compiler related regression, problems with new gcc versions are not exactly uncommon
<AlexDaniel> ssvb: yea, sure. But the last thing to do is to downgrade stuff… I'd much rather move forward
<ssvb> AlexDaniel: I guess, the concept of bisecting is also rather alien to you? because, you know, it involves compiling old code as a part of the process
<AlexDaniel> ssvb: bisecting is ok
<AlexDaniel> I'm just not quite sure that I want to spend too much time on all that stuff
<AlexDaniel> ssvb: and hold on, do you mean that there might be a problem with gcc itself? The code is pretty straightforward, I think that there is nothing wrong with the compiler…
<AlexDaniel> I could be wrong though
ricardocrudo has quit [Remote host closed the connection]
<ssvb> AlexDaniel: I mean that using the newest bleeding edge versions of the compiler increases the risk of encountering problems, especially when compiling rather old code
<AlexDaniel> ssvb: sure, but how bisect could possibly help?
<AlexDaniel> I see no point in having an exact gcc version that introduced that problem
<AlexDaniel> and on linux-sunxi side it will probably go all the way to the past
<ssvb> AlexDaniel: you can bisect the code and you can bisect compiler versions too
<ssvb> I think that using gcc 4.7 or 4.8 should be reasonably safe with the sunxi-3.4 kernel
<ssvb> AlexDaniel: btw, is the mainline kernel not good enough for you?
<AlexDaniel> ssvb: I'm not sure! I tried it yesterday and it couldn't boot. I just saw “Starting kernel ...” and that's it
<ssvb> AlexDaniel: what is your hardware?
<ssvb> AlexDaniel: it is described as "No mainline U-Boot support available / no Device Tree file for the A13-SOM"
<ssvb> AlexDaniel: what kind of u-boot config and the dts file are you using?
<AlexDaniel> ssvb: there is another guide here: https://www.olimex.com/wiki/A13-SOM-building-latest-Debian
<AlexDaniel> which is a bit shitty, but at least it is supposed to work
<ssvb> AlexDaniel: well, you can either try to do some mainlining work yourself, or seek support from the authors of that guide
vishnup has quit [Ping timeout: 246 seconds]
<ssvb> AlexDaniel: that guide also mentions that the DRAM chip type does matter
<AlexDaniel> yes
<ssvb> AlexDaniel: do you have HYNIX or SAMSUNG?
<AlexDaniel> ssvb: I have samsung one, so mainling u-boot should be ok
<ssvb> except that the mainline u-boot has no support for this board yet...
<ssvb> AlexDaniel: the olimex guide suggests using A13-OLinuXinoM_defconfig
<ssvb> it probably makes sense to compare schematics and/or fex files of A13-SOM and A13-OLinuXinoM to check whether they are really 100% compatible
<AlexDaniel> that's the only config out there, so it probably makes sense
<ssvb> so, basically, the kernel fails to boot for you
<AlexDaniel> yeah
<ssvb> it could be potentially a reliability issue (wrong DRAM config or something like this)
<ssvb> or it could be that the dts file from A13-OLinuXinoM is not really fully compatible
<ssvb> or maybe you just found some broken experimental kernel branch
<ssvb> where do you get your kernel sources?
<AlexDaniel> ssvb: I used sunxi-next branch
<ssvb> can you try the latest stable kernel release from kernel.org?
<AlexDaniel> hmmm
<AlexDaniel> definitely, but it would take some time
<ssvb> in any case, your hardware is not officially supported yet, so there may be some rough edges
<ssvb> somebody has to step up and do a proper mainlining job
<AlexDaniel> I see
<AlexDaniel> ssvb: thanks!
<AlexDaniel> I'm currently trying 3.4… if that works, I think that “somebody” will have less motivation to work on mainlining.
<ssvb> well, in fact it's in the best interests of OLIMEX to do the mainlining work themselves
<AlexDaniel> I agree
<ssvb> regarding the 3.4 kernel, just try to workaround these gcc quirks and also pay attention to http://linux-sunxi.org/Mainline_U-Boot#Troubleshooting
<AlexDaniel> “If your 3.4.x kernel refuses to boot / gets stuck right after "Starting kernel ...": Double-check that bootm_boot_mode is set to "sec"! (see above)”
<AlexDaniel> hm, I saw that, but didn't really pay enough attention
<AlexDaniel> ah right, I did that!
Netlynx has joined #linux-sunxi
Netlynx has joined #linux-sunxi
domidumont has joined #linux-sunxi
cubeast has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
akaizen has joined #linux-sunxi
afaerber has quit [Quit: Verlassend]
<AlexDaniel> yeah, just booted sunxi-3.4
<AlexDaniel> phew, finally
dack has joined #linux-sunxi
<ssvb> AlexDaniel: was anything special required (other than gcc related workarounds)?
<AlexDaniel> ssvb: no
<AlexDaniel> basically I followed that guide by olimex
<ssvb> ok
<AlexDaniel> and indeed, it works
domidumont has quit [Remote host closed the connection]
<AlexDaniel> ssvb: one more thing is that a lot of rt* drivers were failing to compile
<AlexDaniel> and I did not find any way to fix that
<AlexDaniel> so I just disabled it, I don't need those anyway
dack has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
alexxy[home] has quit [Ping timeout: 246 seconds]
alexxy has joined #linux-sunxi
domidumont has quit [Ping timeout: 246 seconds]
Andy-D has quit [Ping timeout: 252 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
pmattern has joined #linux-sunxi
Andy-D has joined #linux-sunxi
afaerber has joined #linux-sunxi
paulk-collins has joined #linux-sunxi
naobsd1 has joined #linux-sunxi
AlexDaniel has quit [Ping timeout: 250 seconds]
naobsd has quit [Ping timeout: 246 seconds]
naobsd1 is now known as naobsd
cubeast has quit [Quit: Leaving]
Netlynx has quit [Quit: Leaving]
Igorpec3 has quit [Ping timeout: 264 seconds]
pmattern_ has joined #linux-sunxi
pmattern has quit [Ping timeout: 246 seconds]
destroyedlolo has joined #linux-sunxi
<destroyedlolo> Hello everybody,
<destroyedlolo> I have 2 (stupid) question about the console vs LCD display
pmattern has joined #linux-sunxi
<destroyedlolo> or console vs framebuffer.
<destroyedlolo> 1/ my tablet has a 800x480 px display.
reinforce has quit [Quit: Leaving.]
<destroyedlolo> Why the kernel switched the console to 100x80 characters ? Some characters are missing on the side :(
pmattern_ has quit [Ping timeout: 246 seconds]
<traeak> overscan?
<destroyedlolo> How to remove it ?
<destroyedlolo> I have the same problem with Gentoo or Arch Linux, but with the same kernel.
<destroyedlolo> I didn't changed anything in the configuration.
T0mW has quit [Quit: Leaving]
paulk-collins has quit [Quit: Quitte]
<destroyedlolo> I have the problem only my A13 tablet, but not one my BananaPI.
Andy-D has quit [Ping timeout: 244 seconds]
Andy-D has joined #linux-sunxi
FR^2 has quit [Quit: Leaving]
semlanik has joined #linux-sunxi
<semlanik> Hi guys
<semlanik> Sorry I don't know exact rules of chat
<semlanik> But want to raise one question
<Wizzup> //i.qkme.me/3qt516.jpg <- basically
<Wizzup> er
<Wizzup> http://i.qkme.me/3qt516.jpg <- basically :)
<semlanik> Ok :) So currently there is not multi media support in mainline kernel
arossdotme has quit [Ping timeout: 256 seconds]
<semlanik> And according wiki society won't to integrate it
xypron has quit [Ping timeout: 264 seconds]
<semlanik> So basically mali shared ump and low-level drivers
<semlanik> But to get them work need to integrate sunxi display drivers for LCD and HDMI
<semlanik> did anyone investigate this?
<semlanik> any ideas?
<semlanik> I'm currently trying to copy drivers from linux-sunxi to mainline
<semlanik> but of course there are lots of dependencies
<semlanik> including platform support drivers
<Wizzup> sunxi can display over hdmi at least using simplefb
<Wizzup> I doubt just copying over drivers will work
<semlanik> Of course not :)
<semlanik> simplefb only works with hdmi
<semlanik> but idea is to port sunxi display drivers stack
<semlanik> I saw that there are pre-configured displays in folder that can be replaced with dti's
<semlanik> I mean in sunxi disp folder
<semlanik> But the main drivers I guess may be ported
<Wizzup> So what is your question precisely?
<semlanik> Yep and looks like multimedia support is on last place there
bonbons has quit [Quit: Leaving]
<semlanik> And for mali drivers i think maintainers are to pessimistic
<semlanik> The only non-opensouce part is openGL drivers
<semlanik> I mean librareis
<semlanik> Is there someone who is working on DMA?
<semlanik> Because DMA is part of basic "platform support" that looks like is not ported to mainline yet
<Wizzup> see that page :)
pmattern has quit [Quit: Genug für heute.]
<semlanik> So I need to contact them directly?
<Wizzup> "
<Wizzup> Support for DMA engine"
<semlanik> I know
<Wizzup> planned/merged for 4.3
<semlanik> But DMA engine is small part of platform support
arossdotme has joined #linux-sunxi
<semlanik> if you will look at it there are cpu clock drivers frequency controll etc/
<semlanik> if you will look at it there are cpu clock drivers frequency controll etc.
<Wizzup> If think your help will be appreciated in readying it :)
ricardocrudo has joined #linux-sunxi
<semlanik> I already read it :)
<destroyedlolo> Any idea for my overscan issue ?
<Wizzup> no, readying, not reading
<semlanik> ah sorry :)
<semlanik> Ok probably better to contact maintainers directly, because I want to know overall idea of porting. Looks like they reuse some "standard" arm parts by defining platform-specific things in dts's
<semlanik> Will check code as well
<semlanik> thanks anyway :)
semlanik has left #linux-sunxi [#linux-sunxi]
ricardocrudo has quit [Ping timeout: 265 seconds]
ggogy has joined #linux-sunxi
ggogy has quit [Client Quit]
jemk has quit [Ping timeout: 240 seconds]
jemk has joined #linux-sunxi
destroyedlolo has quit [Quit: Leaving]
philectro has quit [Quit: Konversation terminated!]
naobsd has quit [Quit: naobsd]
xandey has quit [Quit: leaving]
sehraf_ has left #linux-sunxi [#linux-sunxi]
AlexDaniel has joined #linux-sunxi
pekka30 has joined #linux-sunxi
boycottg00gle has joined #linux-sunxi