ikmaak has quit [Remote host closed the connection]
ikmaak has joined #linux-sunxi
perr has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-sunxi
lamer14925527821 has joined #linux-sunxi
lamer14925527821 has quit [Ping timeout: 240 seconds]
ikmaak has quit [Remote host closed the connection]
ikmaak has joined #linux-sunxi
wzyy2 has joined #linux-sunxi
terra854 has joined #linux-sunxi
fl_0 has joined #linux-sunxi
fl__0 has quit [Ping timeout: 240 seconds]
bparker has quit [Ping timeout: 240 seconds]
bparker has joined #linux-sunxi
Keziolio has quit [Quit: No Ping reply in 180 seconds.]
xes has quit [Ping timeout: 240 seconds]
lamer14925527821 has joined #linux-sunxi
Keziolio has joined #linux-sunxi
Keziolio has joined #linux-sunxi
Keziolio has quit [Changing host]
xes has joined #linux-sunxi
lamer14925527821 has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-sunxi
egbert_ has joined #linux-sunxi
egbert has quit [Disconnected by services]
<wens>
MoeIcenowy: afaik there's a framework for loading firmware into coprocessors in the kernel
<wens>
maybe it wasn't merged
<kilobyte>
for any kind of firmware, or even arbitrary blobs of data
<kilobyte>
the userspace must be up at that time, though
ninolein_ has joined #linux-sunxi
<kilobyte>
actually, looks like it's possible to read it directly from a fixed place on the filesystem (which might be an initrd)
ninolein has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-sunxi
Andy-D has quit [Ping timeout: 255 seconds]
lamer14925527821 has joined #linux-sunxi
lamer14925527821 has quit [Ping timeout: 252 seconds]
<swiftgeek>
i hope somebody will document how to do it :>
terra854 has quit [Quit: Connection closed for inactivity]
victhor has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-sunxi
lamer14925527821 has joined #linux-sunxi
lamer14925527821 has quit [Ping timeout: 255 seconds]
terra854 has joined #linux-sunxi
liushuyu has joined #linux-sunxi
liushuyu has left #linux-sunxi [#linux-sunxi]
itdaniher has joined #linux-sunxi
lkcl has quit [Ping timeout: 240 seconds]
pg12_ has quit [Ping timeout: 240 seconds]
reev has joined #linux-sunxi
pg12 has joined #linux-sunxi
<itdaniher>
anyone have experiences they'd like to share wrt A64 close-to-mainline kernels? expecting my pinebook shortly, will be my first A64 machine.
<itdaniher>
probably my first 64b ARM running anything besides ios or android
lkcl has joined #linux-sunxi
liushuyu_ has quit [Ping timeout: 252 seconds]
Hao has joined #linux-sunxi
lurchi__ has quit [Read error: Connection reset by peer]
lurchi__ has joined #linux-sunxi
lamer14925527821 has joined #linux-sunxi
lamer14925527821 has quit [Ping timeout: 260 seconds]
TheSeven has quit [Ping timeout: 255 seconds]
TheSeven has joined #linux-sunxi
reev has quit [Read error: Connection reset by peer]
reev has joined #linux-sunxi
lennyraposo has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
jernej has joined #linux-sunxi
tllim has joined #linux-sunxi
<tllim>
@itdaniher, check with BenG83, he has teh Pinebook mainline build that contribute by Icenowy.
<plaes>
actually, there are two SATA related issues in this letter
Andy-D_ has joined #linux-sunxi
Andy-D has quit [Ping timeout: 240 seconds]
massi has joined #linux-sunxi
LargePrime has quit [Ping timeout: 260 seconds]
matthias_bgg has joined #linux-sunxi
<wens>
plaes: first, pll-periph-sata should be a gate + divider + fixed post divider
<wens>
so just like the old clock driver, you need pll-periph-base, which is 24M * N * K
<wens>
pll-periph-base = pll-periph-base / M / 6
<wens>
oops, meant pll-periph-sata = pll-periph-base / M / 6
<wens>
pll-periph = pll-periph-base / 2
fkluknav has quit [Ping timeout: 260 seconds]
<wens>
then sata = mux( pll-periph-sata , sata-ext ) + gate
kloczek has quit [Quit: kloczek]
kloczek has joined #linux-sunxi
LargePrime has joined #linux-sunxi
kloczek has quit [Ping timeout: 258 seconds]
Andy-D_ has quit [Ping timeout: 260 seconds]
kloczek has joined #linux-sunxi
fkluknav has joined #linux-sunxi
<plaes>
k, thanks :)
kloczek has quit [Ping timeout: 252 seconds]
kloczek has joined #linux-sunxi
simosx has quit [Quit: Yakkety Bye!]
kloczek has quit [Quit: kloczek]
<diego_r>
Hi guys, is there a software way, better if from Linux, to tell which revision of a board I'm running? I'm particularly interested in Olinuxino A20 Lime2
BenG83 has joined #linux-sunxi
<KotCzarny>
nope, unless you find yourself what features are different between revisions and probe/compare them yourself
orn has joined #linux-sunxi
<diego_r>
KotCzarny: understood. no magic fuse bit or stuff like that so...
fkluknav has quit [Ping timeout: 245 seconds]
<orn>
Hi, first post here. Does anyone here have experience with bluetooth drivers for rtl8723bs? I'm trying backports now.
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
<wens>
MoeIcenowy: ^
kloczek has joined #linux-sunxi
<KotCzarny>
hmm, what does PSCI field in status matrix mean? relying on uboot setting it or something else?
<wens>
U-boot provides PSCI support
Hao has quit [Ping timeout: 240 seconds]
fkluknav has joined #linux-sunxi
<plaes>
diego_r: you might want to try #olimex
kloczek has quit [Quit: kloczek]
lemonzest has joined #linux-sunxi
wzyy2 has quit [Ping timeout: 260 seconds]
vickycq- has quit [Read error: Connection reset by peer]
vickycq- has joined #linux-sunxi
libv_ is now known as libv
orn has quit [Ping timeout: 255 seconds]
Turl has quit [Quit: >.<]
Turl has joined #linux-sunxi
fkluknav has quit [Ping timeout: 255 seconds]
reev has quit [Remote host closed the connection]
reev has joined #linux-sunxi
kloczek has joined #linux-sunxi
wzyy2 has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
mbeldyga has joined #linux-sunxi
Hao has joined #linux-sunxi
tlwoerner has quit [Quit: Leaving]
cptG_ has joined #linux-sunxi
<diego_r>
plaes: thanks for the hint
cptG has quit [Ping timeout: 240 seconds]
orn has joined #linux-sunxi
Hao has quit [Quit: Ex-Chat]
Hao has joined #linux-sunxi
fkluknav has joined #linux-sunxi
<lvrp16>
damn shenzhen and it's mosquitos, eating me alive
rpd_ has joined #linux-sunxi
<rpd_>
clear
Hao has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 252 seconds]
<rpd_>
hi, I have run into the dreaded network issue with Pine64 board, but don't understand it fully, is it a hardware issue or something I can correct by using the right build/os?
<lvrp16>
2GB?
<rpd_>
yeah
<MoeIcenowy>
what issue?
<MoeIcenowy>
link is up but cannot transmit data
<MoeIcenowy>
?
<lvrp16>
A64 + 2GB + Ethernet, i thought that problem was resolved long ago?
<MoeIcenowy>
not on mainline.
<rpd_>
it seems to drop packets, initially the connection starts fine, then degrades until it stalls
<rpd_>
I was able to boot "pine64-image-debianbase-310102bsp-2.img", but it is not booting latest armbian release for pine64, considering it boots the other, I am guessing its not a sdcard/power issue, so am a bit clueless as to what to do
<MoeIcenowy>
what's the kernel version?
<rpd_>
I think it is 3.10.102-BSP-2
<MoeIcenowy>
3.10.102... seems a bit old BSP variant
<MoeIcenowy>
for BSP problems please go #Pine64 on irc.pine64.xyz
<MoeIcenowy>
not here
<rpd_>
ok thanks, can you recommend a more recent image I can try
<MoeIcenowy>
I don't know...
<rpd_>
if I build my own using dbootstrap on a vm would that be one way to go?
<IgorPec>
sorry, i saw you are having troubles ... strange
<rpd_>
IgorPec: thanks, I am actually trying to work through your suggestions online, I downloaded Debian_jessie_default.7z, but my board is not booting that image...
orn has quit [Ping timeout: 240 seconds]
<IgorPec>
ok. sorry, don't have pine64 to checkup. better ask / check on forum.armbian.com
<rpd_>
IgorPec: yes let me try other images like Ubuntu and see how it goes, trying to stick to debian due to as wanted to integrate into a dev cluster, lets see...
fkluknav has quit [Ping timeout: 258 seconds]
<IgorPec>
let's move our chat to #armbian since this channel is not covering this topic
<rpd_>
ok will do thanks!
lkcl has joined #linux-sunxi
mhlavink has quit [Ping timeout: 255 seconds]
tlwoerner has joined #linux-sunxi
orn has joined #linux-sunxi
<BenG83>
MoeIcenowy, did you have any luck reproducing GbE issues
fkluknav has joined #linux-sunxi
reev has quit [Ping timeout: 240 seconds]
DullTube has quit [Quit: Leaving]
f0xx has joined #linux-sunxi
<wens>
oh wow, rtl8723bs in staging
<BenG83>
oh wow
<MoeIcenowy>
BenG83: yes
<MoeIcenowy>
with the board from my friend
<BenG83>
because I have seven boards now from different batches and they all work with GbE regardless of kernel version
<BenG83>
I have yet to find one that doesnt work
<KotCzarny>
beng83: try with weak psu maybe?
<MoeIcenowy>
KotCzarny: it's not a PSU problem.
<KotCzarny>
i remember someone mentioning that rmi wasnt powered enough with weak psu
<rpd_>
longsleep: thanks, interesting stuff..., I notice that the yellow led blinks a lot more erratically than the green one, which is odd compared to rest of the sbc boards I have
<IgorPec>
we use the same kernel
<IgorPec>
sorry
orn has quit [Ping timeout: 245 seconds]
<BenG83>
longsleep, afaik it does the same as pulling down the RXDLY pin which is usually only power-on configurable
<BenG83>
28
<BenG83>
RGMII Receiver Clock Timing Control.
<BenG83>
1: Add 2ns delay to RXC for RXD latching
<BenG83>
O/LI/PD
<BenG83>
RXDLY
<BenG83>
e.g. disabling that 2ns fixed delay
<BenG83>
which offsets the registers tuning range
cnxsoft has quit [Quit: cnxsoft]
fkluknav has joined #linux-sunxi
<wens>
montjoie: why do you call sun8i_dwmac_reset() in sun8i_power_phy()?
<wens>
and sun8i_dwmac_reset should be sun8i_dwmac_dma_reset
mbeldyga has quit [Ping timeout: 260 seconds]
mhlavink has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
orn has joined #linux-sunxi
<rpd_>
see you folks again!
rpd_ has left #linux-sunxi [#linux-sunxi]
fkluknav has quit [Ping timeout: 260 seconds]
Andy-D_ has joined #linux-sunxi
f0xx has joined #linux-sunxi
jernej has joined #linux-sunxi
orn has quit [Ping timeout: 255 seconds]
orn has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
Andy-D_ has quit [Ping timeout: 240 seconds]
Nacho__ has joined #linux-sunxi
Nacho_ has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 260 seconds]
komunista has joined #linux-sunxi
<orn>
exit
maz has quit [Quit: Leaving]
maz has joined #linux-sunxi
orn has left #linux-sunxi [#linux-sunxi]
fl_0 has quit [Quit: STRG + Q]
f0xx has quit [Ping timeout: 252 seconds]
fl_0 has joined #linux-sunxi
kloczek has quit [Ping timeout: 240 seconds]
tillz has joined #linux-sunxi
tillz is now known as tillzz
<tillzz>
Hi there, is someone here who knows a bit about the SPI drivers for sun8i SoCs? I'm experiencing a strange problem with the Linux Mainline Driver (which doesn't appear in sunxi-linux), and i'd like to find out the reason to be able to fix it.
pg12 has quit [Ping timeout: 240 seconds]
pg12 has joined #linux-sunxi
<TheLinuxBug>
tillzz: they answer is probably yes, there is someone, however, you will need to hang out and wait a while if you want a reply, people here are in a wide variety of time zones and may not see your request for a while.
<tillzz>
@TheLinuxBug yeah, didn't expect sth different ;-)
<TheLinuxBug>
Just making sure you were aware and didn't just /quit in 5 minutes ;p
<TheLinuxBug>
can't tell you number of times that happens and someone answers the question like 10 minutes later
kloczek has joined #linux-sunxi
<MoeIcenowy>
tillzz: which sun8i?
<tillzz>
H3
reinforce has joined #linux-sunxi
<MoeIcenowy>
what's your slave?
<MoeIcenowy>
Currently (4.11 and former) spi-sun6i cannot do transfers larger than chip's FIFO
<tillzz>
As far is i can see, the mainline driver is just the sun6i with a few patches. My Slave is an AVR µC which I want to program
<MoeIcenowy>
what patches?
<MoeIcenowy>
I think for spi-sun6i to support larger transfers two patches are needed
<tillzz>
yes, know that… But that's not the problem… I observed the whole bus, and there's a really short pulse one the SCK line before the `real` SCK clock starts
<tillzz>
yeah, this won't be a problem in most use cases, as the CS is still high at this pulse, but the AVR's synchronize their clock to the length of the first pulse… and as this is simply so short, they're switching to 'failure' mode
<montjoie>
wens: you got that on which board?
perr has quit [Quit: Leaving]
<montjoie>
wens: the first message is just a warning, uboot certainly leave emac enabled
<montjoie>
wens: the sun8i_dwmac_reset is needed for let MAC seee the syscon value change
kloczek has quit [Quit: kloczek]
<dgp>
tillzz: if you don't need performance bitbang spi on the same pins could work for now
kloczek has joined #linux-sunxi
<tillzz>
yeah, doing that at the moment without problems, but my goal is not 'just getting it to work' ;-) Especially when i add more slaves to the bus, that's going to be a really hacky solution, to switch between native-spi & bitbang.
<wens>
montjoie: h3 orange pi pc
<wens>
montjoie: then that warning is kind of useless :p
<wens>
montjoie: syscon value change?
<wens>
found a few more cleanups
<wens>
like you don't need to check if the pointer is valid for clk_* and reset_control_* calls
<wens>
they ignore NULL pointers
<wens>
and you don't need to take stmmaceth clock, it's done by the driver library
<dgp>
tillzz: how fast is the clock. You could fix it with some 74 series logic too :D
<dgp>
I don't remember seeing weird clock pulses like that when messing around with the spi controller to make a crappy uboot driver for it
<tillzz>
3000Hz, slowest possible (but tried many different speeds)
<montjoie>
wens: strange my opipc work
<tillzz>
dgp damn… where can i find the code of that driver? Already compared differences between mainline and sunxi, proably a minimal driver would help ;-)
kloczek has quit [Read error: Connection reset by peer]
indy has joined #linux-sunxi
popolon has joined #linux-sunxi
kloczek has joined #linux-sunxi
fkluknav has joined #linux-sunxi
<swiftgeek>
do i see correctly that 8189FTV has no blobs?
<tillzz>
ssvb: Thanks, no, didn't see it - I searched explicit for the H3, but of course it's likely to appear on other SoCs too. I'll then play a bit with the driver…
BenG83 has joined #linux-sunxi
<KotCzarny>
swiftgeek: on android there is some fw file, but is it used..
<KotCzarny>
who knows what is it for
<BenG83>
o/
<swiftgeek>
KotCzarny: perhaps update? it's hard to tell without any datasheet :<
IgorPec has quit [Ping timeout: 240 seconds]
<KotCzarny>
no, its a tiny file
<swiftgeek>
then regdomain/calibration for sure
<swiftgeek>
or ROM patch :P
<swiftgeek>
btw what's the jwrdegoede nick here?
IgorPec has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-sunxi
yann|work has quit [Ping timeout: 255 seconds]
popolon has quit [Ping timeout: 258 seconds]
kloczek has quit [Remote host closed the connection]
popolon has joined #linux-sunxi
kloczek has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-sunxi
lkcl has quit [Ping timeout: 260 seconds]
wzyy2 has quit [Remote host closed the connection]