lerc has quit [Quit: No Ping reply in 180 seconds.]
Yong has joined #linux-sunxi
indy has joined #linux-sunxi
nixdork has joined #linux-sunxi
medvid has quit [Ping timeout: 252 seconds]
medvid has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
jski has quit [Ping timeout: 260 seconds]
jski has joined #linux-sunxi
ninolein has joined #linux-sunxi
ninolein_ has quit [Ping timeout: 252 seconds]
Putti has quit [Remote host closed the connection]
Putti has joined #linux-sunxi
Nacho has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
Nacho has joined #linux-sunxi
aballier has quit [Ping timeout: 260 seconds]
victhor has quit [Ping timeout: 240 seconds]
lkcl has joined #linux-sunxi
cptG has quit [Ping timeout: 240 seconds]
cptG has joined #linux-sunxi
Char0n has quit [Read error: Connection reset by peer]
terra854 has quit [Quit: Connection closed for inactivity]
afaerber has joined #linux-sunxi
pg12 has quit [Ping timeout: 260 seconds]
pg12_ has joined #linux-sunxi
chomwitt has quit [Ping timeout: 240 seconds]
reev has joined #linux-sunxi
lennyraposo has joined #linux-sunxi
Char0n has joined #linux-sunxi
vagrantc has quit [Ping timeout: 255 seconds]
terra854 has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<dgp>
Does anyone know how to get actual part numbers for allwinner parts? I'm trying to get a quote for the v3s but the broker says they can't find it and need the actual part number :/
lkcl has quit [Ping timeout: 258 seconds]
<plaes>
dgp: maybe guys in #olimex know
<plaes>
they have ordered from them
<dgp>
plaes: Thanks!
lkcl has joined #linux-sunxi
[7] has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-sunxi
jernej has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
a|3x has quit [Remote host closed the connection]
goofie has quit [Ping timeout: 260 seconds]
goofie has joined #linux-sunxi
IgorPec has quit [Ping timeout: 260 seconds]
jernej has quit [Ping timeout: 240 seconds]
kloczek has quit [Ping timeout: 240 seconds]
lemonzest has joined #linux-sunxi
reinforce has joined #linux-sunxi
a|3x has joined #linux-sunxi
IgorPec has joined #linux-sunxi
kloczek has joined #linux-sunxi
lemonzest has quit [Quit: Leaving]
lemonzest has joined #linux-sunxi
terra854 has quit [Quit: Connection closed for inactivity]
f0xx has joined #linux-sunxi
terra854 has joined #linux-sunxi
DullTube has joined #linux-sunxi
aballier has joined #linux-sunxi
ganbold has quit [Ping timeout: 240 seconds]
ganbold has joined #linux-sunxi
ganbold has quit [Remote host closed the connection]
ganbold has joined #linux-sunxi
diego_ has joined #linux-sunxi
phil42 has quit [Ping timeout: 268 seconds]
ganbold has quit [Ping timeout: 240 seconds]
phil42 has joined #linux-sunxi
paulk-elm has joined #linux-sunxi
yann|work has quit [Ping timeout: 245 seconds]
techping has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
ganbold has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
LargePrime has joined #linux-sunxi
jsadat has joined #linux-sunxi
velly has joined #linux-sunxi
velly has quit [Read error: Connection reset by peer]
velly has joined #linux-sunxi
nOOb__ has quit [Ping timeout: 240 seconds]
yann|work has joined #linux-sunxi
reev has quit [Ping timeout: 245 seconds]
lurchi__ has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
lurchi__ has quit [Ping timeout: 260 seconds]
kloczek has joined #linux-sunxi
popolon has joined #linux-sunxi
cptG has quit [Ping timeout: 240 seconds]
cptG has joined #linux-sunxi
Andy-D_ has quit [Ping timeout: 240 seconds]
BenG83_ has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
Mr__Anderson has joined #linux-sunxi
jsadat has left #linux-sunxi [#linux-sunxi]
vbmithr has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
fkluknav has joined #linux-sunxi
BenG83_ has quit [Quit: Leaving]
agraf has quit [Ping timeout: 240 seconds]
agraf has joined #linux-sunxi
paulk-elm has quit [Read error: Connection reset by peer]
tkaiser has joined #linux-sunxi
<tkaiser>
Does anyone know about boot priority on Pinebook?
<tkaiser>
It seems SD card has not highest priority?
nashpa has quit [Ping timeout: 252 seconds]
<terra854>
tkaiser: SD Card is the highest piority
<terra854>
tkaiser: the pinebook will boot from SD Card if available
<tkaiser>
terra854: ok, then there's something wrong with the image on SD card :)
<terra854>
Which image are you using?
BenG83_ has joined #linux-sunxi
<tkaiser>
My own. Will have to overwrite SPL of course (forgot that).
<terra854>
Yeah, pinebook uses a diffferent boot0/spl due to the different ram type
<longsleep>
tkaiser: yes, that works on the prototype pinebook at least - new pinebook arrived today so will be doing some testing on the weekend
<tkaiser>
longsleep: Great! So I'll close the lid and wait until monday ;)
<longsleep>
tkaiser: hehe :P
<tkaiser>
Just as a reference: lsmod, dmesg and /proc/config.gz of the pre-installed Ubuntu (which uses your ppa and other stuff fortunately): http://sprunge.us/SeFX
<longsleep>
tkaiser: yes, they pretty much base on my kernel tree and build scripts which is good, but BSP is crap as always thus there are problems :)
<tkaiser>
longsleep: I thought it would be based on Kamil's forks but haven't looked that closely yet.
<longsleep>
tkaiser: yes, but that is based on mine plus patches
<tkaiser>
Anyway: works surprisingly well so far and the display is not as bad as expected :)
nashpa has joined #linux-sunxi
<longsleep>
yes - i see the potential too - if i like it good enough i might even consider rolling an image for it
<tkaiser>
longsleep: Yep, I'm currently adding battery monitoring to rpimonitor template for A64. And then it gets interesting...
<longsleep>
tkaiser: i was something about wrong device tree settings for the battery in the image they ship, so make sure you try an update (if there is one) :)
fkluknav has quit [Remote host closed the connection]
fkluknav has joined #linux-sunxi
lemonzest has quit [Quit: Leaving]
<tkaiser>
longsleep: Will have a look next week. That's the decompiled .dtb they currently ship with (-rwxr-xr-x 1 root root 70784 Apr 19 11:41 sun50i-a64-pine64-pinebook.dtb): http://sprunge.us/KUIe
<BenG83_>
morning
<BenG83_>
you guys got production PBs ?
<tkaiser>
BenG83_: I would think so, at least TL said so weeks ago.
<BenG83_>
the last one I saw of my latest shipment
<BenG83_>
8Clearance eventLEIPZIG - GERMANY09:52
<BenG83_>
(yesterday)
<BenG83_>
the current image should be based on Kamil's work
<BenG83_>
as there is nothing else that could run :P
<BenG83_>
well besides MoeIcenowy's mainline stuff
<BenG83_>
that works too
<tkaiser>
BenG83_: Well, I monitored his repos and there's not much magic involved to get Armbian legacy running on the Pinebook :) In fact we prepared the arrival months ago with armbianEnv.txt (Kamil fortunately adopted -- uEnv.txt with his image)
<BenG83_>
I think the latest work on getting suspend fixed reverted back to fex files though?
<BenG83_>
including the correct battery parameters
<BenG83_>
so recent boot-tools from ayufan should work
<BenG83_>
I haven't made a new image for myself yet
<tkaiser>
BenG83_: Ah, ok. I overlooked that completely and thought suspend/resume would still be broken. Good to know.
<jelle>
tkaiser: linux-firmware doesn't contain the right firmware for that one either :(
<tkaiser>
jelle: Xunlong now uses the newer (AP6212A IIRC) and Banana folks did the same on BPi M2+ with more recent batches. Just use the firmware from above link and rename it correctly (and send a PR agains Armbian ;) )
<jelle>
tkaiser: well I would rather have it working for everyone
<dgp>
tkaiser: I saw that. It seems like there are no well supported SDIO chips
<tkaiser>
wens: at least NanoPi Air doesn't work without attached external aerial.
<jelle>
wens: ah but the performance was weak though, not sure if it's better with an antenna
<wens>
hmm, then the opi's and bpi's probably hid an onboard antenna or trace
<jelle>
tkaiser: oh that worked for me on the neo air
<jelle>
but ~ 29kb/s or something
<tkaiser>
jelle: Performance is ok-ish but you definitely need to disable Wi-Fi powermanagement. Otherwise it sucks.
<jelle>
does anyone know how these antenna's are usually called?
<tkaiser>
jelle: the connector is called u.FL and you get 10 such things on Ali for a few bucks. And I hope FriendlyELEC now ships with an aerial by default.
<dgp>
If you have an old wifi AP around crack it open. Sometimes the secondary antenna is on a wire with an ufl connector
<jelle>
oh hehe I do actually
<dgp>
I have a linksys AP with a PCB trace antenna connected to the same PCB by coax :/
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-sunxi
lennyraposo has quit [Ping timeout: 260 seconds]
afaerber has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-sunxi
mzki has quit [Ping timeout: 268 seconds]
mzki has joined #linux-sunxi
lemonzest has joined #linux-sunxi
chomwitt has joined #linux-sunxi
deskwizard has joined #linux-sunxi
velly has quit [Ping timeout: 240 seconds]
<tkaiser>
MoeIcenowy: Thanks for the information. But I wonder why BPi folks don't implement voltage regulation (correctly)?
<MoeIcenowy>
they say that SY8106A is difficult to purchase
<tkaiser>
MoeIcenowy: They use SY8113B aren't they?
<MoeIcenowy>
yes
agraf has quit [Ping timeout: 260 seconds]
<MoeIcenowy>
but SY8113B itself didn't contain voltage adjustment
<tkaiser>
So how does Xunlong and FriendlyELEC manage to do voltage regulation with the same chip but Banana people don't?
Hao has quit [Quit: Ex-Chat]
<MoeIcenowy>
they just forgot it
Hao has joined #linux-sunxi
<MoeIcenowy>
or I doubt they got old reference designs
<tkaiser>
Or that was the last board Steven/Xunlong did for them and he was simply mean? ;)
DullTube has quit [Quit: Leaving]
agraf has joined #linux-sunxi
<MoeIcenowy>
I have saw the reference design page from BPi people
<MoeIcenowy>
it didn't contain voltage adjustment
<tkaiser>
BTW: They sent out another PCB rev 1.0 to another Armbian user who measured 1.3V back then. Maybe I'll give it a try myself. Or simply go the other direction and start to overclock my overvolted M2+
<MoeIcenowy>
but I saw two BPi people measured 1.4v on their v1.0 boards
<tkaiser>
parazyd: Which PCB revision is silkscreened on your board?
<parazyd>
where should i be looking?
<parazyd>
oh
<parazyd>
v1.1 it says
<parazyd>
BPi M2 Plus V1.1
dave0x6d has joined #linux-sunxi
<tkaiser>
At the above conrad.de link (german reseller) someone wrote: 'core voltage is fixed. I read somewhere about 1.4V but I measured 1.5V myself'. And I doubt this guy got PCB rev 1.0. Anyway: the best way to deal with Bananas is to avoid them.
<BenG83_>
:)
mhlavink has joined #linux-sunxi
<parazyd>
tkaiser: nothing that could be done in userspace to undervolt?
<MoeIcenowy>
parazyd: yes
<MoeIcenowy>
nothing
<parazyd>
(i don't know if it would help)
<MoeIcenowy>
except hardware mod
<parazyd>
oh
<KotCzarny>
bananapi org must have lots of money to burn
<tkaiser>
KotCzarny: They still have an established brand so they can sell 'superiour' hardware since all their current customers realize too late that something has changed between first A20 based Bananas and those more recent ones.
<terra854>
Just wondering though, any difference between armbianEnv.txt and uEnv.txt
<terra854>
?
<tkaiser>
Hmm... Pinebook BSP 8723cs driver seems to use random MAC addresses at every boot?
<tkaiser>
terra854: You can invent a terra854Env.txt as long as you use a boot script reading this file. That's all.
<terra854>
boot.scr?
<tkaiser>
Yep, boot.cmd/boot.scr
<MoeIcenowy>
tkaiser: yes
<MoeIcenowy>
8723cs doesn't contain EEPROM
<tkaiser>
MoeIcenowy: So for now it needs rtw_initmac at module load time and a SID based fix in driver sources, ok.
<MoeIcenowy>
for my mainline flavored version I ported the "MAC from dt" part from 8732bs driver (which is needed for 8703as, which is the same die with 8723bs in different package and without eeprom)
agraf has quit [Ping timeout: 255 seconds]
<terra854>
does current mainline work with the Pinebook fully?
<MoeIcenowy>
of course no
agraf has joined #linux-sunxi
<tkaiser>
Workaround for random MAC address on Pinebook (as root after establishing Wi-Fi the modern way): nmcli con show | grep wlan | while read ; do set ${REPLY}; nmcli con modify "$1" wifi.cloned-mac-address $(cat /sys/class/net/$4/address); done
vishnup has joined #linux-sunxi
cnxsoft has quit [Quit: cnxsoft]
cnxsoft has joined #linux-sunxi
nove has joined #linux-sunxi
cnxsoft has quit [Client Quit]
JohnDoe_71Rus has joined #linux-sunxi
vishnup has quit [Remote host closed the connection]
vishnup has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
vagrantc has joined #linux-sunxi
techping has quit [Quit: Leaving]
jernej has joined #linux-sunxi
foxx has joined #linux-sunxi
libv_ is now known as libv
vishnup has quit [Ping timeout: 240 seconds]
<itdaniher>
ah cool, not the only one with a pinebook in here
<itdaniher>
ran into that a few hrs ago, thanks tkaiser
<itdaniher>
also, I tried booting the armbian pine64 image on my pinebook, given that the screen stayed off but the pmic was active, looked like it worked
<itdaniher>
probably need to copy the dtb, possibly whatever bastard kernel they're running in the stock image
fkluknav has quit [Ping timeout: 268 seconds]
<itdaniher>
feel uncomfortable running a not-armbian build
<tkaiser>
itdaniher: Pinebook ships currently with better u-boot/kernel so I would stay with the build on eMMC for now :)
<itdaniher>
yeah, it does look like the community's done some work on it...
<itdaniher>
guess I'll wait the year or two until the a64 has solid mainline support
<itdaniher>
thanks for the advice
<itdaniher>
tkaiser: do you know where one can download the stock pinebook image? I was googling for it
<tkaiser>
itdaniher: No idea, but why not looking in Pine64 wiki and asking in their forum?
<itdaniher>
searched their wiki already
<BenG83_>
doesn't the latest image installer thing include Pinebook images? need to check
<itdaniher>
pinebook's my first pine hardware, I'm not hip to their community yet
<itdaniher>
explains why I couldn't google for it, because apparently people use electron apps instead of dd and wget
fkluknav has joined #linux-sunxi
<BenG83_>
Etcher causes a lot less trouble though regarding image flashing
<tkaiser>
itdaniher: Which is great since so many accidents happen when people use dd without verify. That's the reason stuff like Etcher was needed. Since so many problems with broken OS image burning can be avoided by a verify
<BenG83_>
you wouldn't believe how many people fail to flash raw images
<tkaiser>
you wouldn't believe how many crappy card readers/writers exist and how many crappy SD cards.
<itdaniher>
gotcha
<itdaniher>
yeah, supporting people using dd by hand sounds painful
<itdaniher>
I've fucked up burning images before, and I'm almost competent
<nove>
after all this years, there is finally a move to more collaboration for using GNU in mobile devices -> halium.org
<nove>
but by using libhydris and the android vendor kernels, i am of the opinion that it will not go very far
lurchi__ has quit [Ping timeout: 268 seconds]
lkcl has quit [Ping timeout: 260 seconds]
kloczek has joined #linux-sunxi
matthias_bgg has quit [Quit: Leaving]
lurchi__ has joined #linux-sunxi
<MoeIcenowy>
There's never a new Nokia N900 ;-)
<MoeIcenowy>
P.S. However I'm trying to get Replicant to run on sunxi devices
<MoeIcenowy>
Currently we still have to admit that Android-based mobile solutions are more mature
dev1990 has joined #linux-sunxi
<dgp>
Not sure I see the point in a GNU mobile OS when all the shit you really have to worry about is in the vendors blobs for the radio
<itdaniher>
mobile protocol stacks are a mess
<itdaniher>
it's not like there aren't libre alternatives, it's that nobody wants to carry a usrp and i7 (and probably commit a felony in the US) to call family without vendor blobs
<dgp>
mobile protocol stacks are a mess, the firmware that runs on most wifi chips is a scary mess..
<dgp>
NFC controller firmware is probably a crazy mess
<Ke>
you could still isolate the modem
<Ke>
having hostile modem is not much worse than hostile internet in general
<Ke>
as long, as it works
lkcl has joined #linux-sunxi
<KotCzarny>
and as long its not the master of the device
<KotCzarny>
;)
<Ke>
sure
<nove>
I think the problem is that everyone is trying to make their Mobile OS and not distributions, where the user is free to choose which distribution (and not OS) to run in their device
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
<MoeIcenowy>
In fact at least there's some GSM modules that have the firmware in their internal ROM
<MoeIcenowy>
and can be interfered with directly AT commands
quard has joined #linux-sunxi
<nove>
why not: emerge android or apt-get android or whatever other
<BenG83_>
there are a lot of such devices, they are just not economical for volume handsets
<dgp>
nove: The bit you see on the screen isn't the problem really. It's all the stuff to make it work with the hardware in question
yann|work has quit [Ping timeout: 260 seconds]
<Ke>
I guess the problem is cramming anything reasonable to resonable form factor phone and still have at reasonable price with low production volumes
tkaiser has quit [Ping timeout: 268 seconds]
<nove>
supposedly android uses the same linux kernel and the only thing that stops changing what is seen in the screen, is software politics
popolon has quit [Quit: WeeChat 1.7.1]
chomwitt has quit [Ping timeout: 240 seconds]
<Ke>
nove: some obsolete kernel that is full of holes
<dgp>
Ke: android 7 is a recent kernel
fkluknav has quit [Ping timeout: 260 seconds]
<dgp>
nove: A lot of android is in the userland and where kernel stuff is used there are bits that have been changed to make the userland and kernel interaction better
<nove>
the binary blobs, the non "standard" interfaces, the "myMobile OS" is all software politics
mossroy has quit [Quit: Leaving]
<dgp>
not really. Android as a desktop environment on a totally vanilla kernel and base userland would be pretty horrible
<dgp>
Good example is how insanely awful bluetooth was/still is on most linux distros. It works pretty well for decent (not random chinese vendor) android devices because of all the stuf they did to integrate the kernel, bluez and the android userland
<nove>
exactly that is the problem, the linux kernel is forked to had non standard interfaces to run only the myMobile OS
tkaiser has joined #linux-sunxi
<dgp>
Go over dramatic much?
<dgp>
As long as the source for the kernels ends up somewhere no one should care. If you want to take the work Google did on the kernel for your mobile OS you are free to do so
<tkaiser>
But you should measure before and report back.
<parazyd>
indeed
<parazyd>
will do that when i'm at a place with a multimeter. none at home atm
<MoeIcenowy>
P.S. BPi people said to send me a BPi M2+
lurchi__ has joined #linux-sunxi
<KotCzarny>
tkaiser: did you see on that page: According to the AW's whitepaper H3 should work at 1.008GHz max_freq, but I tested ok with the 1.2GHz sys_config.
<KotCzarny>
har, har
<MoeIcenowy>
KotCzarny: you didn't check the context
<MoeIcenowy>
he means that in 1.2v the maximum is 1.008GHz
<KotCzarny>
ahm
<KotCzarny>
you are right
<MoeIcenowy>
P.S. my Nano Pi NEO2 precisely fail on 1.008GHz @ 1.1v ;-)
<tkaiser>
MoeIcenowy: _Fails_? With which workload?
<MoeIcenowy>
tkaiser: no workload
Mr__Anderson has quit [Remote host closed the connection]
<MoeIcenowy>
only try booting
<MoeIcenowy>
or I should say the workload is "load U-Boot ITB from MMC by SPL"
<tkaiser>
Hmm... I'm confused. 1.1V is the only voltage available here, right?
<MoeIcenowy>
yes
<MoeIcenowy>
and when I set the bootup voltage of SPL to 1008MHz it sometimes fail to boot
<tkaiser>
What is default 'voltage'? ;)
<KotCzarny>
hmm, according to aw notes, 1.1v is 648..816 range
<MoeIcenowy>
?
<MoeIcenowy>
KotCzarny: yes so 1.008GHZ @ 1.1v is not so proper
<tkaiser>
You wrote voltage but meant clockspeed? And I wonder which is default clockspeed.
<MoeIcenowy>
yes I mean clockspeed
<MoeIcenowy>
the default in CCU register is 432MHz
<MoeIcenowy>
very failsafe one ;-)
<tkaiser>
MoeIcenowy: Thanks, then I draw wrong conclusions and spread some BS in the meantime :)
<MoeIcenowy>
?
<tkaiser>
I thought H5 would be fine running with 1008 MHz at 1.1V. Since missing 'default in CCU register is 432MHz'
<MoeIcenowy>
why?
kloczek has quit [Read error: Connection reset by peer]
<tkaiser>
Wrong assumptions. Don't get it now why :)
yann|work has joined #linux-sunxi
<MoeIcenowy>
P.S. currently the default frequency which will be set by U-Boot SPL is still 1.008GHZ
<MoeIcenowy>
GHz
<MoeIcenowy>
which may lead some bad NEO2 (e.g. mine) to boot fail
tkaiser has quit [Ping timeout: 268 seconds]
BenG83_ has quit [Quit: Leaving]
dave0x6d has quit [Quit: Connection closed for inactivity]
[Awaxx] has quit [Quit: To dark to light, to light to dark]
vagrantc has quit [Ping timeout: 260 seconds]
Andy-D_ has joined #linux-sunxi
lkcl has quit [Ping timeout: 260 seconds]
gzamboni has quit [Remote host closed the connection]
vagrantc has joined #linux-sunxi
[Awaxx] has joined #linux-sunxi
paulk-collins has quit [Quit: Leaving]
lkcl has joined #linux-sunxi
vagrantc has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-sunxi
lkcl has quit [Ping timeout: 240 seconds]
scream has joined #linux-sunxi
Char0n has quit [Ping timeout: 240 seconds]
lkcl has joined #linux-sunxi
kloczek has joined #linux-sunxi
lkcl has quit [Read error: Connection reset by peer]
kloczek has quit [Ping timeout: 260 seconds]
netlynx has quit [Quit: Ex-Chat]
Nacho has quit [Remote host closed the connection]
Nacho has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
iamfrankenstein has joined #linux-sunxi
kloczek has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]