<libv>
uart 0 is not wired to anything, that's what hramrach proved yesterday
<libv>
on a13
<libv>
but it stops a10s dead to use uart1 indiscriminately
<libv>
3.4.102+ works just as fine as 3.4.61+
<libv>
when the proper uart is chosen
<libv>
so... i'll go and inverse the uarts in sun5i defconfig, and document the difference
<libv>
and i'll go test the default on some a13 hw as well
techn has quit [Read error: Connection reset by peer]
xavia has quit [Remote host closed the connection]
cajg has quit [Ping timeout: 268 seconds]
hipboi_ has quit [Read error: Connection reset by peer]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
Guest92904 has quit [Read error: Connection reset by peer]
buZz has joined #linux-sunxi
buZz is now known as Guest4153
hipboi_ has joined #linux-sunxi
pwhalen has quit [Ping timeout: 240 seconds]
xavia has joined #linux-sunxi
hipboi_ has quit [Ping timeout: 252 seconds]
pwhalen has joined #linux-sunxi
hipboi_ has joined #linux-sunxi
skaag has joined #linux-sunxi
skaag has quit [Client Quit]
skaag has joined #linux-sunxi
naobsd has quit [Quit: Page closed]
skaag has quit [Quit: Leaving.]
allen has joined #linux-sunxi
<allen>
hello ,i want know whether lubuntu support Sleep and wakeup through Power Enable Key(PEK)? Who can give me tips ? Thank you very much !
<allen>
i found the distro of cubieboard can't sleep ,it is die when i type "echo standby > cat /sys/power/state "
rafaelMOD has joined #linux-sunxi
hramrach has quit [Ping timeout: 264 seconds]
hramrach has joined #linux-sunxi
TheSeven has quit [Ping timeout: 272 seconds]
TheSeven has joined #linux-sunxi
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
\\Mr_C\\ has joined #linux-sunxi
Gerwin_J has quit [Ping timeout: 250 seconds]
Gerwin_J has joined #linux-sunxi
xavia has quit [Ping timeout: 255 seconds]
Gerwin_J has quit [Quit: Gerwin_J]
xavia has joined #linux-sunxi
lynxis_ has joined #linux-sunxi
lynxis has quit [Read error: Connection reset by peer]
naobsd has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
skaag has joined #linux-sunxi
mmarker1 has quit [Remote host closed the connection]
mmarker has joined #linux-sunxi
amitk has joined #linux-sunxi
\\Mr_C\\ has quit [Quit: .]
xavia has quit [Quit: Leaving.]
cubear has joined #linux-sunxi
hipboi_ has quit [Read error: Connection reset by peer]
PulkoMandy has joined #linux-sunxi
rafaelMOD has quit [Quit: Leaving]
hipboi has joined #linux-sunxi
philippe_fouquet has joined #linux-sunxi
<JohnDoe_71Rus>
Can you help with kernel .config? But for android. Config are similar.
<JohnDoe_71Rus>
I need build modules in kernel, but can only check "M"
Guest4153 is now known as buZz
diego_r has joined #linux-sunxi
y0g1 has quit [Ping timeout: 245 seconds]
Quarx has joined #linux-sunxi
<hramrach>
why do you need in kernel?
<hramrach>
anyway, the feature probably depends on something else configured as module
<hramrach>
and you can load modules in android by hand in some startup script
<hramrach>
JohnDoe_71Rus:
maksimlin has quit [Remote host closed the connection]
<JohnDoe_71Rus>
add wifi support. i can't load module insmod: init_module '/vendor/modules/rt2800lib.ko' failed (No such file or directory) but the same folder module rtl8150 8115 0 - Live 0x00000000 loads
<hramrach>
look in kernel log?
<hramrach>
maybe it depends on something else ?
philippe_fouquet has quit [Ping timeout: 268 seconds]
<hramrach>
the full path does not work because the includes are in $(src) but build seems to happen in $(obj)
<joost_dt1>
quick question: building u-boot-sunxi and having an a20-olinuxino-lime-4gb, should i use A20-OLinuXino_Lime or A20-OLinuXino_Lime2 to build?
<hramrach>
first uses emac, second gmac
<hramrach>
not sure if there is a difference otherwise
<joost_dt1>
oh wait, the GMAC is for possible future GigE
<joost_dt1>
so A20-OLinuXino_Lime it is, nevermind
<hramrach>
no. it's for driving the ethernet port with sane ethernet IP
<joost_dt1>
then i misread the comments of the original patch
<hramrach>
so if you mux it there you have it, if not it goes to /dev/null
<hramrach>
so it's good default for a13 as well
<hramrach>
and probably the reason I have it in my config
Andy-D has joined #linux-sunxi
<hramrach>
A13 olinuxino has uart1 wired to a connector. that would be an exception
Andy-D has quit [Client Quit]
Wes- has joined #linux-sunxi
<hramrach>
hmm, the mid tablet had uart1 wired to a port too
<hramrach>
but if you have it you should know and if you do not know about or have an uart connector uart0 should work
<Wes->
Hey, has anybody been able to build the latest kernel with iptables enabled? I keep getting stuck with stuff like the error below, and don't know if I should just go ahead and patch the sources, or if I should keep flipping options in make menuconfig and crossing my fingers.
<Wes->
/export/home/wes/sunxi/A10_kernel_3.4/linux-sunxi/include/net/ipv6.h:364: undefined reference to `in6addr_any'
<hramrach>
make ipv6 built-in
<Wes->
hramrach: Thanks - trying this
pwhalen has quit [Ping timeout: 272 seconds]
* rellla
thinks of buying a bananapi for 40€ ... no ndh, but fex in sunxi-boards and seperate kernel fork not merged into ours ...
<hramrach>
what is interesting about bananapi?
<libv>
hramrach: i think this default is only for early printing, before the .fex values kick in
<rellla>
hramrach: for me only the price and the gmac atm
<libv>
but good, uart0 will be the default in the defconfig
<libv>
i need to write up a whole section on determining the u-boot uart in our uart page anyway
<libv>
so i will document that as well
<libv>
rellla: please do, and ndh it :)
<libv>
rellla: that should get some of the disappointed bananapi users over to us
<libv>
because i doubt that many of the more clueful ones will be too happy with it
<wens>
libv: defconfig for what?
<libv>
wens: sun5i
<wens>
libv: for u-boot or kernel?
<wens>
also should check if uart is muxed before or after mmc
<libv>
wens: kernel
<wens>
if uart is muxed after mmc, might break mmc (especially if you're booting from it)
<rellla>
libv: change your username to sth like ndh_nagger :p
<wens>
libv: 3.4 i presume?
<libv>
wens: CONFIG_SW_DEBUG_UART=1 keeps it from booting on A10s and on hramrach his a13 tablet
<libv>
yes
<libv>
by setting that to 0, other a13 devices do not get uart printing until much later
naobsd has quit [Quit: Page closed]
philippe_fouquet has quit [Remote host closed the connection]
<libv>
the mmc stuff will have been properly set by u-boot before
<Wes->
hramrach: That worked perfectly. Thanks for the tip, I would not have thought to try that on my own.
<libv>
the default is the two io pins which are not exported on a13
<libv>
if that was changed by uboot to mux to the mmc pins, then all is ok as well
<wens>
ah, so it's for the equiv. of earlycon
<libv>
wens: probably, i am just 100% certain that this stops my a10s-es from booting
<libv>
and that the side effects for a13 are minimal and much more manageable
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
<hramrach>
wens: I am booting from mmc and it WorksForMe(TM)
<libv>
yeah, the default is probably those two pins which are not exported
<libv>
but can be switched to be those two mmc pins
<libv>
you then need fel loading, so this is all done at uboot time
pwhalen has joined #linux-sunxi
<hramrach>
the default is probably set by u-boot, anyway
<libv>
yes, it is
<libv>
with no uart config, those two pins of uart0 are used for serial
<libv>
now we need to do the same in our defconfig
JohnDoe_71Rus has joined #linux-sunxi
<JohnDoe_71Rus>
hramrach: do you help me?
<hramrach>
ask the question and then maybe somebody answers
<libv>
hramrach: " -> ''' ... i want this to be consistent
<libv>
hramrach: either you go and edit the 101 different pages, or you use " :)
philippe_fouquet has joined #linux-sunxi
<JohnDoe_71Rus>
I forgot who was trying to help me with the kernel modules a couple of hours ago
ZetaNeta has left #linux-sunxi ["Freeing memory"]
<libv>
plus, we probably should be appendign _config to every page
<libv>
but then, that will change again when we move our uboot to the next version of uboot
<libv>
as there things get completely changed again
<libv>
and i hope that they then finally keep things that way for more than a uboot release
<libv>
well, not all the time, i often use either single ' or " as well
<libv>
but you have a point that '' or ''' is easier to select
<libv>
but '' says "this bit of text is literal, and different from the sentence surrounding this", whereas ''' says "it is very important that you read this exact sentence or you will shoot yourself in your foot"
<hramrach>
when used for whole sentence maybe. I use ''' for higlighting the parts that are useful in the text
<hramrach>
because '' does not make the text stand out much and makes it hard to read
<hramrach>
so generally not a good idea for something you want the people to read
<hramrach>
you can get italic almost as good as normal text with good antialiasing but never as good on screen with vertical pixel rows
<libv>
overuse of bold will reduce its value
<libv>
''' is one step up from '' which is one step up from normal text
<libv>
so yes, not using " or ' will make it easier to select and copy
<libv>
but ''' is a step too far
<dack>
''''' for the win! bold and italics!
<hramrach>
I skip '' for the reasons stated above. When I get italics screen then maybe I will start to use it because at least on my screen it will look sane
<JohnDoe_71Rus>
hramrach: any suggest or more logs?
<libv>
and when this change gets instituted, it should be done everywhere, and we should _config everything
<libv>
JohnDoe_71Rus: what are you doing?
<hramrach>
JohnDoe_71Rus: I suggest you keep using the ubuntu pastebin that does not block people out
<libv>
JohnDoe_71Rus: why are you getting all that noise in your log?
<libv>
JohnDoe_71Rus: state hw, what uboot/kernel you are using, etc
<hramrach>
libv: the problem was that he insmods a kernel module without inserting the dependencies first
<libv>
dack: my a10s is close to working, libnand on cubietruck should happen after that
<libv>
hramrach: he has more issues than just that
<hramrach>
on android where there is no sane module loading
<libv>
this log is insane
<JohnDoe_71Rus>
libv: i try add rt3072 wifi support. cubieboard android. i made this with 3.3 kernel but cant repeat with 3.4
<hramrach>
I did nit see the lst log
<libv>
so you added the code for this wifi module to our sunxi-3.4 kernel?
<hramrach>
you can't repeat building the driver or can't repeat the error?
<libv>
JohnDoe_71Rus: this is for a usb wifi stick?
<dack>
libv: woot! I'm _still_ fighting with the supplier to send me a flash image for my device. He finally understood what I wanted a week ago but hasn't been able to figure out how to send me a big file. :P
<hramrach>
so they are probably aware of the driver discrepancy ..
avsm1 has joined #linux-sunxi
Wes-_ has joined #linux-sunxi
<hramrach>
so it's known problem but nobody diagnosed the actual cause
<hramrach>
libv: what are you doing with libnand?
<wens>
libv: ping, where do you want people to put meminfo dumps?
avsm has quit [Ping timeout: 255 seconds]
<libv>
wens: sunxi-boards/meminfo/
<libv>
wens: i have put that in two emails already, but people overlooked it
<libv>
wens: sunxi-boards/meminfo/aXX/
<libv>
like with sunxi-boards/sys_config/
<hramrach>
JohnDoe_71Rus: When I built the first cubieboard2 SD image both drivers were the same. I could access the nand with either the closed driver or the open one. But looks like something diverged somewhere
techn has joined #linux-sunxi
<hramrach>
anybody has some idea about the nand driver here?
<wens>
libv: pushed a31 hummingbird
<wens>
i'll do the a23 tomorrow
<hramrach>
JohnDoe_71Rus: does the android still work?
<JohnDoe_71Rus>
it build full image to write livesuit
<hramrach>
so maybe you need to make clean or whatever and build again. You obvoiusly get different kernel and modules mixed up
<JohnDoe_71Rus>
I started to build again. will be ready tomorrow
<hramrach>
that's why I don't like these SDKs that build everything from start to end in a day .. and hten when something minor goes wrong you have no idea how the build works so you just build for another day and pray that in the end you get something that works
<JohnDoe_71Rus>
build so long only old pc and small RAM
<hramrach>
JohnDoe_71Rus: does the android in flash still work?
<ssvb>
hramrach: actually there is a difference in u-boot dram code, the old sunxi u-boot tried to set MBUS clock speed to half of DRAM clock speed, but rc2 tries to set MBUS to 300MHz by default
<ssvb>
hramrach: this can be overrided in 'dram_para' struct and you can set '.mbus_clock' parameter for each board
<ssvb>
hramrach: oh, it's 2013.10-rc2-08396-g27c7eed-dirty (*2013* not *2014*), u-boot is also ancient :)
<ssvb>
hramrach: "sunxi head" means u-boot from the linux-sunxi github repository?
<hramrach>
yes, that
<hramrach>
setting to 1300 also just stops there
MY123 has quit [Quit: Connection closed for inactivity]
<ssvb>
hramrach: I have not broken the u-boot at linux-sunxi github yet :)
<ssvb>
hramrach: what happens if you try to disable the 'pmu' in fex altogether?
<ssvb>
hramrach: or reduce the dcdc3 voltage also in u-boot (could it be that a sudden voltage drop is bad?)
bertrik has quit [Remote host closed the connection]
paulk-collins has quit [Quit: Ex-Chat]
joost_dt1 has quit [Ping timeout: 240 seconds]
link0 has quit [Remote host closed the connection]
GeertJohan has quit [Ping timeout: 250 seconds]
link0 has joined #linux-sunxi
bengal has quit [Ping timeout: 272 seconds]
GeertJohan has joined #linux-sunxi
GeertJohan has quit [Changing host]
GeertJohan has joined #linux-sunxi
joost_dtn has joined #linux-sunxi
nuptse_ has quit [Quit: Leaving]
<hramrach>
setting both u-boot and fex to 1400 gets me past that point
F1skr has quit [Quit: WeeChat 1.0]
<hramrach>
but it panics or locks up :/
petr has quit [Ping timeout: 245 seconds]
Seppoz has joined #linux-sunxi
<libv>
hrm, we have no-one who is interested in touchscreens it seems
<Seppoz>
i do use touchscreens with A10/20
<Seppoz>
whats the question
<Seppoz>
or what about em (sry)
<Seppoz>
libv: how advanced is the mainlined branch of the sunxi yet? does it have all features the sunxi-linux has
<libv>
well, we seem to have no-one who works our touchscreen page, or who bothers with getting them running and keeping them running
<Seppoz>
oh
<libv>
Seppoz: quite a way to go still, some of it is blocked on my kms work though
<Seppoz>
oh ok
<Seppoz>
im using gt911 products with a10/20 if any1 ever needs any help
<libv>
Seppoz: on many device pages, people complain about their touchscreen or they have some explanation of how to fix things, or at least of what is wrong with sunxi-3.4 support
<libv>
but nobody has gone and unified this information
rafaelMOD has joined #linux-sunxi
<libv>
and i hate it when that has to be me again.
<libv>
as it always seems to be me
<Seppoz>
well you realize that the touchscreen implementation and the gpio implementation on the sunxi brnch is really a pita right?
<Seppoz>
especially the combination of touchscreens into one config and so on
<Seppoz>
makes it really hard to work with
xavia has quit [Read error: Connection reset by peer]
<libv>
i am now fixing up the Along_rt713 page again, and the owner of that is complaining that the ft5x has the axis reversed
<Seppoz>
it took me like 5 days to port the gt911 driver
<Seppoz>
thats just one setting
<libv>
i think i heard this axis reversal several times
<Seppoz>
i believe
xavia has joined #linux-sunxi
<Seppoz>
its just a matter of the config you use for the screen
jinzo has quit [Quit: Leaving]
<libv>
but when i go to the touchscreen page, there is just as much there as when i created it and gave it some structure
lerc_ has joined #linux-sunxi
<libv>
which means that it still has no real content
<Seppoz>
i believe the problem with touchscreens is that they are mostly very specific
<Seppoz>
per device
<Seppoz>
with all the configs and so on
<Seppoz>
its like the stuff with the screens
lerc has quit [Ping timeout: 252 seconds]
montjoie[home] has quit [Ping timeout: 252 seconds]
<Seppoz>
its not like you have a single implemenattion that works with any device
<libv>
but currently, nobody has bothered to document that
<libv>
nobody has bothered to gather the touchscreen knowledge that is out there
<libv>
why or how it does or does not work, nobody has bothered to explain this
<Seppoz>
yea i understand, its not the most easy tho ;P
<Seppoz>
its not that hard
<libv>
everyone just pokes at it a few minutes and then gives up
<Seppoz>
well
<Seppoz>
once you understand how those ts work
<Seppoz>
mainly most are the same
<libv>
i do not want to know or hear that, i want others to be able to find that out easily
<Seppoz>
problem is that most touchscreens require specific stuff from ts producer
<Seppoz>
like a ts profile
<Seppoz>
or eeprom config
<libv>
Seppoz: can you go document your own touchscreen hardware on our touchscreen page?
<libv>
and explain why touchscreen are such a pain in a separate section?
<Seppoz>
yes i guess, its propriotary hw tho
<libv>
it has a driver, no?
<libv>
you said something about having ported it
<Seppoz>
yes
<libv>
oh, but the board that has that driver is proprietary and not commercially available?
<Seppoz>
yes
<Seppoz>
shouldnt matter tho
<Seppoz>
as long as they use same i2c and same gpios
<Seppoz>
also i had to use some tricks in fex file to work around iterrupts and stuff, but i can share that no prob
<libv>
ok, thanks :)
montjoie[home] has joined #linux-sunxi
<Nyuutwo>
afair in my tablet setting up touchscreen was fixing fex file for reversing axis
<libv>
Nyuutwo: which tablet was this?
<Nyuutwo>
k10001l1c
<libv>
ah, ok
<Nyuutwo>
and I'm bad man
<Nyuutwo>
haven't sent patch probably
<Nyuutwo>
it just hangs in git
<Nyuutwo>
on my disk ...
<libv>
Nyuutwo: time to redeem yourself :p
<libv>
as you know, i have that same hw, because you had the issues with lvds
<Nyuutwo>
yup - pll was not initialized in fex
<Nyuutwo>
like manufacturer just hardcoded things bypassing fex
petr has joined #linux-sunxi
<Seppoz>
ctp_exchange_x_y_flag = 0
<Seppoz>
lol
<Seppoz>
must be very hard to change
<Seppoz>
xD
<Seppoz>
people are just to lazy
<libv>
Seppoz: hehe
<libv>
this is a pretty common theme here, yes
tinti has joined #linux-sunxi
<libv>
Seppoz: sounds like that should sit in a "Common pitfalls" section
<Seppoz>
sounds like it should sit in the RTFM section
<Seppoz>
lol
<libv>
Seppoz: our whole wiki is a big RTFM section, but still people refuse to do so
<Seppoz>
i have to admit sometimes asking is more easy
<libv>
yes, and then when you get a link, you should actually go and read that
<libv>
not complain your head off like some :)
<Seppoz>
xD
xavia has quit [Remote host closed the connection]
<libv>
i am so funny.
<libv>
The UART pins are available on the {{Edit|flip}}side of the board, right next to the {{Edit|Fluxcapacitor}}.
buZz has quit [Read error: Connection reset by peer]
buZz has joined #linux-sunxi
Renard has quit [Remote host closed the connection]