Renard has quit [Read error: Connection reset by peer]
diego71_ has quit [Remote host closed the connection]
diego71 has joined #linux-sunxi
hipboi has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
pietrushnic has joined #linux-sunxi
hipboi has quit [Ping timeout: 240 seconds]
hipboi has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
rafaelMOD has quit [Remote host closed the connection]
xavia has joined #linux-sunxi
pietrushnic has quit [Ping timeout: 250 seconds]
link0 has quit [Read error: Connection reset by peer]
link0 has joined #linux-sunxi
TheSeven has quit [Ping timeout: 272 seconds]
TheSeven has joined #linux-sunxi
ricardocrudo has quit [Ping timeout: 250 seconds]
Skaag has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
Skaag has quit [Quit: Leaving.]
Skaag has joined #linux-sunxi
Skaag has quit [Quit: Leaving.]
Skaag has joined #linux-sunxi
indy has joined #linux-sunxi
leviathanch2 has joined #linux-sunxi
philippe_fouquet has joined #linux-sunxi
HeHoPMaJIeH has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-sunxi
akaizen_ has joined #linux-sunxi
philippe_fouquet has quit [Remote host closed the connection]
philippe_fouquet has joined #linux-sunxi
akaizen has quit [Ping timeout: 272 seconds]
philippe_fouquet has quit [Ping timeout: 260 seconds]
Tinut has joined #linux-sunxi
philippe_fouquet has joined #linux-sunxi
Tinut has quit [Client Quit]
Tintu has joined #linux-sunxi
<Tintu>
hello...
<Tintu>
i'm using A20 hummingbird ... i connected a 4.3 inch LCD to it... Modified fex file for 480*270 resolution as described in the fex guide.. Display works.. But an error "Unfortunately system UI has stopped" appears.. How can i fix thi problem?
<hno>
hramrach_, what have always worked for me on all SoC generation is to load u-boot.bin from the Allwinner "soft FEL" mode, i.e. the FEL mode triggered from boot1 by holding a button during boot or pressing a number (3? don't remember) on the console during boot.
<hno>
The Allwinner FEL blobs may need some additional data sent before executed. Don't remember full details, see FEL USB dumps. And it's more than one Allwinner blob before DRAM is initialized.
<Tintu>
can you tell me why this error occured?
leviathanch2 has quit [Ping timeout: 260 seconds]
Nyuutwo has quit [Ping timeout: 246 seconds]
<hno>
Tintu, sounds like a problem with whatever user inferface you are running.
<Tintu>
we modified the fex file for 1024*768 resolution and viewed through hdmi ... it works with no error.. !! is there any problem with 480*272 resolution?
leviathanch2 has joined #linux-sunxi
philippe_fouquet has quit [Remote host closed the connection]
<JohnDoe_71Rus>
Which interface? Perhaps the interface is not designed for small resolution.
<Tintu>
okay.. how can we remove the error message... ?
megal0maniac has quit [Ping timeout: 260 seconds]
megal0maniac has joined #linux-sunxi
Akagi201 has joined #linux-sunxi
<lauri>
Hi, has anyone set up btrfs root with Cubietruck?
Quarx has joined #linux-sunxi
<hno>
Tintu, by removing the broken user interface?
cazzacar1a is now known as cazzacarna
Tintu has quit [Ping timeout: 246 seconds]
leviathanch2 has quit [Ping timeout: 245 seconds]
pietrushnic has joined #linux-sunxi
hansg has joined #linux-sunxi
hansg has quit [Client Quit]
popolon has joined #linux-sunxi
FR^2 has joined #linux-sunxi
ah has joined #linux-sunxi
philippe_fouquet has joined #linux-sunxi
<rellla>
ssvb: what was the reason, why un-forking of linux-sunxi failed a time ago? should we try to initiate this again?
leviathanch2 has joined #linux-sunxi
afaerber has joined #linux-sunxi
leviathanch2 has quit [Ping timeout: 272 seconds]
<hramrach_>
hno: the FEL mode is entered by a button, yes
<hramrach_>
the u-boot on the tablet helpfully reports everything on SD uart so you see it boot, then notice the button and then it starts FEL mode. Even prints a message about it
philippe_fouquet has quit [Remote host closed the connection]
philippe_fouquet has joined #linux-sunxi
<philippe_fouquet>
Hi
<philippe_fouquet>
some body know on SoC A20 whitch power used by rtc_vcc pin ?
Net147 has joined #linux-sunxi
_massi has joined #linux-sunxi
leviathanch2 has joined #linux-sunxi
hipboi has quit [Ping timeout: 260 seconds]
Nyuutwo has joined #linux-sunxi
Renard has joined #linux-sunxi
<hramrach_>
philippe_fouquet: it has something to do with RTC so presumably the rtc backup battery would get somewhere around there
<philippe_fouquet>
where?
<hramrach_>
1) A20 datasheet 2) reference schematic that presumably came with your DDK 3) possibly a reference AW schematic that can be found on the net somewhere 4) CT schematic which has the battery mounted
<philippe_fouquet>
ok thant I search
_massi has quit [Remote host closed the connection]
<wens>
To create your new page, open a new window or tab in your browser, type http://linux-sunxi.org/, immediately followed by the Manufacturer of your device, then an underscore _, then the Name of your device, and go to that URL. The wiki will then offer you to create that page.
<wens>
maybe some people are taking it too literally... :/
<philippe_fouquet>
wens: you know how many uA it must have on A20 RTC_RTC? I din't find it in datasheet, i find the voltage but not theamperage
ddc has joined #linux-sunxi
Renard has quit [Ping timeout: 250 seconds]
MY123 has quit [Quit: Connection closed for inactivity]
ddc has quit [Ping timeout: 276 seconds]
<alexvf>
mripard: just FYI, the bug related to interrupts is only reproducible when using gdb, so most likely caused by gdb in some way
<alexvf>
mripard: i tried to compile the kernel without CONFIG_HOTPLUG_CPU, in order to force the PIC to send interrupts to all cpu's but have no success
philippe_fouquet has quit [Remote host closed the connection]
philippe_fouquet has joined #linux-sunxi
<mripard>
alexvf: ?
<mripard>
what's the relation between CONFIG_HOTPLUG_CPU and the interrupts?
xavia has joined #linux-sunxi
<alexvf>
based on the darticles i have read, it allows PIC to work in logical-mode
<alexvf>
i was on the idea, that interrupt was being handled by the wrong cpu
philipp__ has joined #linux-sunxi
philippe_fouquet has quit [Ping timeout: 240 seconds]
<mripard>
"you will get similar situation with probably any kernel newer than 2.6.10"
<mripard>
definitely looks up to date...
<mripard>
the kernel is 10 years old....
<alexvf>
but it makes sense that, if you don't have hotplugable cpus, PIC can divert interrupts to all cpus
<alexvf>
i don't know if that was the problem but i gave it a try
<alexvf>
and i don't have any other idea as how to fix this weird behaviour
<alexvf>
once i have checked that it only happens with gdb, i can live with it ... and i have to
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 264 seconds]
philipp__ has quit [Remote host closed the connection]
<mripard>
alexvf: no, the interrupts can be executed by any of the online CPUs
<alexvf>
but then, it have to be notified to the appropiatte one, no?
<alexvf>
in this case, a thread is waiting for a interrupt to be handled
<alexvf>
what seems to happen here is that it never realizes it has been handled
<alexvf>
so there is a problem at some point that prevents that information reaching that thread/cpu
<mripard>
any CPU can execute any piece of code. So the interrupt handler might run on a CPU, and your thread on another one, and it's completely fine.
<mripard>
precisely because the interrupt code doesn't have any idea about what will be woken up
<mripard>
(if there's anything to wake up)
<alexvf>
yes, i understand that
<alexvf>
but the semantics of the ioctl is "wait for an interrupt to come"
<alexvf>
it doesn't matters which cpu handles the interrupt
<alexvf>
but the cpu executing the ioctl must know that it has been handled
<alexvf>
that's why i was expecting that handling the interrupt in the same thread that is waiting would mask the actual problem that the system is showing
<alexvf>
sorry, i meant *the same cpu*
HeHoPMaJIeH has quit [Quit: Konversation terminated!]
<mripard>
1/ an interrupt is not handled in a thread
<lauri>
ssvb: Okay I got the u-boot you revision you pointed out
<alexvf>
i meant a cpu
<libv>
wens: i only just added that
<wens>
libv: oh, then i have no clue :(
<lauri>
ssvb: I am stuck with uEnv config
<lauri>
ssvb: It attempts to boot from TFTP
<mripard>
alexvf: and then, again, when the interrupt is handled, the kernel has no idea of what it's going to do. So you have no way to know on which CPU to run it
<mripard>
more likely it's the thread itself that will be migrated to the CPU that has handled the interrupt.
<alexvf>
mripard: i know
<alexvf>
so again, definitely there is a problem with the ioctl that is unable to realize that the interrupt has been handled (and please, let's forget that i thought that handling the interrupt in the same cpu than the ioctl would make a difference)
<mripard>
then why are you still chasing after the CPU affinities and everything, while you know that you're aiming at the wrong target?
<alexvf>
no, i'm not chasing after that anymore
<alexvf>
it was a test
<alexvf>
failed, because my crazy guess was wrong
Wes- has joined #linux-sunxi
cubear has joined #linux-sunxi
<alexvf>
one takes crazy guesses when it doesn't have any idea why something is not working as it should
Andy-D has joined #linux-sunxi
pwhalen has quit [Ping timeout: 272 seconds]
<mripard>
it really is about: 1) is the interrupt handler running ? 2) If not, why? is the interrupt has been disabled (by who, what for)? is it considered a spurious interrupt? are all the interrupts masked? If the handler is still running, is it waking up the wait queue? if it does, why doesn't the wait queue returns?
<mripard>
once you will have done that, maybe you'll have a better view at what's going on
konradoo77 has joined #linux-sunxi
<alexvf>
mripard: is there a way i can test 1) without recompiling the kernel?
<alexvf>
if so, i can test it now, if not ... i don't know if it pays the prize
<alexvf>
even if i'm able to do it with my kernel knowledge (limited as you can see)
<mripard>
look at /proc/interrupts, it should give you an idea
<mripard>
but you won't be able to really debug this without recompiling your kernel.
konradoo77 has quit [Ping timeout: 272 seconds]
nove has joined #linux-sunxi
pwhalen has joined #linux-sunxi
pwhalen has quit [Changing host]
pwhalen has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
F1skr has quit [Quit: WeeChat 1.0]
<alexvf>
mripard: it stops handling interrupts
<alexvf>
85: 143334 0 GIC cedar_dev
<alexvf>
once i see that the decode function times out, that number never grows
<alexvf>
and /proc/irq/85/spurious neither
<alexvf>
count 43334
<alexvf>
unhandled 0
<alexvf>
last_unhandled 0 ms
<alexvf>
forever
<alexvf>
what a coincidence, 143334 interrupts, 43334 spurious
<alexvf>
hmmm
<alexvf>
well, if a decide to debug this into the kernel i'll let you know the results
<ssvb>
lauri: however, if it even tries to boot from TFTP, then the cubietruck 600MHz dram clock speed settings should not be totally bad ;-)
<ssvb>
lauri: once you get it booting from the sd card, be sure to do a lima-memtester run
<ssvb>
libv: received the 10" tablet
konradoo87 has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 272 seconds]
<ssvb>
libv: maybe I'm really spoiled, but my first impression is that it is a piece of crap :-) Not sure that paying 90 euro for everything (including postage cost) was really worth it
<libv>
ssvb: you should have the right to send it back
<ssvb>
libv: it is apparently even not allwinner
<libv>
then definitely send it back
<libv>
ssvb: what is it that you are looking for anyway?
<libv>
why did you pick exactly this device?
<ssvb>
libv: because the seller claimed that it is allwinner a20
konradoo77 has joined #linux-sunxi
<libv>
ssvb: so you were just looking for an a20 tablet?
<ssvb>
yes
<libv>
any a20 tablet?
<ssvb>
any a20 with hdmi
<libv>
does it have to be new?
konradoo87 has quit [Ping timeout: 245 seconds]
<ssvb>
sigh, first I'll try to identify what kind of hardware is used in this one
<libv>
adb, dmesg :)
dantob has joined #linux-sunxi
<libv>
there are two used ones which look like an inet k100 on ebay right now, if you want to, i'll bid on it and mail it over
<libv>
heh, one says rk30sdk in the about tablet *sigh*
<ssvb>
libv: actually I'm taking it back, maybe it is still allwinner a20
<ssvb>
libv: this "hardware info" application might be just bogus
<libv>
ssvb: adb is where it is at :)
<ssvb>
libv: yeah, I see two cores in /proc/cpuinfo and some references to mali in /dev
<libv>
dmesg should tell you all you need to hear
<paulk-collins>
libv, who is reviewing what goes in linux-sunxi's sunxi-3.4? I'm afraid my patches will be forgotten if I don't insist… What's the way to go here?
<libv>
paulk-collins: mnemoc
<libv>
i still need to look into your uart patch
<paulk-collins>
libv, ok, but note that it doesn't break current setups and is separate from your earlyprintk patch
<libv>
yeah
<libv>
dack: at this point, english is my third language.
<Wes->
Does it need to be a tablet? If not, you might look at olimex A20-OLinuXino-LIME
<dack>
libv: ga?
<dack>
libv: was that comment intended for me?
<libv>
dack: you just swapped oktober to october
<libv>
2 out of my 3.5 languages write it as oktober :)
<dack>
libv: ah.. :)
<dack>
libv: which languages? German, dutch, something else?
<libv>
dutch is my mother tongue, i spend my days talking german and typing english
<dack>
libv: Chinese keeps it simple... "10th month" who really needs names?
<libv>
dack: tbh, i still don't really get why we don't have 13 months of 4 weeks exactly
<dack>
libv: I'm also mono-lingual, so my brain organizes everything as "English" or "Not English"
<dack>
libv: there's not exactly 52 weeks in a year... but the months having all different amounts of days isn't particularly useful
<libv>
dack: 52 weeks and 1 day
tomboy64 has joined #linux-sunxi
<libv>
and another for a leap year of course
<dack>
I guess 13 months with 14 weeks with one having that extra day and possible leap day would make more sense
<libv>
new years could be right after sunday, and monday could start the day after new years
<libv>
sadly, thirteen is a cursed number or such
tomboy65 has quit [Ping timeout: 264 seconds]
<dack>
libv: well, part of it is a month is supposed to be a lunar cycle... 29.5 days
nove has quit [Quit: nove]
<dack>
libv: then I think they didn't have enough days in the past and just stuck them on the different months to stop seasons drifting
<libv>
yeah, seasons are more important
<dack>
it was developed like spagetti code... little bits all over the place with little organization over top
<libv>
but people who would like to switch to something sensible would have to claim to be religious first
<libv>
and then would have to have all sorts of useless illogical bullshit for people to believe that this is truly a religion
<libv>
so perhaps we should just keep using october/oktober
<dack>
I think the 7 days in a week is the only thing with religious connotations...
<dack>
I don't think I could manage a 10-day week...
Skaag has quit [Quit: Leaving.]
<libv>
:)
<libv>
ooh, even days hours and minutes were decimalized
MY123 has joined #linux-sunxi
dantob has quit [Quit: dantob]
<libv>
ssvb: did you find out anything more?
Gerwin_J has quit [Quit: Gerwin_J]
<ssvb>
libv: yes, a lot of weird stuff in dmesg, I'll paste it somewhere a bit later
Zboonet has quit [Ping timeout: 240 seconds]
<libv>
ssvb: any closer to what the hw is supposed to be?
pwhalen has joined #linux-sunxi
tomboy64 has quit [Remote host closed the connection]
tomboy64 has joined #linux-sunxi
<ssvb>
libv: it is charging the battery for the first time (which supposedly should not be interrupted), too far from my PC to connect the USB cable for adb
<ssvb>
libv: however it is rooted out of the box and I could see the dmesg log in the terminal application on the device itself
Andy-D has quit [Read error: Connection reset by peer]
<libv>
full refund sounds like the postage should be included.
<libv>
this is very much not as advertised
<ssvb>
crap, I missed this review comment :(
<libv>
it happens, and it is not your fault
<ssvb>
on the other hand, I may just keep it, because this tablet apparently has a quad core Cortex-A5 CPU to fill the missing slot in my ARM CPU cores collection
<ssvb>
naobsd: yes, but it wants me to install a browser plugin, which raises a big red flag :)
<naobsd>
ssvb: same for me. so I started firefox(non-used for daily purpose) and downloading now :)
<naobsd>
I often run "rm -rf ~/.mozilla" :)
<naobsd>
ah, I should make dummy user for it ;)
xavia has quit [Remote host closed the connection]
<naobsd>
ssvb: if you need, I'll put somewhere
pwhalen has joined #linux-sunxi
<ssvb>
naobsd: do you have any devices with this SoC?
<naobsd>
ssvb: no
<ssvb>
libv: leaving the SoC alone, does your 10" tablet also have a very poor quality display with really bad viewing angles and a somewhat grainy picture?
<libv>
ssvb: no idea :)
<libv>
it came with a broken android, and it sitting in a drawer waiting for a serial connector to be soldered on and for me to get to LVDS bringup :)
<libv>
but i guess so
<libv>
the displays on these types of devices barely every change
FreezingCold has quit [Ping timeout: 272 seconds]
<naobsd>
ssvb: download finished. do you need it?
phh has quit [Quit: No Ping reply in 180 seconds.]
<ssvb>
naobsd: yes, sure, thanks
phh has joined #linux-sunxi
<libv>
heh
<libv>
i just realized that the grandaddy of ndh is about to get proper board pictures :)
<naobsd>
ah, please wait another 10min or so for uploading
yann_s has quit [Ping timeout: 272 seconds]
yann_s|AFK has joined #linux-sunxi
<ssvb>
libv: about the sunxi u-boot, not sure if it was really useful, but I tried to populate a trello board with some to-do items to make it more clear what's going on - https://trello.com/b/jFRe2Hx3/sunxi-bsp-v2014-10
yann_s|AFK is now known as yann_s
<ssvb>
libv: and I had a hope that I could already start doing some practical tests of this stuff on the new tablet...