<MoeIcenowy>
oh I cannot now understand this... I should now only undo it
<rellla>
it's up again :p
caog has left #linux-sunxi ["Ex-Chat"]
OverCR1 has joined #linux-sunxi
cptG has joined #linux-sunxi
OverCR has quit [Ping timeout: 260 seconds]
OverCR1 has quit [Ping timeout: 244 seconds]
cptG_ has quit [Ping timeout: 272 seconds]
IgorPec has quit [Ping timeout: 258 seconds]
<KotCzarny>
another column worth mentioning might be hdmi?
<KotCzarny>
or its the uboot part of initializing simplefb?
<MoeIcenowy>
But I think such a table should be present for AXP series
OverCR has joined #linux-sunxi
<mripard>
KotCzarny: simplefb is U-boot only
vagrantc has quit [Quit: leaving]
<speakman>
mripard: If I need to do minor modifications to sun7i-a20-olinuxino-micro.dts, like adding a simple device to one i2c bus, do I need to clone the whole dts file? I'm trying to #include it, but the dtc fails with syntax error on the "/dts-v1/" line
<speakman>
Why I'm asking, is because if I clone the dts, any changes to the original dts won't follow newer kernel versions. Or maybe there shouldn't be any changes to the "final" dts file, I'm not very well into this yet.
<mripard>
you can only have a single /dts-v1/
<mripard>
if you include some file that has it and declare in yours as well, it won't work
libv has joined #linux-sunxi
<speakman>
mripard: oh, ok. It does sound like a limitation to a newbie. There will always be situations where you add stuff to preexisting boards like the OLinuXino-A20-Micro, even if it's just a matter of a single device on an i2c bus.
libv_ has quit [Ping timeout: 244 seconds]
<speakman>
I build my kernel using Buildroot. Then I can manage my own dts file which then will be copied into the kernel source tree and compiled when the kernel is built.
<speakman>
It does seem like a more proper way to just make a very small dts with minor changes, which then #includes the generic board dts.
<speakman>
Just a thought at this moment.
Da_Coynul has joined #linux-sunxi
<MoeIcenowy>
mripard: speakman: so overlay is important :-)
<speakman>
It somehow feels that way when you first approach the Device Tree idea. :)
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 276 seconds]
paulk-nyan-big has joined #linux-sunxi
<wens>
speakman: #include <board-x.dts> is what we do for some very similar boards
<speakman>
wens: but that's not possible since the boart-x.dts includes the /dts-v1/; line
<wens>
then you don't have your own /dts-v1/; line
<speakman>
hm?
<speakman>
I do, but before the #include. If I just remove the /dts-v1/; line and only #include the board-x.dts? Trying as we speak :)
<wens>
speakman: see sun7i-a20-olinuxino-lime2-emmc.dts
<speakman>
wens: Yep, that worked perfectly :D
<speakman>
wens: But what about that "/ { ... };" thing at the top? Sorry, I'm very new to Device Tree :/
<speakman>
Can I replace "model" and "compatible" with anything I like? (except from "allwinner,sun7i-a20" of course)
libv has joined #linux-sunxi
libv_ has quit [Ping timeout: 260 seconds]
OverCR has quit [Quit: Leaving.]
OverCR has joined #linux-sunxi
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 272 seconds]
<wens>
you can
<speakman>
cool :)
<speakman>
mripard: do you know what commit fixes the simplefb? because I've implemented that latest clock change commit in my tree but it still doesn't work :/
Da_Coynul has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<plaes>
speakman: did you recompile dts?
<speakman>
plaes: yep, it's done every time (i've been changing the dts a lot lately(
<speakman>
)*
Da_Coynul has joined #linux-sunxi
<speakman>
I've even enabled boot logo and console on frame buffer just to be sure. I can see everything during boot as always.
Da_Coynul has quit [Client Quit]
reev has joined #linux-sunxi
<reev>
Hii , it is possible to run mac os on banana pi ?
<KotCzarny>
most likely no
<KotCzarny>
unless you port mac os kernel to it
OverCR1 has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<OverCR1>
reev: I don't think so.
<reev>
KotCzany okay cany you link any reference related to porting the mac kernel on ARM
<KotCzarny>
only if you are going to put lots of time and skills into it
<KotCzarny>
and most people heere are interested in linux
<reev>
hmm thanks! btw KotCzarny
libv has joined #linux-sunxi
libv_ has quit [Ping timeout: 272 seconds]
_stephan has quit [Remote host closed the connection]
<montjoie>
MoeIcenowy: your changelog are bery bad, always the same
Mr__Anderson has quit [Remote host closed the connection]
IgorPec has quit [Ping timeout: 240 seconds]
<MoeIcenowy>
montjoie: sorry...
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 240 seconds]
libv_ has quit [Ping timeout: 258 seconds]
afaerber has quit [Quit: Ex-Chat]
dearfibonacci has quit [Quit: Leaving]
libv has joined #linux-sunxi
dearfibonacci has joined #linux-sunxi
vagrantc has joined #linux-sunxi
DullTube has quit [Quit: Leaving]
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
IgorPec has joined #linux-sunxi
zumbi has quit [Ping timeout: 240 seconds]
zumbi has joined #linux-sunxi
<speakman>
well, problem solved pretty easy; reverting to version 4.6.3 both fixed the fb issues AND the interrupt issues.
<speakman>
This is the last day prior my six week vacation, but as soon as I get back I'm willing to test newer kernels or help debugging if the problem is not solved.
<mripard>
speakman: HEAD~1
<mripard>
speakman: and including a dts works
<mripard>
speakman: you just have to remove the /dts-v1/ line in the file that includes it
zumbi has quit [Ping timeout: 246 seconds]
<wens>
6 weeks sounds nice, though I doubt i could stay away from a computer that long
vagrantc has quit [Ping timeout: 276 seconds]
fire219 has joined #linux-sunxi
zumbi has joined #linux-sunxi
<speakman>
mripard: found that out thanks to wens :) The DTS inclusion works perfectly now :)
<speakman>
And while we're at it; if I have a "legacy" driver, which does not utilize Device Tree, can I still make it load automatically using Device Tree? It has two required arguments which are both specified in /etc/modprobe.d/thedriver.conf
<mripard>
no
vagrantc has joined #linux-sunxi
libv has quit [Ping timeout: 272 seconds]
<speakman>
ok
reev has quit [Ping timeout: 272 seconds]
<plaes>
speakman: what driver?
afaerber has joined #linux-sunxi
tlwoerner has quit [Remote host closed the connection]
<speakman>
plaes: it's my own very old one :D
libv has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
dearfibonacci_ has joined #linux-sunxi
dearfibonacci has quit [Ping timeout: 240 seconds]
a|3xx has quit [Ping timeout: 260 seconds]
Mr__Anderson has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
vagrantc has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
BenG83 has joined #linux-sunxi
|Jeroen| has joined #linux-sunxi
paulk-nyan-big has quit [Remote host closed the connection]
paulk-nyan-big has joined #linux-sunxi
matthias_bgg has quit [Quit: Leaving]
cnxsoft has quit [Quit: cnxsoft]
fredy has quit [Excess Flood]
dearfibonacci_ has quit [Remote host closed the connection]
libv has quit [Ping timeout: 240 seconds]
fredy has joined #linux-sunxi
IgorPec has quit [Ping timeout: 264 seconds]
jernej has joined #linux-sunxi
libv has joined #linux-sunxi
matthias_bgg_ has quit [Remote host closed the connection]
nove has joined #linux-sunxi
yann|work has quit [Read error: Connection reset by peer]
<BenG83>
ther is no source for the arisc binary for the A64, right?
<|Jeroen|>
no idea, but the A64 works great with mainline already
<apritzel>
BenG83: no, and given past experience with AW that's unlikely to ever be published
<apritzel>
BenG83: not that you would _want_ to look at it anyway
<BenG83>
I am still learning how the PMiC is handeled regarding the battery charger
<apritzel>
but as |Jeroen| mentioned: it's not needed for the current mainline approach
Mr__Anderson has quit [Remote host closed the connection]
<apritzel>
we may use the arisc at some point in time later, though, but that code would be from scratch anyway
<BenG83>
basically what I want to know is, if I change the battery paramters and charge current/cutoff voltage in the linux driver, will something interfere with that
<BenG83>
e.g. in suspend modes
<apritzel>
on the BSP Pine64 kernel the PMIC is entirely handled in the arisc
<apritzel>
but you give low level command via ATF and the mailbox interface
<apritzel>
so you can still access every PMIC register
<apritzel>
but yes: the arisc could trigger it's own commands
<apritzel>
I have observed this when accessing the RSB directly from Linux with the arisc running: registers changed
<BenG83>
I wanted to hook up my logic analyzer to the PMIC directly and watch the communication a bit
<BenG83>
not sure if I can get to the pins
<apritzel>
why would you want to do this?
<apritzel>
if you want to snoop PMIC commands, you could peek into the RSB registers
<apritzel>
namely command and data
<BenG83>
I would like to compare how the battery is charged with/without Linux running for example
Amit_t_ has joined #linux-sunxi
<apritzel>
without Linux? Android?
<BenG83>
does AW have different arisc binary for their Android BSP?
<apritzel>
well, AW doesn't even have a Linux ;-)
<apritzel>
BenG83: I was just wondering what you meant by "with/without Linux running"
<apritzel>
I wouldn't expect the arisc to actually do much about charging expect from initial setup, maybe
<BenG83>
ah, I meant just boot, but don´t run any high-level os with a PM driver
<apritzel>
OK, so like staying in U-Boot, for instance?
<BenG83>
yeah
apritzel1 has joined #linux-sunxi
<BenG83>
the PMIC has default register values for the charger, so it will do something
<|Jeroen|>
isn't it the same, android == linux
<BenG83>
potentially dangerous though if the battery is too small for example
<BenG83>
or non-standard lithium chemistry with lower cut-off voltage
<KotCzarny>
i think charging liion doesnt depend on capacity but on voltage
<BenG83>
I want to use li-fepo which needs 3.7V
<BenG83>
you need to limit the current in the beginning
<BenG83>
then go to constant voltage
<KotCzarny>
and your use case requires control because you do something not in the spec
<BenG83>
the PMIC can charge LiFePo fine
<BenG83>
just needs 3.7V cutoff register settings
<KotCzarny>
cutoff is a part of the (dis)charge process
|Jeroen| has quit [Quit: dada]
<OverCR1>
out of curiosity - are all NAND chips pin-compatible?
<BenG83>
there are often a lot of pin-compatible drop-in replacements / standadard series for a certain package and technology, but generally not
<apritzel>
they all corrupt your data in a compatible way ;-)
<BenG83>
I used a dual-port ram in a project which was basically the same from 8 different vendors...
<OverCR1>
asking because I noticed two different NAND chips used on one board (hynix/micron)
<KotCzarny>
grab the specs, compare?
<BenG83>
but sometimes pin/feature compatible still can have different timings, temperature and voltrage ratings
<BenG83>
or reliability classes
<OverCR1>
good to know, thank you
libv has joined #linux-sunxi
fredy has quit [Excess Flood]
fredy has joined #linux-sunxi
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 244 seconds]
libv_ has quit [Ping timeout: 244 seconds]
libv has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
OverCR1 has quit [Quit: Leaving.]
apritzel1 has quit [Ping timeout: 244 seconds]
popolon has quit [Quit: WeeChat 1.3]
jernej has quit [Quit: Konversation terminated!]
apritzel has quit [Ping timeout: 244 seconds]
lennyraposo1 has quit [Ping timeout: 276 seconds]
apritzel has joined #linux-sunxi
<Amit_t_>
maz: The GIC is dead, interesting subject line :)
apritzel has quit [Ping timeout: 244 seconds]
lennyraposo has joined #linux-sunxi
<mripard>
montjoie: we should probably order the fields alphabetically
<mripard>
before it gets out of hands with way too many IPs
Netlynx has quit [Quit: Leaving]
afaerber has quit [Quit: Ex-Chat]
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 244 seconds]
apritzel has joined #linux-sunxi
ricardocrudo has quit [Remote host closed the connection]
<jonkerj>
when at work, I am tinkering with the Opi sometimes, and every now and then it gets stuck
<jonkerj>
before today, this meant more productivity at work :-)
<jonkerj>
(what have I done?!)
<KotCzarny>
you want to work from home, don't you?
<KotCzarny>
now you can say to your boss that you have to test
<KotCzarny>
;)
<jonkerj>
well, my work does not involve embedded arm boards
<jonkerj>
but maybe I can convince my boss this contributes to the company goals some day
<TheLinuxBug>
I just want the Orang Pi Plus 2E to be able to run Android for more than an hour and a half without freezing,. I left it go the other night adn went to it in the morning to find it had hard frozen one hour after I left it. Likely the DRAM issues though as Android uses 672
<KotCzarny>
TheLinuxBug: wrong channel, its about linux :P
<TheLinuxBug>
ahahaha
<TheLinuxBug>
so I can bitch about Android too ;p
<jonkerj>
well, need to go, I will document it on the wiki next week from work :-)
<TheLinuxBug>
I am thinking though linux is going on it
<KotCzarny>
in the same way osx is freebsd :P
<TheLinuxBug>
I actually almost bought another just to see if one would actually work with those dram settings so I could stop bitching
<TheLinuxBug>
but then stopped short cause that seemed a bit insane
<TheLinuxBug>
ahaha
<KotCzarny>
:)
<KotCzarny>
just fix the droid?
<TheLinuxBug>
so far SDK isn't provided for it but believe me
<TheLinuxBug>
I have been thinking about it
<TheLinuxBug>
just nothing is easy in android from my experience
<TheLinuxBug>
and my biggest concern is getting it back on emmc
<KotCzarny>
binaryedit something?
<TheLinuxBug>
I am fairly confident I can make an android image on sd card and fix dram
<KotCzarny>
make 2 fexes differing only in dram speed and try finding it
<TheLinuxBug>
well problem is its not that easy in android
<TheLinuxBug>
the method tkaiser showed me gave me a headache
<jonkerj>
maybe the wine will spawn some creativity :-)
<KotCzarny>
wouldnt be bad to have relay with ethernet and magic frames capability ;)
jmcneill has quit [Ping timeout: 252 seconds]
sigjuice has quit [Ping timeout: 252 seconds]
<jonkerj>
that would be awesome
JohnDoe_71Rus has quit [Ping timeout: 252 seconds]
<jonkerj>
I am using my NAS as power source and ttyUSB anyways, so don't need that
montjoie has quit [Ping timeout: 252 seconds]
gaby has quit [Ping timeout: 252 seconds]
huehner has quit [Ping timeout: 252 seconds]
kronicd has quit [Ping timeout: 252 seconds]
orly_owl has quit [Ping timeout: 252 seconds]
<jonkerj>
here, enjoy the ASCII art
<KotCzarny>
perfect ;)
gaby has joined #linux-sunxi
huehner has joined #linux-sunxi
<KotCzarny>
add controller/slave devices?
kronicd has joined #linux-sunxi
orly_owl has joined #linux-sunxi
zuikis has left #linux-sunxi [#linux-sunxi]
<KotCzarny>
hmm, remote part could be done with usbip
libv has quit [Ping timeout: 276 seconds]
<KotCzarny>
though that still requires pretty intelligent third device
libv has joined #linux-sunxi
<jonkerj>
still, I think there is no point in doing that, because 99% of the use cases will involve a USB-UART connected to a unix box as well
<jonkerj>
but I agree it is awesome
sigjuice has joined #linux-sunxi
montjoie has joined #linux-sunxi
Mr__Anderson has joined #linux-sunxi
libv has quit [Ping timeout: 244 seconds]
BenG83 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
montjoie has quit [Remote host closed the connection]
libv has joined #linux-sunxi
<TheLinuxBug>
eesh
<TheLinuxBug>
I think its a bit disingenuous that C.H.I.P. said we would have the board in June and then shipped it the beginning of this week saying it would be at least 2 weeks till arrival from Hong Kong
<TheLinuxBug>
guessing they had some issues getting their supply in time
montjoie has joined #linux-sunxi
staplr has quit [Ping timeout: 260 seconds]
iaglium has joined #linux-sunxi
OverCR has joined #linux-sunxi
Amit_t_ has quit [Ping timeout: 250 seconds]
iamfrankenstein has joined #linux-sunxi
somedude23 has joined #linux-sunxi
Mr__Anderson has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
nove has quit [Quit: nove]
staplr has joined #linux-sunxi
Mr__Anderson has joined #linux-sunxi
Shirasaka-Hazumi has quit [Ping timeout: 276 seconds]
Shirasaka-Hazumi has joined #linux-sunxi
afaerber has joined #linux-sunxi
lemonzest has quit [Quit: Leaving]
staplr has quit [Remote host closed the connection]
jstein__ has joined #linux-sunxi
jstein has quit [Read error: Connection reset by peer]
jstein__ has quit [Ping timeout: 246 seconds]
firnsy_ has joined #linux-sunxi
BenG83 has quit [Quit: Leaving]
topi`_ has joined #linux-sunxi
kelvan_ has joined #linux-sunxi
tuxillo_ has joined #linux-sunxi
paulk-nyan-big has quit [Excess Flood]
firnsy has quit [Write error: Broken pipe]
tuxillo has quit [Write error: Broken pipe]
topi` has quit [Write error: Broken pipe]
kelvan has quit [Quit: No Ping reply in 180 seconds.]
paulk-nyan-big has joined #linux-sunxi
mozzwald_ has joined #linux-sunxi
mozzwald has quit [Ping timeout: 260 seconds]
RzR is now known as rZr
Mr__Anderson has quit [Quit: Leaving.]
jmcneill has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Aria 4.9.2, revision: git-6627-gf708225, sources date: 20160102, built on: 2016-05-12 17:32:15 UTC git-6627-gf708225 http://www.kvirc.net/]
Da_Coynul has joined #linux-sunxi
tsuggs has joined #linux-sunxi
paulk-nyan-big has quit [Quit: Leaving]
Da_Coynul has quit [Quit: My Mac has gone to sleep. ZZZzzz…]