<gzamboni>
mnemoc its the 2.8V required for the camera sensor
<mnemoc>
gzamboni: those those have some logic or just dumb VCC 2V8 ?
<mnemoc>
rm: :)
<gzamboni>
just dump vcc2v8
<gzamboni>
its named like that as the csi is the only place that need this voltage
<gzamboni>
you gotta check if the camera sensor you will use needs 1.8V also
<gzamboni>
there are some camera sensors with an internal regulator and others without
<gzamboni>
my pcb is in the revision state, i think tomorow it will be done
<gzamboni>
if you want i can send you the schematics in about 4 hours as they are not here in this pc
hipboi has joined #linux-sunxi
<gzamboni>
nice board rm
<gzamboni>
didnt know this one
<gzamboni>
hi hipboi, can i /q ?
<hipboi>
gzamboni: hi
<mnemoc>
gzamboni: that would be great. thanks. and thanks for the info. I'll adjust the wiki page accordingly.
<mnemoc>
wb hipboi!
<hipboi>
hi
<hipboi>
the last week we are busy with moving and declorating the office
<mnemoc>
nice :) in zhuhai?
<hipboi>
yes
<oliv3r>
hipboi: Cubieboard A20! Any idea's yet? :)
<gzamboni>
ok mnemoc
hipboi has quit [Remote host closed the connection]
<oliv3r>
fine! leave!
hipboi has joined #linux-sunxi
<gzamboni>
he answered you
<gzamboni>
with acts
<oliv3r>
lol
<hipboi>
A20 is taped out now
<oliv3r>
so hipboi, any idea/eta/info on CubieBoard A20
<hipboi>
allwinner is debugging the chip
<oliv3r>
oh nice, that's good right?
<hipboi>
not sure when they will release the source code
<oliv3r>
I saw some software support dumps here and there, so it's going well?
<oliv3r>
are they planning on it?
<hipboi>
isn't there is a mysterious guy leaked the source code?
<oliv3r>
I guess I should have said, is allwinner planning on releasing it officially?
<oliv3r>
tbh, they should just put their git public :p, or atleast push stuff occasionally there when it's release time :p
<hipboi>
they would not release publicly
<oliv3r>
so they leak instead :p I guess that's 'just as good' as complieing in this sense
<oliv3r>
hipboi: I have heard that allwinner has sanctioned that the A13 datasheet was allowed to be shared publically
<oliv3r>
(it's identical to the A10 one we allready have, the one from the ML, with sections masked of course)
<oliv3r>
hipboi: any plans on the A20 datasheet?
<oliv3r>
or do we have to hope for a leak there aswell?
<hipboi>
hope for a leak
<hipboi>
leaking is publishing....
<hipboi>
in some way
<hipboi>
mnemoc: where did you push the leaked a31 source code?
<mnemoc>
on my github
<hipboi>
ok, i see it
<mnemoc>
it's from the first leak, without history
<mnemoc>
s/leak/source drop/
<hipboi>
there is tag
<oliv3r>
hipboi: cloudsto announced a few A20 'to be expected mid-march' how likly do you think that will be? I guess cubeboard 2 won't make it by that time?
<hipboi>
mid-march?
<mnemoc>
hipboi: from a10/a13/a10s sources, those are in the lichee/ branches of my github
<mnemoc>
still need to make a sanitization branch, preserving the history, but fixing encoding, ^M and whitespacing
<gzamboni>
anyone have/know the pinout of this marsboard gpio ?
<mnemoc>
lichee/ branches are pristine
<mnemoc>
gzamboni: mail them :)
<gzamboni>
will do so
<hipboi>
reuuimllatech.com
<hipboi>
i named it before i left allwinner
<oliv3r>
I'm so excited for those branches. Intentionally or not, it deserves a padding on their shoulder for leaking it :)
<mnemoc>
hipboi: was the reuuimlla word invented by you or your boss?
<hipboi>
me
<mnemoc>
it's nice :)
<hipboi>
i replaced all allwinner to reuuimlla
<jinzo>
but the domain isn't even registered? Could be quite a fun phising target.
<oliv3r>
i guess if I search the wiki for awutils i'll find interesting stuff
<mnemoc>
hope so
<oliv3r>
nothing
<hipboi>
there is a window tool
<hipboi>
called unimg
<hipboi>
to extract the livesuite image
<hipboi>
written by a Chinese boy
<hipboi>
at the time of F20
<mnemoc>
sure, but I prefer to promote the open tool ;-)
ganbold_ has joined #linux-sunxi
<oliv3r>
who is this ithmar anyway and why did he write that?
<mnemoc>
a gut from .nl
<mnemoc>
guy*
<mnemoc>
libv knows him
<libv>
he did telechips stuff a few years ago
<libv>
the only one touching telechips tablets with a clue
<oliv3r>
ah, hup holland hup :p
<oliv3r>
i was just supprised as i'd imagine it falling somewher under linux-sunxi, a wiki page or him idleing here
<mnemoc>
hipboi: who ever is in charge of drivers/usb/serial/option.c in allwinner's kernel. I hate him
<hipboi>
me too
<mnemoc>
*g*
hipboi has quit [Quit: Leaving]
FergusL has left #linux-sunxi ["Quit"]
<oliv3r>
sweet, that works, it decompressed the image and inded the script.bin (seems uncompressed) is in there
<oliv3r>
seems in fex format
<arete74>
oliv3r:was is the name the file "script.bin" after decompress image?
<oliv3r>
12345678_1234567890script
<oliv3r>
2014 bytes
<oliv3r>
speaking of, do we have a 'most basic script.bin' that we could use to base our device uppon? I mean, we know that script.bin just gets copied and some minor modifications done to it
<oliv3r>
so a bare minimum to 'start from' would be nice, no?
<oliv3r>
ZaEarl, try using gcc-4.6.3 from linaro
<rz2k>
anyone designed boards with a13?
<oliv3r>
rz2k: anyone here? or generally?
<rz2k>
cant find ball-to-die info for ddr3 routing
<rz2k>
here
<mnemoc>
rz2k: Tsvetan must have the reference design
<rz2k>
cant ask olimex for doing support instead of allwinner
<rz2k>
dont ask why :p
<mnemoc>
but you can ask for the pdf
<mnemoc>
it might even be in olimex's github
ganbold has quit [Ping timeout: 255 seconds]
ZaEarl_ has joined #linux-sunxi
gzamboni has quit [Read error: Connection reset by peer]
gzamboni has joined #linux-sunxi
wingrime has joined #linux-sunxi
rellla has quit [Ping timeout: 272 seconds]
hansg has quit [Quit: Leaving]
rellla has joined #linux-sunxi
<wingrime>
mnemoc: when you will make patch review ?
<mnemoc>
wingrime: what patch exactly? pretty busy with work and cleaning/rebasing the history of the A10/A13/A10s/A20/A31 code I got
<wingrime>
[PATCH] ft5x_ts:enable power port hardware featue
<wingrime>
this is a last patch for support ft5x_ts for my hw
<mnemoc>
wingrime: will need an ack from drachensun and techn for that
<techn__>
mnemoc: wingrime: I gave comments about coding convension
<techn__>
wingrime: asked if he can do patch afterwards for whole driver :/
<wingrime>
techn__: I followed driver code style, if you wanna make do driver cleanup for code style I think it better do in separate patch afterwards
<wingrime>
techin__: I can make some driver cleanup
<techn__>
wingrime: ft5x_set_reg(FT5X0X_REG_PMODE, PMODE_HIBERNATE); , should that be done on suspend.. if it makes controller do some power save stuff?
<wingrime>
techin__: if HW have power port feature I simply poweroff TS IC
<techn__>
or will pin control shutdown whole chip?
<wingrime>
yes, thats why it not worked when I tested it first time
<wingrime>
i do some IDA investegation and saw this stuff
<wingrime>
if this pin set to 0 chip not answer over I2C
<wingrime>
just timeout messages
<wingrime>
also there was IRQ problem , but it already fixed
<wingrime>
techn__: so what should I do ?
<techn__>
wingrime: I found other improvement.. I'll send it to ML
<mnemoc>
wingrime: about style, in this context it's prefered to fix style on the go. new code must have correct linux style, and only lines affected by code changes get fixed
<mnemoc>
and allwinner doesn't have a code style at all. they don't even care to align the lines within the same if () { }
<wingrime>
techn__: ok
<wingrime>
if I send fixed patch will it be attached to same thread on ML?
<techn__>
wingrime: that's good question.. dunno the practice :/
<mnemoc>
wingrime: git-send-email supports arguments for that
<mnemoc>
you give the id of the mail you are replying, and the new mail is composed accordingly
<wingrime>
example please
<techn__>
mnemoc: is that prefferred way.. Even though I have used that reply-to feature
<techn__>
?
<wingrime>
and where can I get this "id"?
<mnemoc>
techn__: it's supposed to work.... haven't tried myself
<wingrime>
techn__: I not very sure that reset is mandatory after hibernate but this code actualy not mine, i think that wake up is only one have to be done but it need invetegate