pietrushnic`away has quit [Ping timeout: 252 seconds]
pietrushnic`away has joined #linux-sunxi
engideavr has quit [Ping timeout: 252 seconds]
engidea-vr has joined #linux-sunxi
fest has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
bwarff has joined #linux-sunxi
khuey is now known as khuey|away
mosterta|2 has quit [Ping timeout: 276 seconds]
mosterta|2 has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
ninolein_ has quit [Ping timeout: 268 seconds]
ninolein has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
mosterta|2 has quit [Read error: Connection timed out]
mosterta|2 has joined #linux-sunxi
mosterta has joined #linux-sunxi
mosterta|2 has quit [Ping timeout: 276 seconds]
p1u3sch1 has quit [Ping timeout: 276 seconds]
p1u3sch1_ has joined #linux-sunxi
SMD has joined #linux-sunxi
SMD is now known as Guest74059
keh has quit [Ping timeout: 244 seconds]
Guest74059 has quit [Remote host closed the connection]
reev has joined #linux-sunxi
fredc has joined #linux-sunxi
SMDhome has joined #linux-sunxi
tsuggs has quit [Ping timeout: 268 seconds]
tsuggs has joined #linux-sunxi
tsuggs has quit [Ping timeout: 260 seconds]
tsuggs has joined #linux-sunxi
<KotCzarny>
woo hoo usb planned for h3 in 4.7 :)
IgorPec has joined #linux-sunxi
IgorPec has quit [Ping timeout: 250 seconds]
reinforce has joined #linux-sunxi
avph has quit [Ping timeout: 250 seconds]
<mripard>
wens: there's still no fix for that?
premoboss has quit [Remote host closed the connection]
avph has joined #linux-sunxi
<wens>
mripard: fix is in 4.6-rc2
<wens>
don't know about stable
<mripard>
it doesn't look like it was flagged for stable
<wens>
i think it was a slightly large series :(
kaspter has quit [Ping timeout: 244 seconds]
Guest19030 is now known as fredy
paulk-collins has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 246 seconds]
apritzel has joined #linux-sunxi
kaspter has joined #linux-sunxi
kaspter has quit [Ping timeout: 250 seconds]
IgorPec has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
fl_0 has quit [Quit: STRG + Q]
fl_0 has joined #linux-sunxi
yann|work has quit [Ping timeout: 260 seconds]
tomboy64 has joined #linux-sunxi
yann|work has joined #linux-sunxi
apritzel has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 260 seconds]
<wens>
from what i heard, h8 and a83t are identical, except for the chip IDs, and marketed to different markets
Rondom has quit [Remote host closed the connection]
<plaes>
are there any H8 devices?
Rondom has joined #linux-sunxi
<wens>
the cubietruck plus is h8
<buZz>
man
<buZz>
i -so- hope someone is gonna make a allwinner 'cpuboard' for the upcoming Pyra handheld :D
JohnDoe_71Rus has joined #linux-sunxi
bwarff has quit [Read error: Connection reset by peer]
bwarff has joined #linux-sunxi
<KotCzarny>
buzz: you know that for handhelds expected standby/idle power usage should be ~10mA? and that most (all?) allwinner boards suck ~200-500mA in idle?
<plaes>
well.. power management hasn't been implemented yet
<buZz>
KotCzarny: i have near infinite batteries ;)
<KotCzarny>
riiiiight
<KotCzarny>
cosmic power powered?
bwarff has quit [Read error: Connection reset by peer]
<NiteHawk>
homebrew fusion plant?
bwarff has joined #linux-sunxi
Worf has joined #linux-sunxi
<KotCzarny>
beer wont work as an arm power source
tkaiser has joined #linux-sunxi
<tkaiser>
wens: plaes: There's another one. And the boot0 BLOB checks the SoC ID: http://forum.linksprite.com/index.php?/topic/4516-lm-sensors-no-worky/#entry12084
<buZz>
KotCzarny: nah, just near constant influx of 'broken laptop batteries' which usually have ~6 cells, of which 1-2 is bad
<wens>
tkaiser: yup, the r58? also heard about the check in boot0
<tkaiser>
wens: plaes: So in Allwinner's BSP the boot0 BLOB is not only initializing DRAM but does also marketing stuff
<wens>
more like market segmenting stuff :p
<tkaiser>
wens: True! :) PcDuino 8 Uno is using H8, I've not seen any R58 device in the wild except of BPi-M3-R
JohnDoe71rus has joined #linux-sunxi
<tkaiser>
SinoVoip also did a M3 variant using R58 and confirmed that u-boot 2016.05-rc1 happily boots all three SoCs
JohnDoe_71Rus has quit [Ping timeout: 244 seconds]
<tkaiser>
Also according to SinoVoip they release different 'SDKs' for all three chips and do for example not 'allow' Android 5.x running on H8
mosterta has quit [Read error: Connection timed out]
mosterta has joined #linux-sunxi
<tkaiser>
Seems Allwinner produces one single SoC with three different names, assigns different chip IDs and business units and then they do what they want
<lennyraposo>
hey tkaiser
<lennyraposo>
I was already caught up with the posts you sent mate
<tkaiser>
lennyraposo: No, please no Pine64 stuff. I'm done with that
<lennyraposo>
no worries mate
kaspter has joined #linux-sunxi
bfree has joined #linux-sunxi
<lennyraposo>
but there is one thing that isn't pine specific
<tkaiser>
lennyraposo: Pine64 + mainline kernel == ok, everything else not interesting any more
<KotCzarny>
hehe
<lennyraposo>
and it's if anyoen puts out a SBC things should be in place to maintain knowledge base
<lennyraposo>
;)
<KotCzarny>
someone should add 'no legacy kernels/bsp related topics' to the channel topic
<lennyraposo>
that's up to me right now
<lennyraposo>
hence the more refined system I am setting up
<lennyraposo>
should be a little more helpful in terms of quality control
<lennyraposo>
it's too difficult to navigate the forums there now
<lennyraposo>
abotu 30 different threads for the same issues
apritzel1 has joined #linux-sunxi
<tkaiser>
lennyraposo: I know, but this will not change. It's the Pine64 folk that do not want to document the mess, they created. Fragmenting documentation at pine64.pro or eLinux.org isn't a solution either. And our wiki allows stuff like http://linux-sunxi.org/Pine64/99_Reasons_why_this_board_will_not_boot already ;)
<tkaiser>
wens: SinoVoip said they send also a BPi M3 to Hans. Do you know of others?
enrico_ has joined #linux-sunxi
<wens>
tkaiser: vishnu
<wens>
foxconn people also mentioned a80 is discontinued :(
<buZz>
is eh, CHIP shipping yet?
<buZz>
ah, nope
<tkaiser>
wens: I'm a bit concerned the same might happen with A83T/R58/H8/insert-your-favourite-business-unit-here again
<mripard>
buZz: it's shipping to the backers
<buZz>
yeh
<mripard>
but it shouldn't be very far from the last batch
<tkaiser>
SoC discontinued too early
<mripard>
so it will probably change quite soon
<tkaiser>
mripard: Is it too early to ask for performance of CHIP's NAND implementation?
<buZz>
i know some backers that have theirs already
<buZz>
but i want to just order and get it, not fund some 'maybe' thing
mosterta has quit [Read error: No route to host]
mosterta has joined #linux-sunxi
<wens>
tkaiser: there's a chance a83t will be long term
<KotCzarny>
i wouldnt mind octacore thingie
<KotCzarny>
btw. who can fix wiki nazi email filter?
ricardocrudo has quit [Remote host closed the connection]
<tkaiser>
wens: Hmm... according to TL Lim the R series is expected to get long term support but anyway. Until now the three available A83T/H8 devices aren't that great either
<bbrezill1>
tkaiser: I don't know, and honnestly that's not my priority :)
<bbrezill1>
but you can test it ;)
<tkaiser>
bbrezill1: I'm really interested especially in random I/O with small record sizes. Given the CHIP's price I think also it's the best to test it myself (and then get back and on your nerves ;) )
<bbrezill1>
I recently optimized raw perfs by using DMA in the sunxi NAND driver
<bbrezill1>
but not sure how much it improves perfs at the FS lavel
<bbrezill1>
level
<KotCzarny>
more cpu available = more fun
<bbrezill1>
and there's still room for improvement (next step => supporting DDR mode, I already made a prototype, but I need to clean it up)
<tkaiser>
bbrezill1: Do you only test sequential performance or random as well? Or neither/nor due to different priorites?
<wens>
not fun if it get's killed half way through :p
<KotCzarny>
unless calling dma is slow and bottlenecking
<bbrezill1>
tkaiser: mainly sequencial perfs, but given to the way we're currently interfacing with the NAND chip, I don't expect any difference between sequencial and random accesses
tkoskine has quit [Ping timeout: 276 seconds]
<bbrezill1>
(we're not making use of cached or multi-plane accesses optims, but that's on my TODO list too)
<tkaiser>
bbrezill1: Thx, then I will keep in mind that this is still WiP :)
<bbrezill1>
tkaiser: any help is welcome
<bbrezill1>
;)
<bbrezill1>
if you have to time to bench the current implementation it would be a good start
<tkaiser>
bbrezill1: Only 'help' I can provide is the iozone call above and the recommendation to always test different record sizes ;)
JohnDoe71rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
avph has quit [Ping timeout: 250 seconds]
merbanan has quit [Remote host closed the connection]
avph has joined #linux-sunxi
scott_ has joined #linux-sunxi
scott_ is now known as Guest96896
solarnetone has quit [Ping timeout: 276 seconds]
kasper has joined #linux-sunxi
<kasper>
hi, can i change dram clk in script.bin or should i recompile uboot?
mosterta has quit [Read error: Connection timed out]
mosterta has joined #linux-sunxi
Incursion has joined #linux-sunxi
<Amit_T>
Not sure but I think there are some test cases where you can run u-boot with different dram clk (which particular clock you are looking for)
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
<kasper>
ok thx
kasper has quit [Quit: Page closed]
tkaiser has joined #linux-sunxi
merbanan has joined #linux-sunxi
prasannatsm has joined #linux-sunxi
prasannatsm has quit [Client Quit]
prasannatsm_ has joined #linux-sunxi
<prasannatsm_>
I have an infocus firefox os tablet, it has Allwinner A31. I would like to work on one-wire task. Can anyone explain what it is and what is pending to be done?
* willmore
doesn't have one and still appreciates linux-sunxi
<KotCzarny>
oh, wow, my opipc power adapter died
tomboy64 has quit [Ping timeout: 252 seconds]
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
<willmore>
I just read that un-review. What kind of screaming noob is that person? You want to run a desktop environment on a 512MB dev board on day one and expect it to be flawless?
<willmore>
plaes, I think linux-sunxi is *lucky* not to have been mentioned in that article. It was so negative and the author so ignorant, you don't want to be associated with that.
<lvrp16>
willmore: we handle support for orange pi from customers and the raspberriness of their minds are bespoke
IgorPec has joined #linux-sunxi
<KotCzarny>
willmore: you CAN run desktop happily on 64M, just dont expect to run any productive apps ;)
<lvrp16>
willmore: why can't I run raspbian on my orange pi is like the #1 question
<willmore>
lvrp16, SMH
<lvrp16>
the other thing is GPIO, people can't use sysfs for GPIO...
<willmore>
KotCzarny, Hey, I ran a desktop in 16M in '92 on my AMD 386DX40, so yeah, I know you can do it. ;) I'm just saying things have changed a bit since then.
cosm_ has quit [Ping timeout: 276 seconds]
<lvrp16>
they must use "WiringPi"
<ssvb_>
willmore: to be honest, the desktop 2D performance is not particularly stellar yet, because of missing 64-bit ARM assembly in a few places
<ssvb_>
willmore: this is going to be addressed soonish
<willmore>
ssvb_, I was thinking the amount of memory won't get you far with something like Unity.
<willmore>
Your 2D work is great.
prasannatsm has quit [Ping timeout: 246 seconds]
<KotCzarny>
+1
<willmore>
lvrp16, I've never done GPIO on a PI, but I know there a half billion ways to do it it. So, I'm not surprised that all of them (most made up from scratch (pardon the pun) on the pi) aren't supported well elsewhere.
<ssvb_>
well, using XFCE, LXDE or MATE makes more sense on such systems
<KotCzarny>
or fluxbox
<willmore>
Agreed. Heck, I use XFCE on my full fat laptop.
<KotCzarny>
or matchbox
<willmore>
I've got 16GB in here. I use it because it's better at what I want than GNOME.
fredy has quit [Excess Flood]
<willmore>
Also, when I have issues, I can go to the #xfce channel and ask questions of the actual developers *who listen* and correct me if I'm doing it wrong or *fix it* if they did.
<willmore>
GNOME devs don't do either of those things.
fredy has joined #linux-sunxi
<plaes>
you have to know the right people :P
tomboy64 has joined #linux-sunxi
<KotCzarny>
gnome is just part of evil empire these days
<willmore>
plaes, if that's how they want it, then they can keep it.
<willmore>
I'm not going to play that game.
<KotCzarny>
one funny note of that un-review: The board itself is bent in the middle
<KotCzarny>
;)
<willmore>
KotCzarny, so are both of my Opi1. That 40 pin connector was soldered by people who aren't used to through-hole.
<KotCzarny>
willmore, slanted connector is one thing, bent mobo is the whole new world of wtf
<KotCzarny>
but i bet on the sloppy shipping
<willmore>
KotCzarny, look at the picture in the article, it's bent only along the length of the 40 pin connector.
<KotCzarny>
picture is blurry, but tkaiser was hit but a more severe bentywtfness
<KotCzarny>
they first shipped boards without any carton or stiffiness
<KotCzarny>
just plain envelope
libv has quit [Ping timeout: 246 seconds]
libv has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 244 seconds]
apritzel has quit [Ping timeout: 244 seconds]
prasannatsm has joined #linux-sunxi
<prasannatsm>
I have an infocus firefox os tablet, it has Allwinner A31. I would like to work on one-wire task. Can anyone explain what it is and what is pending to be done?
<kdubious>
that says: Easy Tasks - One Wire / 1-Wire (dedicated HW only present on A31/A80)
<prasannatsm>
Found about 1-wire interface from the above link. Wiki page https://linux-sunxi.org/1-Wire shows how to use it. I am wondering what has to be done.
<ssvb_>
prasannatsm: just to make sure that you can run some system on this tablet first :-)
<prasannatsm>
I am looking at them
<kdubious>
I *think* 1-wire is working with the legacy kernel, but needs the driver to be written for the mainline kernel
<kdubious>
Anyone know a good resource to work out a possible wiring / grounding issue with i2s from terh GPIO pins?
<prasannatsm>
I see. I will collect as much info as I can related to my device and compile Android or some Linux distro for it.
<ssvb_>
prasannatsm: it's not about the Linux distro image, but more like just to have some pictures and a very basic device information with tips and tricks
libv has quit [Ping timeout: 244 seconds]
<ssvb_>
prasannatsm: also even without the 1-wire interface, your tablet should be pretty much useful if you create the U-Boot defconfig file and the appropriate dts file for the linux kernel
Netlynx has quit [Quit: Leaving]
libv has joined #linux-sunxi
<ssvb_>
prasannatsm: all the necessary information for creating the defconfig and the dts files should be available in the Allwinner's fex file
<prasannatsm>
@ssvb_: Okay.
<prasannatsm>
I am mostly interested in mainlining kernel code. So I am looking for things that I could do.
<ssvb_>
prasannatsm: too bad that a lot of the mainline code has been already implemented, and you only need to provide the appropriate configs
<ssvb_>
that's a lot less fun and not challenging at all
<ssvb_>
but still somebody has to do this for your tablet
<prasannatsm>
Yes its not going to be fun as I would like.
<KotCzarny>
if you have mali engine you may try writing opensource driver
<KotCzarny>
:)
<prasannatsm>
I don't have one. The tablet has a SGX.
<prasannatsm>
how could I retrieve fex file?
<KotCzarny>
well, sgx driver wouldnt be bad neither
<KotCzarny>
but it might be i have reconfigured kernel source slightly in the meantime, so recompile time
prasannatsm has left #linux-sunxi [#linux-sunxi]
apritzel has joined #linux-sunxi
<plaes>
kdubious: 1-wire works quite well with bit-banging using regular GPIO
<plaes>
via w1-gpio
cptG_ has joined #linux-sunxi
cptG has quit [Ping timeout: 244 seconds]
<mripard>
plaes: yeah, but the point of that task is not to use a gpio but the controller ;)
<plaes>
I know
zuikis has left #linux-sunxi [#linux-sunxi]
apritzel has quit [Ping timeout: 244 seconds]
<kdubious>
plaes: I was asking about i2s.... i mentioned 1-wire since prasannatsm asked about it
<kdubious>
mripard: do you know about i2s output signals?
<kdubious>
I have a board that converts 3.3v ttl to LVDS
<kdubious>
that board requires power, call it the "send board"
<kdubious>
if I power the send board from my A20 board's 5v & GND, I get distortion on 192kHz
<kdubious>
if I use a second power supply to power the send board, I can't connect the ground between the A20 and the send board (or I get distortion) unless I add a resistor in between
<mripard>
LVDS ?
<mripard>
the panel interface?
<longsleep>
can ayone explain to me the reasons why the pine64 provide images as torrents and not just plain downloads? Even my images they link as torrents instead of the direct downloads ..
<kdubious>
we send i2s over lvds (on an HDMI cable) to a receiver in our DAC
<kdubious>
so we can transmit i2s over a longer distance
<mripard>
wow
<mripard>
that looks interesting
<KotCzarny>
longsleep: money
<longsleep>
KotCzarny: what money?
<KotCzarny>
torrents use backer's bandwidth
<longsleep>
KotCzarny: pff bandwidth is cheap
<KotCzarny>
not if you want to provide 2mbit for few thousands of users
<kdubious>
a few high-end DAC companies (device, now chip) use this approach
<longsleep>
KotCzarny: i mean my images are available by direct download from canada, europa and japan
<kdubious>
but do you have any feedback about the wiring? Do I need pull-up / pull-down resistors for the 3 i2s lines?
<longsleep>
KotCzarny: 2mbit for a few thousand of users?
<longsleep>
KotCzarny: that is nothing if you ask me
<KotCzarny>
longsleep: so you have 2gbit guaranteed uplink ?
<KotCzarny>
lucky you
reinforce has quit [Quit: Leaving.]
<longsleep>
KotCzarny: no, 1gbit only but really bandwidth is cheap in Germany - they can easily put servers here
* vagrantc
doesn't get what's wrong with using a torrent
<longsleep>
vagrantc: well, you cannot wget it
* vagrantc
doesn't get what's wrong with using a torrent
<longsleep>
properly seeded torrent is fine, but only in addition to a fast direct download if you ask me
<longsleep>
i see people complaining about slow torrent download where the same people could just use the fast direct download from my server
<kdubious>
mripard: are the i2s pins supposed to be tied up or down?
<kdubious>
can anyone tell me about the diff between the legacy gmac and the mainline stmac driver?
<mripard>
kdubious: I have no idea
<kdubious>
about either?
<lvrp16>
longsleep: torrents prevent modification, it's automatically verified for you
<kdubious>
or i2s pins
<mripard>
kdubious: about the i2s pins
<lvrp16>
longsleep: so that malicious hosters can't tamper with the image and distribute bad images to thousands of users
<mripard>
for the gmac vs stmac, different driver for the same hardware block
<lvrp16>
longsleep: i know because i faced the problem numerous times b4
IgorPec has quit [Ping timeout: 276 seconds]
libv has quit [Ping timeout: 244 seconds]
<kdubious>
i have this strange issue that on some power-ups, I get no eth traffic at all
<kdubious>
but, if I connect 3.3v to UARTo-Rx (before power up), it works
libv has joined #linux-sunxi
<kdubious>
I think I may have a bad DTS... or Itead Core EVB has a bad board design / manufacturing process
<kdubious>
but I'm not sure how to troubleshoot
p1u3sch1 has quit [Ping timeout: 260 seconds]
<mripard>
I don't know either
<mripard>
that looks like an hardware issue
<mripard>
you could try to contact them
<mripard>
and / or contact owners of that board
p1u3sch1 has joined #linux-sunxi
<kdubious>
I've been in contact with them, they suggested a better quality crystal would create fewer dropped packets... but that's not it
<kdubious>
I also don't think they're using the mainline kernel at all
<kdubious>
I saw tha BPi uses the regulator, and adds a delay to the 3v
pekka10 has joined #linux-sunxi
<kdubious>
and on one of the boards I have, the 3.3v to UART0-Rx doe not work.. but if I power it up with a USB UART connected, eth works
<kdubious>
is there some power sequence that teh PHY needs? does the driver handle that?
<kdubious>
Is there a better place to ask these questions?