lamer14520031072 has quit [Ping timeout: 264 seconds]
tomboy64 has joined #linux-sunxi
lamer14520031072 has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 240 seconds]
ricardocrudo has quit [Ping timeout: 260 seconds]
mozzwald_ is now known as mozzwald
viccuad has quit [Ping timeout: 276 seconds]
captainigloo has quit [Ping timeout: 260 seconds]
vinifr has quit [Quit: Saindo]
captainigloo has joined #linux-sunxi
zerotri_ has joined #linux-sunxi
orly_owl has quit [Ping timeout: 255 seconds]
zerotri_ is now known as zerotri
lamer14520031072 has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 246 seconds]
cnxsoft has joined #linux-sunxi
ninolein_ has quit [Ping timeout: 250 seconds]
ninolein has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
orly_owl has joined #linux-sunxi
captainigloo has quit [Ping timeout: 260 seconds]
hipboi_ has quit [Quit: Leaving]
captainigloo has joined #linux-sunxi
captainigloo has quit [Ping timeout: 260 seconds]
captainigloo has joined #linux-sunxi
hipboi has joined #linux-sunxi
afaerber has quit [Ping timeout: 250 seconds]
lamer14520031072 has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-sunxi
naobsd has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
lamer14520031072 has joined #linux-sunxi
TheSeven has quit [Ping timeout: 240 seconds]
lamer14520031072 has quit [Ping timeout: 265 seconds]
TheSeven has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 245 seconds]
p1u3sch1 has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 256 seconds]
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
lamer14520031072 has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 265 seconds]
vagrantc has joined #linux-sunxi
IgorPec has joined #linux-sunxi
leio has quit [Ping timeout: 240 seconds]
whitesn_ is now known as whitesn
whitesn has quit [Changing host]
whitesn has joined #linux-sunxi
lamer14520031072 has joined #linux-sunxi
leio has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 240 seconds]
vagrantc has quit [Quit: leaving]
doppo has quit [Ping timeout: 250 seconds]
IgorPec has quit [Ping timeout: 246 seconds]
doppo has joined #linux-sunxi
lamer14520031072 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
domidumont has joined #linux-sunxi
lamer14520031072 has quit [Ping timeout: 255 seconds]
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
ikmaak has quit [Remote host closed the connection]
ikmaak has joined #linux-sunxi
TheLinuxBug has quit [Ping timeout: 250 seconds]
rgwan-phone has joined #linux-sunxi
TheLinuxBug has joined #linux-sunxi
hipboi has quit [Ping timeout: 240 seconds]
hipboi has joined #linux-sunxi
HeHoPMaJIeH has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 256 seconds]
lamer14520031072 has joined #linux-sunxi
mawe242 has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
avph has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
rgwan-phone has quit [Ping timeout: 272 seconds]
IgorPec has joined #linux-sunxi
Andy-D_ has joined #linux-sunxi
Andy-D has quit [Ping timeout: 240 seconds]
FlorianH has joined #linux-sunxi
martijn has joined #linux-sunxi
diego_r has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
lamer14520031072 has quit [Ping timeout: 260 seconds]
yann|work has joined #linux-sunxi
apritzel has joined #linux-sunxi
mmwolbrink has joined #linux-sunxi
martijn has quit [Quit: Leaving]
mmwolbrink has quit [Remote host closed the connection]
mmwolbrink has joined #linux-sunxi
mmwolbrink has quit [Remote host closed the connection]
mmwolbrink has joined #linux-sunxi
<sunxi_fan>
mripard: the PCM5102 looks like a I2S DAC without software config (as far as the PDF says http://www.ti.com/lit/ds/symlink/pcm5102a.pdf), i'm wondering how can just make the simple-audio-card entry "happy" in the codec node so to make the alsa audio device visible and check if the clocks are getting out of the I2S bus on the a20 side..
deskwizard is now known as desk_away
<mripard>
I'm afraid you'll still need a driver to let ASoC at least know what format the codec handles, how many bits it can handle, etc.
<mripard>
it won't be very hard to do, but still
KotCzarny has quit [Ping timeout: 272 seconds]
naobsd has quit [Remote host closed the connection]
viccuad has joined #linux-sunxi
<sunxi_fan>
i don't mind to make a stub codec driver. i'm just wondering there aren't already actually.. i'm going to give a look in the codec dir.. BTW i supposed a "dummy codec" they talk about in alsa ML was exactly about this kind of setup.
<mripard>
I looked yesterday evening, and it didn't look like it had support
<MoeIcenowy>
To be honest
<MoeIcenowy>
I found that the A33 ASoC driver in Lichee cannot be used
desk_away has quit [Quit: Growing old is mandatory, growing up is optional ! ^.^]
<MoeIcenowy>
try to use it will lead kernel to lock down/panic
<MoeIcenowy>
(randomly
<MoeIcenowy>
(Oh
<MoeIcenowy>
(It's the compiler's fault
<MoeIcenowy>
I used a 4.9 compiler to build this 3.4 kernel
<MoeIcenowy>
failed
<MoeIcenowy>
then I switched to a 4.6
<MoeIcenowy>
ok
<MoeIcenowy>
Oh the system have gone dead lock again
<mripard>
sunxi_fan: and it seems like you can't load the dummy codec on its own, at least using dt
<sunxi_fan>
that "issue" about DTS was really what i was looking just now..
<sunxi_fan>
i suppose the PCM5102 driver CANT depend on the i2c bus..
<sunxi_fan>
maybe we can map it into the dai0 node..
<mripard>
well, no, it's not a i2c device
<sunxi_fan>
(let me tell you i really dont know what i'm talking about..)
<sunxi_fan>
:-)
<mripard>
just put in at the root at the tree
<mripard>
like led-gpios for example
<sunxi_fan>
i suppose that, as the only "link" to host is the I2S link (a part of VCC/GND..), it SHOULD be connected on the I2S bus (whatever it means into the DTS model..)
<sunxi_fan>
ok.. this is a simpler approach..
<mripard>
the link is expressed by the simple-machine stuff
Ueno_Otoko has quit [Ping timeout: 255 seconds]
<mmwolbrink>
pcm5102 indeed doesnt need any configuration, just connect i2s and it should work
lamer14520031072 has joined #linux-sunxi
<mmwolbrink>
sunxi, i designed and build a simple dac with the pcm5102 if you need one i could send you one
<MoeIcenowy>
Oh lichee just sucks
<MoeIcenowy>
All lichees should be built with lichee gcc-linaros
<montjoie>
I have just get an ethernet dongle, so I will work faster on h3 EMAC driver now
<apritzel>
montjoie: ah, that's your nick ;-)
<montjoie>
apritzel: for the moment the H3 Emac driver is not usable, not getting interupt for receiving frame, and nothing get transmitted
<mripard>
apritzel: I haven't
<mripard>
apritzel: and yeah, DT can remove some of it
<mripard>
apritzel: moving the phy bits to the phy framework too
<apritzel>
montjoie: is your driver from scratch or based on some BSP crap?
<mripard>
(same thing for the clocks)
<montjoie>
But I still receive frame, but only the first one seems not garbarge
<montjoie>
I receive arp request I send
<mripard>
you can drop the mac adress generation thing too, there's a generic function to do that in the net framework
<montjoie>
but after seems really garbarge
<montjoie>
apritzel: driver is made from scratch
ricardocrudo has joined #linux-sunxi
<mripard>
is there any particular reason to start from scratch ?
<mripard>
the original driver looks quite ok already
<apritzel>
montjoie: mripard: do you mind if I take a look at adapting the original driver?
nemunaire has quit [Quit: quit]
mawe242 has quit [Remote host closed the connection]
nemunaire has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 272 seconds]
mmwolbrink has quit [Remote host closed the connection]
<mripard>
apritzel: fine by me, that will give you the occasion to dig into the network stack ;)
<apritzel>
mripard: tempting ... not ;-)
KotCzarny has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
Ueno_Otoko has joined #linux-sunxi
avph has joined #linux-sunxi
<montjoie>
mripard: starting from scratch is not the problem, the bad documentation is
viccuad has quit [Read error: Connection reset by peer]
<mripard>
montjoie: and with bad documentation, starting from scratch becomes a problem
<montjoie>
perhaps I will change my way to do it, but I am near to success
reinforce has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
<jelle>
I'm quiet new to the sunxi development, how does u-boot then handle h3 ethernet driver? Is there usually first a linux driver written then ported to u-boot?
_massi has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 255 seconds]
<tkaiser>
If I understand correctly H3, A83T and H64 use the same new MAC implementation. And results with Allwinner's BSP driver on Banana Pi M3 (A83T) looked somewhat promising: 550-730 Mbits/sec without further tuning
<tkaiser>
Would be nice to get this with mainline kernel too :)
avph has quit [Ping timeout: 255 seconds]
<jelle>
cool
<montjoie>
I am not sure than A83T have the same EMAC
<tkaiser>
i.MX6 gets close to 100 MB/s with SATA but Ethernet throughput is limited to 400 Mbits/sec (at least on the older chip revisions)
<Wizzup>
I get about 120MB/s on SATA on an A20
<Wizzup>
that is with a sata port multiplier
<Wizzup>
That is on a lime2
<tkaiser>
Wizzup: Read or write? If read then your disk is the bottleneck.
<Wizzup>
I think this is read, but like I said, sata PM
<Wizzup>
and the A20 only supports the slower PM mode
<Wizzup>
tkaiser: these are two recently WD 6TB disks
<Wizzup>
with hdparm I get a bit more, but a btrfs scrub ran at 120MB/s
<montjoie>
apritzel: yeah I believe that wens said that it was a stmmac but didnt find source of that in my irclogs
<tkaiser>
A20 can exceed 200 MB/s reading but I never got more than 45 MB/s write. PM or not doesn't matter that much unless it's about random I/O
orly_owl has quit [Ping timeout: 250 seconds]
<Wizzup>
tkaiser: I have a SSD on the same SATA PM, can try that.
<tkaiser>
No need (at least for me, spent already days testing A20 SATA ;)
<Wizzup>
ack
cnxsoft has quit [Remote host closed the connection]
<TheLinuxBug>
tkaiser: in my own application I am using a SYBA JMxxx raid card so its one port on the A20 and my performance is pretty nice, but of course hit the bottleneck of 50M/sec on the gigbit nic cause it can only be bound to 1 cpu core
<TheLinuxBug>
tkaiser: also I have been really intereested in the Marvell boards for that reason, ususally cost is what prevents me from buying them when I find a distributor
<TheLinuxBug>
they either want purchase in bulk for a reasonable price
<TheLinuxBug>
or some higher amount for single boards
<TheLinuxBug>
I tested first with PM card with software raid5. then tested with the SYBA JMxxx hardware raid
<tkaiser>
And what's also important: Use cases. When you run a database random I/O and native command queueing are more important than sequential read speeds.
<TheLinuxBug>
the hardware raid actually turned out the better option
<TheLinuxBug>
especailly for raid rebuild
<TheLinuxBug>
in both cases read/writes are right along the lines to be expected
<TheLinuxBug>
some things that can help if mount options for the drive also
<tkaiser>
Regarding SOHO RAID I've my own opinion (avoid it!) and regarding Marvell: Check the Turris Omnia, I will get one and use a simple mechanical mSATA to SATA converter to use it with a large 3.5" disk
<TheLinuxBug>
yeah I read your articles on it
<TheLinuxBug>
ther is always going to be a single point of failure to be had
<TheLinuxBug>
if this were 'important' information like business information I wouldn't store it on it anyways
<TheLinuxBug>
but for a home NAS, even if I do have a failure at some point, shouldn't be a huge loss
afaerber has joined #linux-sunxi
<TheLinuxBug>
I went through and did a lot of messing with A20, tweaks (some from your articles and some from others) and used PM and the SYBA PM/Raid card and I just felt satisfied with the raid card
<TheLinuxBug>
offloading rebuild is a nice thing to have
<TheLinuxBug>
rebuilding the software raid would take more than a day with 5x2tb
<tkaiser>
TheLinucBig: I won't comment on RAID ;) but you should warn 'drmike' since the USB-to-SATA bridge on the Orange Pi Plus 2 is really crap (slow as hell)
<TheLinuxBug>
hehehe yeah
<TheLinuxBug>
well hey, your welcome to sign-up and participate some too my friend, we always need some new friendly faces around there as well :) Good group of guys.
<TheLinuxBug>
(and girls?)
<TheLinuxBug>
anyhow, doing some cross promotion I guess ;p
<TheLinuxBug>
tkaiser: btw I generally do enjoy reading most of your posts I have seen on any SoC. Actually ran into your material a lot when working on my project with the A20, so thank you for that :)
lamer14522639463 has joined #linux-sunxi
tkaiser has quit [Ping timeout: 245 seconds]
Ueno_Otoko has quit [Ping timeout: 256 seconds]
lamer14522639463 has quit [Ping timeout: 276 seconds]
<topi`>
tkaiser: do you have experience of the SATA on the Geekbox?
<KotCzarny>
mm, my router/nas/audio box is coming nicely
<KotCzarny>
i wonder how to control battery charging thresholds
<KotCzarny>
keeping li-ion constantly at 100% isnt future-proof
<topi`>
i'd rather keep it at 80% or 90%
<KotCzarny>
i dont mind keeping it ~50-60%
<KotCzarny>
but dont' know how
<topi`>
stop charging at that point?
<topi`>
evidently, that requires access to the battery controller code
<topi`>
which is probably hidden from view
<KotCzarny>
the only interface is through /sys/
<topi`>
when I worked at Nokia, one of the closely kept secrets was the battery charging code
<KotCzarny>
:)
<topi`>
I tried to find it to have a look, but didn't have permissions
MaDMaLKaV has quit [Read error: Connection reset by peer]
MaDMaLKaV has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
iamfrankenstein has quit [Ping timeout: 255 seconds]
naobsd has joined #linux-sunxi
focus has quit [Ping timeout: 245 seconds]
avph has joined #linux-sunxi
focus has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
fredy has quit [Excess Flood]
T0mW has joined #linux-sunxi
avph has joined #linux-sunxi
fredy has joined #linux-sunxi
tkaiser has joined #linux-sunxi
<tkaiser>
topi`: nope, just read that the Geekbox uses the JM20329 bridge (zero experience with it)
Netlynx has joined #linux-sunxi
Netlynx has joined #linux-sunxi
<tkaiser>
KotCzarny: Still playing with the R1?
yann|work has quit [Ping timeout: 246 seconds]
<KotCzarny>
tkaiser: yes, its stable, no udma crc errors, routing properly, battery works, 2.5W of total power usage
<KotCzarny>
i'm quite happy atm
domidumont has quit [Read error: Connection reset by peer]
<apritzel>
KotCzarny: is that the BananaPi Router thing?
<KotCzarny>
yes, bpi-r1
<apritzel>
does the switch (aka phy) work with mainline?
<KotCzarny>
dont know yet
<KotCzarny>
i need audio
<KotCzarny>
so im stuck with legacy atm
<topi`>
tkaiser: usb2 sata bridges suck :( but so does the write perf in the A20
<topi`>
so, for writes, the A20 is not much better, unfortunately.
<tkaiser>
apritzel: The switch works but needs a patchset from OpenWRT that will not be accepted upstream
<tkaiser>
And there are serious performance drawbacks when using the b53 driver
<apritzel>
tkaiser: because it is too ugly and nobody cared about cleaning it up?
<tkaiser>
Maybe, don't know. I just followed a few discussions on an OpenWRT list.
<tkaiser>
But since the R1 sucks in many regards I simply gave up.
<KotCzarny>
tkaiser, if you dont need gbit performance its quite usable and all-in-one wonder
<apritzel>
tkaiser: what are the problems with the R1? Looked quite good to me to replace my router and have some easy NAS solution included
<tkaiser>
1st problem: You can't use it as router since when it boots (or you bricked your board) you always end up with a layer 2 switch interconnecting WAN and LAN
<tkaiser>
It has to learn VLAN configuration and in between it opens up your whole network.
FlorianH has joined #linux-sunxi
<apritzel>
(coming from OpenWRT on MIPS it looks like a revelation in terms of performance to me)
<KotCzarny>
tkaiser, if you backup it with battery there isnt much in the reboots world
<tkaiser>
The BCM53125 might work in another mode (5 GbE PHYs and 2 RGMII interfaces) but the A20 has only one RGMII interface
<apritzel>
tkaiser: so that's the reset configuration?
<tkaiser>
Yes, it's a switch and has to learn VLANs later to be able to differentiate between WAN and LAN
<tkaiser>
That's a simple no-go (at least for me)
<KotCzarny>
im using it in 2x wan (different) + 3xlan config
<topi`>
tkaiser: I've been looking for a decent cheap AArch64 box, and am still looking ;)
<KotCzarny>
works pretty well
<topi`>
although I'm willing to give the Geekbox a try. but I wish I'd get cortex-a57 / cortex-a72 based boards :/
<apritzel>
topi`: who is not?
<tkaiser>
KotCzarny: I won't use a switch as router. For me the default state of a router has to be: No interconnect between WAN and LAN. With the Lamobo the default state is: bridging on layer 2
<tkaiser>
BTW: Any of you guys applies for Pine64 developer samples?
<apritzel>
tkaiser: I did
<tkaiser>
s/applies/applied
<apritzel>
they sent it out on Monday reportedly
* apritzel
is eagerly waiting for it
<apritzel>
meanwhile I just managed to compile that BSP A64 ethernet driver on mainline
<apritzel>
removing a lot of crap
<tkaiser>
Cool :)
<apritzel>
one of two things need to be cleaned up, still (like regulators and maybe pinctrl)
<apritzel>
s/of/or/
<tkaiser>
I remember you posted something regarding boot state in the pine64 forum. Did you resolves that also in the meantime?
<tkaiser>
But that was related to 3.10.65 kernel
<apritzel>
tkaiser: I guess I need the actual board to see what they are doing ...
<KotCzarny>
tkaiser: my lan is linux laptop and steam pc
<KotCzarny>
so it doesnt matter much, yet i like my r1
<apritzel>
tkaiser: they _have_ a PSCI implementation in their ARM trusted firmware code in the BSP
<apritzel>
but for some reasons they appear to not use it
<apritzel>
maybe it's broken
vishnu_ has quit [Ping timeout: 240 seconds]
<topi`>
I don't know about PINE64... I'm myself waiting for Olimex's version of A64
<tkaiser>
To finish the R1 stuff: 2nd problem is DC-IN (micro USB responsible for undervoltage/undercurrent situations) and 3rd problem is heat dissipation when you use the board horizontalle. On top of that: crappy Wi-Fi wasting one USB host port and being not able to work reliably in AP mode
<apritzel>
tkaiser: Allwinners BSP kernel (3.10.x LSK based) expects to be entered in EL3 (and EL3 only)
<KotCzarny>
tkaiser, crappy wifi and boot time fubar config are the only things i have to say negatively about it
<tkaiser>
topi`: Pine64 is on Kickstarter and starts at $15 for the basic variant. What scares me a bit is their marketing. They advertise the board consuming only 2.5W and stay close above 32¡C.
<KotCzarny>
i dont use wifi tho
<apritzel>
which is a) forbidden and b) does not play with any sane firmware
<topi`>
well the Pine64 guys are completely unknown, whereas the Olimex guys are known for their skill in designing HW
<apritzel>
also that means that their firmware cannot load upstream kernels easily
<tkaiser>
apritzel: So we'll see when you have the board at hands... BTW: They sent me a first board on Dec. 15th that's still on its way ;)
<KotCzarny>
btw. my r1 also has ~29-32C (idle) and ~2.5W of power
<apritzel>
tkaiser: great :-(
<tkaiser>
I would believe the Pine64 guys will cooperate with a good ODM (in Shenzhen)
FlorianH has quit [Ping timeout: 240 seconds]
<tkaiser>
KotCzarny: The 'problem' is this https://www.youtube.com/watch?v=0Co9iDEVnWc (showing idle consumption and claiming that would be consumption under load, and I don't believe the 30¡C simply since all recent Allwinner SoCs work 15¡-20¡C above ambient temperature when being idle)
<KotCzarny>
tkaiser, a20 doesnt grab much more power under load, and yeah, i saw max ~37C (kernel compilation)
<tkaiser>
Have a look at budget-cooling and thermal zones.
iamfrankenstein has quit [Ping timeout: 255 seconds]
<tkaiser>
The values there seem to indicate that A64 might get quite hot
iamfrankenstein1 has joined #linux-sunxi
<KotCzarny>
:)
<KotCzarny>
could be overclocked?
<KotCzarny>
also, do you know how to keep li-ion from being charged at 100% all the time?
<tkaiser>
The opposite. Pine64 is advertised as running 'up to 1.2 Ghz' but in the BSP it's 1152 MHz max.
indy has quit [Ping timeout: 255 seconds]
iamfrankenstein1 is now known as iamfrankenstein
<tkaiser>
No idea. Maybe using a cheap relay triggered through GPIO and reading out the charging progress through sysfs and then interrupting the connection? Nope that renders the whole UPS approach useless
<KotCzarny>
you've mentioned boot.scr tables
<KotCzarny>
(few weeks ago)
FlorianH has joined #linux-sunxi
RzR has joined #linux-sunxi
indy has joined #linux-sunxi
<tkaiser>
'boot.scr tables'?
<wens>
the fex file (and the pmu) has a table that corelates battery voltage with charge level
<wens>
nice to see a lot of interest and will to work on the a64 :)
FlorianH has quit [Ping timeout: 255 seconds]
<KotCzarny>
s/scr/fex/
<KotCzarny>
pmu_bat_para[1..16]
<KotCzarny>
and pmu_battery_[rdc,cap] etc
<KotCzarny>
wens, do you have any idea how to use those tables to set charging thresholds?
<wens>
nope
<KotCzarny>
or phrasing in this way 'if i set 100 at some lower table will it end the charge earlier'
<wens>
no idea, sorry
Deskwizard has joined #linux-sunxi
domidumont has joined #linux-sunxi
WarheadsSE has joined #linux-sunxi
<WarheadsSE>
Well, my PINE64 has arrived
<apritzel>
WarheadsSE: did it came with any image (or a pointer to it?)
<WarheadsSE>
which at best is the lichee tree bsp & android image
<apritzel>
WarheadsSE: well, at least one does not need to build that crap ;-)
<WarheadsSE>
Yeah
<apritzel>
WarheadsSE: thanks for the pointer, somehow missed that ...
iamfrankenstein1 has joined #linux-sunxi
<WarheadsSE>
Gotta catch up on the mailing lists etc for uboot/linux-sunxi, see where it stands
<WarheadsSE>
I had to google for it
<apritzel>
ah great, they have the pin numbers there
<apritzel>
(was wondering about that for the .dts)
Wizzup_ has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 255 seconds]
iamfrankenstein1 has quit [Ping timeout: 255 seconds]
Wizzup has quit [Ping timeout: 255 seconds]
<tkaiser>
The .tgz from the link in the forums is the same they already put in the mid of December on Google drive.
<tkaiser>
And IIRC I got errors while running untar
FlorianH has joined #linux-sunxi
valkyr1e has quit [Ping timeout: 255 seconds]
valkyr1e has joined #linux-sunxi
valkyr1e has quit [Changing host]
valkyr1e has joined #linux-sunxi
<WarheadsSE>
joy
FlorianH has quit [Read error: Connection reset by peer]
<WarheadsSE>
So, how much do we have with linux-sunxi? So far all i see is the Kconfig/defconfig and a DTS for the pine
mnr has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
enrico_ has quit [Quit: Bye]
<ssvb>
WarheadsSE: did you have any kind of notification or a tracking number before your pine64 board arrived?
afaerber has quit [Quit: Ex-Chat]
<KotCzarny>
seriously, did they send the device without any kind of os ?
afaerber has joined #linux-sunxi
<ssvb>
KotCzarny: if I understand it correctly, this board has no built-in storage
<KotCzarny>
ssvb, i meant without any os available
<tkaiser>
KotCzarny: There in no kind of OS ;) Only Android is working at the moment and the boards have just SD card
<tkaiser>
The Pine64 people rely solely on this community.
khuey|away is now known as khuey
<KotCzarny>
o.o
<ssvb>
KotCzarny: you are supposed to download the OS separately, it is not shipped in the same package with the board
<KotCzarny>
did they send any samples to notable devs of sunxi-linux ?
<ssvb>
tkaiser: "The Pine64 people rely solely on this community" - that's a pretty bold statement, I'm sure they have a backup plan
<WarheadsSE>
ssvb: nope. just showed up USPS
<ssvb>
tkaiser: even if this backup plan means the 3.10 sdk kernel + some sort of linaro/ubuntu rootfs
<WarheadsSE>
mine didn't even come with an SD card, just the board.
<WarheadsSE>
ssvb: their backup plan is vendor pile.
<tkaiser>
ssvb: Agreed. But as apritzel pointed out it might be hard to get this 3.10.65 kernel booting Linux
<mnr>
KotCzarny: They offered boards to developers on the linux-sunxi mailing list.
<ssvb>
WarheadsSE: ok, then maybe they also have sent one of the boards to me
<ssvb>
tkaiser: if it boots Android, then it should be able to boot GNU/Linux userland too (with or without some tweaks)
<WarheadsSE>
Yeah, I didn't know it was coming, but realized I never got the mail yesterday. strolled out to find a package from china
<ssvb>
WarheadsSE: so they are sending it from China? what was the declared price?
<tkaiser>
Sure, but the 'Linux experience' for their backers will be horrible. There are a lot of people in their forums announcing that they will combine kernel+bootloader stuff with a rootfs of their choice
* ssvb
wonders if it is going to get stuck in the customs or not
<WarheadsSE>
ssvb: $5
<tkaiser>
My 1st board was sent out from Kuala Lumpur and they said the 2nd will be sent from China
<tkaiser>
1st board went through customs on the 5th and is now somewhere here around...
<WarheadsSE>
"main board <gibber>" Kg 0.075 Val (US) 5.0
<WarheadsSE>
yeah, Arch can't rely on that vendor kernel crap
<WarheadsSE>
We had to nix 6 previous ones because they lagged so far back systemd/udev/docker/etc
<mnr>
Is anybody aware of any changes regarding phy handling in linux-next? I'm currently trying to get linux-next working on a cubietruck and get "[ 2.805974] sun7i-dwmac 1c50000.ethernet eth0: NO MDIO subnode
<jelle>
ssvb: yeah but so much marketingspeak there :p
<ssvb>
they already have designed the board and tested it to some extent, the kickstarter is for mass production
<ssvb>
some of the boards are sent to interested developers before general public gets them too
<ssvb>
but 1 month gap might be a little bit too small
<ssvb>
C.H.I.P. takes a different approach and will ship much later, but probaby with better software support
<jelle>
yeah I ordered a C.H.I.P. also since I heard they actually help with mainlining
<ssvb>
we'll see which strategy turns out to be more successful in the end :-)
<jelle>
:-)
<ssvb>
on the other hand, Raspberry Pi is using a totally different strategy (same as Apple)
<ssvb>
they are very secretive and make an announcement only when they can start sales literally next day
<jelle>
ssvb: you mean the zero?
<jelle>
btw, while I'm here can anyone judge how easy it would be to get the board camera working on the orange pi pc? By ofcourse porting the driver to mainline?
<ssvb>
yes, this allows to catch their competitors by surprise, and also people don't get too bored waiting
viccuad has joined #linux-sunxi
<ssvb>
jelle: there is a camera for orange pi pc?
<jelle>
ssvb: I have a camera yeah
<ssvb>
does it work with the 3.4 kernel?
<jelle>
ssvb: sunxi-linux?
<jelle>
haven't tested that
<jelle>
I don't have a clue how in general these camera's are supported, take for example the bananapi
domidumont has quit [Ping timeout: 246 seconds]
Deskwizard has quit [Quit: Growing old is mandatory, growing up is optional ! ^.^]
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
ricardocrudo has quit [Ping timeout: 272 seconds]
skoperst has joined #linux-sunxi
Andy-D_ is now known as Andy-D
<mnr>
jelle: regarding the camera support - I suppose that is a camera for the CSI port? AFAIK nobody has done any work on a CSI driver for mainline.
<jelle>
mnr: yes CSI
<jelle>
mnr: ok so with every board?
<mnr>
jelle: yes, completely unsupported in mainline to my knowledge.
<jelle>
mnr: ok and in the sunxi 3.4 kernel?
<mnr>
jelle: I personally don't use 3.4, sorry.
mosterta has joined #linux-sunxi
yann|work has joined #linux-sunxi
premoboss has joined #linux-sunxi
<ssvb>
jelle: not many people have this kind of hardware and interested in this stuff
<jelle>
ssvb: ok no problem
<jelle>
I'll try looking into it when I have some more expierence with hacking on allwinner devices
<ssvb>
if you can verify that the camera works with the 3.4 kernel, then at least this code can be inspected and ported to the mainline kernel
<jelle>
ok, that sounds logical yes
jinzo has joined #linux-sunxi
mnr has quit [Quit: leaving]
apritzel has joined #linux-sunxi
IgorPec has joined #linux-sunxi
IgorPec has quit [Ping timeout: 246 seconds]
jinzo has quit [Quit: Leaving]
Mausschubser has joined #linux-sunxi
<Mausschubser>
i downloaded livesuite in a zip-file which I extracted
<Mausschubser>
after that i ran a command which I forgot, to set it up
<Mausschubser>
now I want to run livesuite but the command doesn work