<moofish>
*Hypothetically* if someone happened to have laid their hands on lichee for a1x,a20 and a31 - Who would be best to talk to about making use of it?
<mnemoc>
it's a mailing list. you can't delete/edit posts
<mnemoc>
stuff is already sent to everyone's mail
<vinifm>
ok
<vinifm>
Does anyone know why all printk is shown twice when using stage/sunxi3.0 on a13-olinuxino-micro?
<hramrach>
why can't you diff a moved file in git?
<vinifm>
sorry, i did not understand
<hramrach>
vinifm: that's unrelated
<hramrach>
the double printk is probably due to early console not going away when the regular console is enabled
<hramrach>
note that early messages only apper once
<Turl>
hramrach: you can, use the -M flag to find renames
<hramrach>
Turl: I have the file *everywhere* but whatever file I diff git always diffs with /dev/null
<Turl>
did you change the file much?
<hramrach>
and, I already did git mv but I want to swap the mv with some changes to the file
<Turl>
if it's too different it'll consider it a different file
<Turl>
you can use -C to find copies too
<hramrach>
that's completely fine
<hramrach>
so long as it diffs the damn file with whatever I have on disk
<Turl>
there's also --find-copies-harder
<hramrach>
it's right there. in *both* the place from where the file was moved from and in the destination
<hramrach>
but git uses /dev/null, not the on-disk file
<hramrach>
well, you check out the latest commit, move the file someplace else, roll back before the move, move the modified file back, get diff :s
<hramrach>
but without such dances git is totally unable to give you diff of a file that has moved. Because you told it you moved it. so whtever is on the disk cannot possible be the moved file, right?
<hramrach>
you mean it is always disconnecting and reconnecting?
<hramrach>
not sure I saw exact smae thing
<hramrach>
but wpa_supplicant is definitely a piece of software that breaks in various ways
<hramrach>
try a different version if avalilable in your distro
<vinifm>
it is deauthenticating itself
<hramrach>
indeed
<hramrach>
thre is a possibility that reason 3 has some actual meaning
<hramrach>
and different configuration whould not trigger it perhaps
<hramrach>
but the damn thing ahs printf so it could tell you what reason 3 is
<vinifm>
could be driver?
<hramrach>
if you really want to know find a wpa_supplicant mailing list or whatever
<hramrach>
or use gdb ;-)
<hramrach>
sadly the time when you do not need gdb to connect to a wireless network has not yet come :\
<hramrach>
does nobody ever use wireless /o\
<hramrach>
vinifm: I have a wifi card that used to work flawlessly sometime mid between squeeze and wheezy
<hramrach>
after upgrade to wheezy it stopped working
<hramrach>
in Fedora it locks up
<vinifm>
:0
<vinifm>
i am using debian squeeze
<hramrach>
the problem is the working version was somewhere in testing in-between, at least for my card
<mnemoc>
hramrach: after this change to sunxi-tools, anything pending regarding nand partitions?
<hramrach>
yes, the kernel patchset on ml
Skaag has quit [Ping timeout: 244 seconds]
<mnemoc>
drachensun's ?
<hramrach>
I just sent one
<mnemoc>
1m
<mnemoc>
oh
<hramrach>
well, his stuff seems low-level from the topic so hopefully not conflicting
* mnemoc
nods
<hramrach>
the patchset I sent only removes part of the nand driver that duplicates partition-generic.c in block
<mnemoc>
drachensun: btw, I have the source-drop related commits on hold until I finishing putting up the sanitized lichee3 tracking branches. need to have a clear idea of what is merged and what's not.
<mnemoc>
drachensun: shouldn't pass from this weekend
<hramrach>
btw I suspect the sunxi partitioning code was bogus to begin with because it gives weird minors to the partitions
<hramrach>
but also by using partition-generic we lose the sinxi ioctls to make partitions ro/wo/no-access
<hramrach>
I am not sure they are available for generic partitions and I have no idea if not implementingthem would break something on android
<hramrach>
sure I would not mind having nanda accessible again but the ioctl failing might get noticed if they have error checking
<drachensun>
drachensun: Ok
<drachensun>
mnemoc: ok
<drachensun>
oops
Skaag has joined #linux-sunxi
<Turl>
hramrach: basically what we need to make sure of is
<Turl>
hramrach: 1) does it still expose nanda, b, etc as before by default?
<Turl>
hramrach: 2) can you mount -o ro /dev/nandX /somewhere?
<Turl>
and I think that's it
<hramrach>
Turl: 1) is done
vinifm has quit [Quit: Saindo]
<hramrach>
2) is done by the generic partition code, just tested
<hramrach>
the remaining problem is you can't build nand as module now
<hramrach>
which was introduced by the first patch which did generic partitions
<hramrach>
it links sumbols from nanda
<hramrach>
nand*
<Turl>
well, most people make it builtin
<Turl>
but that's no excuse for breaking the module support
<hramrach>
well, I did not break it
<hramrach>
but removed the code that was used before ;-)
<mnemoc>
jochensp: will publish the stuff soon. need to sanitize a couple of things more
<jochensp>
mnemoc: some new audio drivers for the A10 in there as well?
<mnemoc>
haven't had time to review the new a10 code yet, but there is quite a bunch of code to review/merge, so I need to push decent sanitized branches so people can review their favourite soc/subsystem and merge what's valuable
<jochensp>
mnemoc: awesome, will have a look when it's published
<Turl>
mnemoc: try merging this > git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git timers-v3.4-rc4
<Turl>
they probably cherrypicked it
<jelly-home>
I've done some testing of SATA on a cubieboard, and it seems it uses quite a bit of cpu. In addition, it had issues talking to a consumer SSD on 3.0Gbps speeds when I tried to dd the whole disk. http://paste.debian.net/239224/ The transfer got stable after reneg. to 1.5Gbps and pulled a decent 110MB/s. sata on A10 does DMA, right?
<mnemoc>
Turl: will push it based on android-3.3 + v3.3 for now
<Turl>
jelly-home: what A10 hardware revision are you using?
<Turl>
it's printed on dmesg early on boot
<jelly-home>
this? [ 0.000000] chip-id: A10 (AW1623 revision C)
<Turl>
yeah
<Turl>
jelly-home: what cpu governor are you using btw?
<jelly-home>
interrupt count / MB looks about the same as ahci on an intel H55 chipset, around 8 per 1MB read = 900/s, so I _guess_ it does DMA not PIO
<jelly-home>
Turl: ondemand with 400-1000MHz, it goes up fairly early on and stays at 1GHz
<Turl>
there should be DMA support on the hardware
<Turl>
jelly-home: if you set it to performance and run the same test, can you spot what's eating the cpu time?
<jelly-home>
from top: dd_rescue 65% kswapd0 10-18% (even after I disabled all swap)
<Turl>
iirc kswapd also handles freeing of pages and compaction
<jelly-home>
from vmstat, 0-1% user, 92% system, 7-8% iowait
<jelly-home>
so... cache usage and/or memory bandwidth is not that well on (this) A10?
<Turl>
anything interesting on /proc/<pid>/stack ?
<jelly-home>
of dd_rescue? Lemme see.
<Turl>
yes
<jelly-home>
huh, no stack in /proc/.../ on this Linux version 3.4.24-a10-aufs+ (max@lynx) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1) ) #1 PREEMPT Sun Jan 27 00:28:21 CET 2013
<jelly-home>
(it's not my kernel, but the berryboot-a10's one, seemed based on stage/sunxi-3.4)
<Turl>
google says you may need to enable CONFIG_STACKTRACE to use it
<Turl>
(which sounds sensible, but I haven't checked)
<jelly-home>
could be, # CONFIG_STACKTRACE is not set, and it's present on my pc workstation where there is /proc/*/stack
Skaag has quit [Ping timeout: 245 seconds]
* jelly-home
can only go so far without having to build a kernel
<Turl>
:)
Skaag has joined #linux-sunxi
<jelly-home>
amusing thing, if I let some mplayer play music (off a nfs share unrelated to sata) at the same time, it takes 10% cpu but it's subtracted off _kswapd0_ not the dd userspace
<jelly-home>
perhaps I should not trust these numbers
<mnemoc>
Turl: there is something else missing between the v3.3 and the timers patch. but we need to compose a sane base.