<oliv3r>
mripard: so what is the subtle difference then?
<oliv3r>
mripard: also, hi :)
<wens>
oliv3r: 8 cores vs 4 cores
<mripard>
oliv3r: well, in one case, you have 4 cores enabled max, in the other one, 8
<wens>
the linaro article has a comparison that says it all
<mripard>
oliv3r: and as for the PowerVR, I guess you're only buying Tegra K1 then? :)
lukas_2511 has joined #linux-sunxi
<mripard>
(and hi :))
<rm>
Allwinner A23 should be OK
<rm>
4-core with Mali
<rm>
oh nope
<rm>
A33
hansg has quit [Quit: Leaving]
<oliv3r>
mripard: so if there's only 4 cores, 2 fast 2 slow, it works allready?
<oliv3r>
mripard: limadriver :p
<oliv3r>
is there hardware out with a33 yet?
<oliv3r>
or has 'a40' been announced yet?
<wens>
oliv3r: no, you get either the fast one or the slow one, not both
nabblet has joined #linux-sunxi
hramrach has quit [Remote host closed the connection]
hramrach has joined #linux-sunxi
<amitk>
oliv3r: the restriction isn't the number of cores, it is how the linux scheduler percieves them. The current assumption made by the Linux scheduler is that all cpus are equal. This is bad in the case of big.LITTLE when one type of core is fast and power-hungry and the other is slow(er) but power efficient
<oliv3r>
exactly, but i thought that very smart people where working on that :p
<oliv3r>
which is what my statement was about
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
<amitk>
Each run with a workload will give different performance and power numbers (depending on which cpu it got scheduled on)
<amitk>
oliv3r: yes, it is WIP
akaizen_ has quit [Remote host closed the connection]
<mripard>
oliv3r: yep
lukas_2511 has quit [Ping timeout: 264 seconds]
akaizen has joined #linux-sunxi
lukas_2511 has joined #linux-sunxi
<oliv3r>
wens: you know the innards of the axp PMU's yeah?
<mripard>
oliv3r: and given that lima haven't seen any commit in over a year, I don't really see how it can compare.
<wens>
oliv3r: pretty much
<oliv3r>
mripard: i know :( it saddens me :(
avsm has quit [Quit: Leaving.]
<oliv3r>
wens: if my board lacks a power button (or inaccessable power button) what are my chances of getting stuck in a 'powered off' mode
<mripard>
mnemoc: all: just fyi, the git tree with my accepted patch branches have moved to kernel.org
<nedko>
the soc doesnt seem to be attached to the case-sink
<nedko>
via heatpipe or something
<popolon>
no picture of the opened case
<popolon>
perhaps that's just a preventive case, used with an experimental version of A80 ?
lukas_2511 has quit [Ping timeout: 264 seconds]
<popolon>
at least with this kind of case, I suppose no fan is needed even with very hot SoC
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
nabblet has quit [Quit: leaving]
<popolon>
CT-Metal Case, so that's for cubietruck, not for Cubieboard 8
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
<wens>
i made the same mistake yesterday :p
<oliv3r>
wens: so the AXP if it looses complete power (no backup battery) it comes back up 'normally'
<oliv3r>
i think i have to put time and effort into porting the nadnd driver from the oldu-boot to our current ub--boot
lukas_2511 has joined #linux-sunxi
<oliv3r>
boot0 code may just not be sufficient for us to work with :S
<wens>
oliv3r: that's my understanding, yes
<oliv3r>
btw, what was the reasoning that the 8192cu etc have special 'sw' versions? I think it was the power pin, right?
<oliv3r>
the vusb power thing
lukas_2511 has quit [Ping timeout: 248 seconds]
lukas_2511 has joined #linux-sunxi
<wens>
i'm not aware of it
lukas_2511 has quit [Read error: Connection reset by peer]
hani_ has joined #linux-sunxi
<hani_>
Hi everyone I saw a message on the forum about the nand driver is in the mainline but I'm having trouble finding it
<wens>
oliv3r: i only see 8192cu and 8192su on realtek's website
<wens>
(and other non usb 8192 variants)
<HeHoPMaJIeH>
5 мин
<HeHoPMaJIeH>
sorry , wrong window :)
<mripard>
hani_: it's not there yet
leviathanch has joined #linux-sunxi
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
lukas_2511 has joined #linux-sunxi
avsm has joined #linux-sunxi
<hani_>
mripard: thanx. I've been using bbrezillon nand patches for quite sometime without any issues. A part from obtaining the timing information I think it is good enough to make to mainline
lukas_2511 has quit [Ping timeout: 248 seconds]
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
_massi has quit [Remote host closed the connection]
hani_ has quit [Ping timeout: 246 seconds]
Black_Horseman has quit [Remote host closed the connection]
lukas_2511 has joined #linux-sunxi
Black_Horseman has joined #linux-sunxi
lukas_2511 has quit [Ping timeout: 264 seconds]
lukas_2511 has joined #linux-sunxi
hani_ has joined #linux-sunxi
lukas2511 has quit [Ping timeout: 248 seconds]
lukas2511 has joined #linux-sunxi
lukas2511 has quit [Read error: Connection reset by peer]
hani_ has quit [Ping timeout: 246 seconds]
lukas2511 has joined #linux-sunxi
lukas2511 has quit [Read error: Connection reset by peer]
Andy-D has joined #linux-sunxi
lukas2511 has joined #linux-sunxi
lukas_2511 has quit [Ping timeout: 248 seconds]
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
joedj_ has quit [Ping timeout: 260 seconds]
lukas_2511 has joined #linux-sunxi
joedj_ has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
arokux1 has joined #linux-sunxi
hramrach has quit [Ping timeout: 264 seconds]
arokux has quit [Ping timeout: 245 seconds]
y0g1 has quit [Ping timeout: 245 seconds]
lukas_2511 has joined #linux-sunxi
eagles0513875 has quit [Ping timeout: 272 seconds]
nabblet has joined #linux-sunxi
y0g1 has joined #linux-sunxi
eagles0513875 has joined #linux-sunxi
y0g1 has quit [Ping timeout: 245 seconds]
eagles0513875 has quit [Changing host]
eagles0513875 has joined #linux-sunxi
y0g1 has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
lukas_2511 has quit [Ping timeout: 264 seconds]
lukas_2511 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 264 seconds]
lukas_2511 has quit [Read error: Connection reset by peer]
jebba has quit [Quit: Leaving.]
lukas_2511 has joined #linux-sunxi
nedko has quit [Ping timeout: 260 seconds]
lukas_2511 has quit [Ping timeout: 264 seconds]
lukas_2511 has joined #linux-sunxi
lukas_2511 has quit [Read error: Connection reset by peer]
leviathanch has quit [Ping timeout: 240 seconds]
avsm has quit [Quit: Leaving.]
hipboi has quit [Quit: Leaving]
xinj has joined #linux-sunxi
<oliv3r>
wens: i ment the 8192 realtek that has special 'sw' e.g. softwinner driver versions
<oliv3r>
hani_ how's the nand performance with bbrezillon's patches
FDCX has quit [Ping timeout: 240 seconds]
nabblet has quit [Quit: leaving]
avsm has joined #linux-sunxi
<mripard>
oliv3r: I don't have any comparison, but can it be worse than no support at all ?
<oliv3r>
mripard: compared to libnand :p
<oliv3r>
since it lacks dDMA
<oliv3r>
if we have reasonable fast nand, we could actually go with a mainline kernel in our product
<oliv3r>
i'm not looking forward to working with boot0 :S
arokux1 has quit [Remote host closed the connection]
<mripard>
oliv3r: DMA doesn't mean that it will be faster
arokux has joined #linux-sunxi
<mripard>
it means that it will consume less CPU
<oliv3r>
true, what CPU usage do you see?
<mripard>
don't know, never tested the patches
<oliv3r>
i guess I should :D
<oliv3r>
the a10 temp sensor patches where for mainline only where they not?
<mripard>
but I'd much rather seeing it work before seeing it work fast
FDCX has joined #linux-sunxi
<oliv3r>
what still needs to be done to get it into the mainline kernel?
<mripard>
having a responsive maintainer would help
<mripard>
giving bbrezillon some motivation to repost his patches too
<oliv3r>
eep : (
<oliv3r>
that kinda sucks :(
<wens>
oliv3r: hmm, maybe for parsing fex file and getting the usb stuff, though I thought the rfkill driver did that
jebba has joined #linux-sunxi
<oliv3r>
yeah but doe sthe 3.4 have rfkill stuff?
<oliv3r>
parsing fex for sure
<oliv3r>
but i may just make a small generic fex -> rfkill thing
<oliv3r>
allowing the usage of regular usb wifi drivers
<wens>
there is, but doesn't seem to compile
<oliv3r>
ah :(
<oliv3r>
well that's fixable
<oliv3r>
:)
Gerwin_J has quit [Quit: Gerwin_J]
Gerwin_J has joined #linux-sunxi
issueat has joined #linux-sunxi
mmarker has quit [Ping timeout: 272 seconds]
Black_Horseman has quit [Quit: Zwi se logou mou!!!]
HeHoPMaJIeH has quit [Remote host closed the connection]
ecelis_ is now known as ecelis
afaerber_ has quit [Quit: Verlassend]
tomboy64 has joined #linux-sunxi
eagles0513875 has quit [Changing host]
eagles0513875 has joined #linux-sunxi
eagles0513875 has joined #linux-sunxi
eagles0513875 has quit [Changing host]
<juanfont>
has anyone had any luck with the 'rtl8192cu' driver? (I'm saying it to add to http://linux-sunxi.org/Wifi that it's better to use the '8192cu' and blacklist the 'rtl8192cu'
wickwire has quit [Ping timeout: 264 seconds]
xavia has joined #linux-sunxi
hramrach has joined #linux-sunxi
avsm has quit [Quit: Leaving.]
wickwire has joined #linux-sunxi
FunkyPenguin has quit [Ping timeout: 240 seconds]
FunkyPenguin has joined #linux-sunxi
FunkyPenguin has quit [Ping timeout: 240 seconds]
eagles0513875 has quit [Read error: Connection reset by peer]