mnemoc changed the topic of #linux-sunxi to: Allwinner/sunxi development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
leviathanch2 has quit [Ping timeout: 250 seconds]
protoCall7 has quit [Quit: protoCall7]
physis has joined #linux-sunxi
<Turl> libv: maybe it's something aided by rockchip?
<Turl> they themselves were collaborating upstream now
kuldeepdhaka has quit [Ping timeout: 246 seconds]
<libv> Turl: it does seem very clear that no attempts were made to contact the people behind the mostly defunct linux-rockchip "community"
<libv> so now there are two mls, a dead site/wiki and a github project
<libv> that's not how you revive a community
nedko has quit [Quit: kernel panic]
<libv> Turl: bad luck for hipboi, and it means i have to put more faith in the exynos project
<Turl> the google group has like 3 emails :/
<libv> if any of the originators cares about this project at all, it will get a whole lot more soon
<Turl> libv: they seem to be supporting the rock http://www.spinics.net/lists/arm-kernel/msg355769.html
<libv> Turl: yes, but they did just trample that small seedling of a community that was withering away
<libv> anyway, i am probably way too sensitive over this
<libv> but then, i am never too far away from the Xorg forkers and their actions.
<Turl> libv: they even got a kms driver *hint* :p
<libv> i know
popolon has quit [Quit: Quitte]
zombu2 has quit [Ping timeout: 240 seconds]
<Turl> they're selling banana pi on dx now
<libv> i'm going to get shafted on my first aliexpress purchase :(
<libv> and banana pi...
<libv> i am really saddened that that thing actually sells
<libv> it only sells due to the name and the vague attempt to look the same
<libv> not because it is a useful product
rafaelMOD has joined #linux-sunxi
egbert_ has joined #linux-sunxi
egbert has quit [Disconnected by services]
physis has quit [Remote host closed the connection]
<Turl> libv: you could say roughly the same about the rpi itself :p
<libv> Turl: at least the rpi made the market and did the marketing
Akagi201 has joined #linux-sunxi
rds_ has joined #linux-sunxi
<rds_> Turl: I wonder which of these "dev" boards are actually useful! The Mele seems to be the best for me. Maybe the A80, will change everything. :-)
<wens> mripard_: i still have the patch file i sent, if you need it
<libv> heh, 16 for pll divider is totally acceptable
<libv> but 640x480 on vga is not playing ball yet :(
ganbold_ has joined #linux-sunxi
physis has joined #linux-sunxi
<Turl> rds_: it really depends on what you want to do
<Turl> for home server kind of stuff, the mele is pretty good because it's a sharp looking black box :)
physis has quit [Ping timeout: 246 seconds]
<libv> rds_: just look for something with a good formfactor
<libv> something that suits your needs
xavia has quit [Ping timeout: 240 seconds]
imcsk8 has quit [Read error: Connection reset by peer]
hipboi has quit [Ping timeout: 260 seconds]
hipboi has joined #linux-sunxi
maksimlin has joined #linux-sunxi
imcsk8 has joined #linux-sunxi
protoCall7 has joined #linux-sunxi
Faisal has quit [Ping timeout: 240 seconds]
TheSeven has quit [Ping timeout: 272 seconds]
TheSeven has joined #linux-sunxi
Turl has left #linux-sunxi [#linux-sunxi]
Turl has joined #linux-sunxi
rz2k has joined #linux-sunxi
pwhalen has quit [Ping timeout: 240 seconds]
Turl has quit [Remote host closed the connection]
Turl has joined #linux-sunxi
physis has joined #linux-sunxi
wingrime has joined #linux-sunxi
physis has quit [Ping timeout: 240 seconds]
pwhalen has joined #linux-sunxi
mmarker has quit [Remote host closed the connection]
mmarker has joined #linux-sunxi
pwhalen has quit [Ping timeout: 260 seconds]
FreezingCold has quit [Quit: Out]
pwhalen has joined #linux-sunxi
quitte_ has joined #linux-sunxi
quitte has quit [Ping timeout: 246 seconds]
zombu2 has joined #linux-sunxi
FreezingCold has joined #linux-sunxi
physis has joined #linux-sunxi
amitk has joined #linux-sunxi
FreezingCold has quit [Quit: Out]
maksimlin has quit [Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140715215003]]
physis has quit [Ping timeout: 245 seconds]
wingrime1 has joined #linux-sunxi
wingrime has quit [Read error: Connection reset by peer]
wingrime1 has quit [Ping timeout: 240 seconds]
wingrime has joined #linux-sunxi
<bbrezillon> quitte_: the reason to move to a 3.16 kernel -> because I won't/can't backport my v4 work on a 3.13 kernel
<bbrezillon> quitte_: how about using buildroot ?
<bbrezillon> quitte_: it's pretty straightforward
<bbrezillon> quitte_: moreover buildroot support building the last mainline kernels and can generate UBI images
mawe242 has joined #linux-sunxi
PulkoMandy has joined #linux-sunxi
HeHoPMaJIeH has joined #linux-sunxi
HeHoPMaJIeH has joined #linux-sunxi
Andy-D has joined #linux-sunxi
<akaizen> how do i upload the A31 sdk to dl.linux-sunxi.org?
<wens> uploading mine
<wens> hmm, can anyone with sudo create a 'merrii' directory and give me permissions?
hipboi has quit [Ping timeout: 255 seconds]
<wens> or maybe just chmod 1777 the whole dl directory
<wens> also have some docs to upload
kuldeepdhaka has joined #linux-sunxi
hipboi has joined #linux-sunxi
protoCall7 has quit [Quit: protoCall7]
protoCall7 has joined #linux-sunxi
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-sunxi
hipboi has quit [Ping timeout: 255 seconds]
protoCall7 has quit [Quit: protoCall7]
ddc has joined #linux-sunxi
mawe242 has quit [Quit: Leaving]
Faisal has joined #linux-sunxi
hipboi has joined #linux-sunxi
_massi has joined #linux-sunxi
<oliv3r> does anybody else have an A33 device?
<wens> oliv3r: any chance you can ask eva if they have an updated version of a23 manual?
quitte_ has quit [Ping timeout: 255 seconds]
diego_r has joined #linux-sunxi
ganbold_ has quit [Ping timeout: 255 seconds]
<oliv3r> wens: i can ask :)
<oliv3r> i have received eva's A33 tablet!
<hramrach> wut is a33?
<hramrach> should I even be interested?
ganbold_ has joined #linux-sunxi
<oliv3r> quad core with mali
<oliv3r> (i think it's mali, i haven't checked yet)
<oliv3r> our wiki says it is mali400
physis has joined #linux-sunxi
Andy-D has quit [Ping timeout: 250 seconds]
Gerwin_J has joined #linux-sunxi
<hramrach> sounds nice
<wens> oliv3r: don't think anyone else has it
<wens> while you're at it, some a33 docs would be nice too :)
<hramrach> still adding more cores kinda does not make the device more powerful
<hramrach> 2 cores is much better than 1 but then any gains from more cores are diminishing unless you also add RAM bandwidth or some features
patp has joined #linux-sunxi
<oliv3r> wens: yeah i first thanked for the a33 sample, on her reply, I'll ask for docs, sdks' etc
<patp> a33 datasheet if you haven't seen one http://wenku.baidu.com/view/d5cc4cb94afe04a1b071ded3.html
<oliv3r> we have no a23 user manual do we?
<wens> oliv3r: we do
<wens> oliv3r: otherwise my mainline effort would be much harder
<oliv3r> :)
<wens> damn, baidu again
<oliv3r> i seriously doubt they have an updated version
physis has quit [Ping timeout: 272 seconds]
<oliv3r> wens: which one is the download button?
<patp> oliv3r: apperantly you need a account with credits to download
<oliv3r> anybody has one? :)
<oliv3r> bug me not?
<PulkoMandy> I have an account, no idea about credits
<PulkoMandy> trying...
<wens> new accounts have 4 credits
<oliv3r> don't waste much money on this though, this document is really not that interesting
<wens> shouldn't need it either
<wens> the a33 is pin compatible with a23
<oliv3r> yeah
<wens> should be compatible on the inside as well, except for the extra 2 cores
<hramrach> 下載
<hramrach> not the first character for down
<hramrach> +e
<oliv3r> it's like a10 vs a20
<oliv3r> but without emac
<oliv3r> which sucks
<wens> download is the button in the lower right part of the screen , immediately to the left of the coin icons
<Gerwin_J> i have download it
<wens> oliv3r: have to use wifi or otg on these
<wens> oliv3r: what i'd like from allwinner is some documentation on RSB, and boot0
rds_ has quit [Ping timeout: 246 seconds]
<oliv3r> wens: i know! complained about that often
<wens> :p
<oliv3r> RSB i did not know we had no info on
<oliv3r> i'm supprised that's not in the sk
<PulkoMandy> and my account has no points left. sorry :(
<oliv3r> sdk*
<wens> oliv3r: only a badly commented driver in u-boot
<oliv3r> ah
<oliv3r> well that's something I guss
<wens> which really doesn't explain some of the wierdness :(
<wens> like setting a runtime address
<oliv3r> it's compareable to their super i2c bus on the a31 is it not?
<wens> oliv3r: p2wi is not addressable, rsb is
<wens> oliv3r: it's like an improvement over p2wi
<patp> Gerwin_J: thanks
<oliv3r> if only i rememberd my passwd
<wens> the probably made the new bus to either lock in peripherals or avoid patents
<wens> or for higher speeds
<wens> we'll see with the a80
<oliv3r> mnemoc: can you move that dir pls :)
<wens> oliv3r: could you put this in the A23 dir?
<oliv3r> i rememberd my passwod for sudo back then :p
<oliv3r> so A23 I created, hence i can make stuff in it
<oliv3r> wens: missread your Q sorry
<oliv3r> wens: done
<wens> oliv3r: :)
<oliv3r> ok started small, asked for a33 user manual and sdk
<oliv3r> (she replied to my mail about receiving the tablet)
patp has quit [Ping timeout: 246 seconds]
<Gerwin_J> patp thank my girlfriend :)
<wens> oliv3r: that was quick :)
<oliv3r> aye
<oliv3r> Gerwin_J: thanks Gerwin_GF
<wens> uploading a31 4.5 sdk
<wens> /home is going to almost full
<oliv3r> mnemoc: ^
<wens> the latest one is huge, complete with android and a full toolchain
<oliv3r> i think the a23 was that too wasn't it
<wens> but the a31 one is 2gb larger o.O
Gerwin_J has quit [Quit: Gerwin_J]
<mnemoc> wens: you shouldn't upload to /home, but to /srv/http :<
<mnemoc> wens: made /srv/http/sunxi/linux-sunxi.org/dl/A31 yours
<mnemoc> wens: and moved the stuff on your home there
<mnemoc> wens: /srv/http/sunxi/linux-sunxi.org/dl/SDK/A31 is yours too. same partition so moving from /A31 to /SDK/A31 is cheap
<mnemoc> oliv3r A33 moved
<mnemoc> oliv3r: but you have `sudo` anyway....
rafaelMOD has quit [Remote host closed the connection]
<mnemoc> oliv3r: need your passwd reset?
Quarx has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
<ddc> bbrezillon: hi
notmart has joined #linux-sunxi
notmart has joined #linux-sunxi
kuldeepdhaka has quit [Ping timeout: 250 seconds]
<bbrezillon> ddc: hi
<ddc> bbrezillon: I've a good news the BBT patch, resolved all my issues so far
kuldeepdhaka has joined #linux-sunxi
<bbrezillon> ddc: great news indeed!
<bbrezillon> ddc: all the BB blocks are marked (the 6 or 7 ones we've seen before)
<bbrezillon> ddc: and never used after that ?
<bbrezillon> ddc: the BBT was buggy, and this is all my fault
<bbrezillon> ddc: but now he know that we should NEVER erase real bad blocks on a Samsung NAND
<bbrezillon> ddc: this will make the transition from libnand to my driver a lot more complicated
<bbrezillon> :(
<wens> :(
<wens> some bad juju with samsung nand?
<bbrezillon> ddc: do you know why you have version 0x5
<bbrezillon> ddc: mine display version 0x1
<ddc> bbrezillon: why do I get two BBT though. is second one is a mirror of the first one, I'm a bit confused her
<ddc> here
<bbrezillon> ddc: yes that's normal
<bbrezillon> ddc: in case the block on which the BBT is written becomes bad
<bbrezillon> ddc: you always have a mirror BBT
<ddc> I'm trying to make sense of the table version control; initially (before applying the patch) it was showing as version 0x1
<ddc> bbrezillon: whey do we need BBT property in the device tree, I thought I will be just another option in nand structure
<ddc> why
indy has quit [Read error: Connection reset by peer]
<bbrezillon> ddc: I don't know. For now the NAND_BBT_USE_FLASH flag is always set by nand controller drivers, not stored in nand_ids table
<bbrezillon> ddc: I guess this is because this choice is left to the NAND user, one would want to create an on BBT while other not
<bbrezillon> on flash
<oliv3r> mnemoc: i do say I need a pwd reset, but then i'll forget it again, even though i picked something i'm sure i'd remember :)
<oliv3r> wens: download to ~/public_html, should be same partition as dl :)
<wens> finished already :)
<ddc> bbrezillon: then that should validate the use onfi timing in the device tree
<oliv3r> (assuming you have thatsymlink)
<bbrezillon> ddc: unfortunately not, because timings are described in NAND datasheets, and thus can be deduced from the NAND id
<ddc> bbrezillon: but how about if I need to pass extra options to the nand, how that is going be done
konradoo77 has quit [Ping timeout: 240 seconds]
konradoo77 has joined #linux-sunxi
<bbrezillon> ddc: what kind of extra options ?
<bbrezillon> ddc: you should really join #mtd on oftc server
<bbrezillon> ddc: :-)
physis has joined #linux-sunxi
<bbrezillon> ddc: the question you're asking might be interest to MTD maintainers or other MTD developers
<bbrezillon> ddc: be of interest
<ddc> bbrezillon: if need to set two plane mode, interleaving mode , and so on
<ddc> bbrezillon: sound good I will do so
seppel has joined #linux-sunxi
physis has quit [Ping timeout: 250 seconds]
<ddc> bbrezillon: did you get any feedback regarding adding onfi timing field to nand_id structure
<bbrezillon> ddc: AFAIK two plane mode is not supported in linux
<bbrezillon> ddc: no feedback yet
<bbrezillon> ddc: but maybe you guys can help getting Brian's attention
<bbrezillon> help me
<oliv3r> what can I do!
paulk-aldrin has joined #linux-sunxi
<ddc> bbrezillon: I was reading this http://lists.infradead.org/pipermail/linux-mtd/2014-May/053948.html, It sounds as if Brian supports the idea of using the maximum supported timing mode, but he does not like the idea of adding it to either nand_id or dts
<ddc> bbrezillon: I don't know if there is an easy way to auto-detect the Max onfi mode without going through a wasteful cycles of read reties
<bbrezillon> ddc: actually that's exactly what he suggested => add it to the nand_ids table
rzk has joined #linux-sunxi
<bbrezillon> ddc: to avoid the fastidious work of specifying the correct (max supported) ONFI timing for each and every new board
rz2k has quit [Ping timeout: 272 seconds]
<bbrezillon> ddc: I'm not in favor of timing auto detection either
<bbrezillon> ddc: because some commands might work with a given timing mode and other won't
<ddc> bbrezillon: then could this be left to u-boot or other boot-loaders to handle
<bbrezillon> ddc: I don't like this idea
<bbrezillon> ddc: in general I think the kernel should not rely on things being done in the bootloader
<bbrezillon> ddc: there are some exception though
<bbrezillon> ddc: BTW, what's bothering you with the current approach ?
quitte has joined #linux-sunxi
<ddc> bbrezillon: I'm not really bothered but in my opinion you are more likely to get your driver accepted
<ddc> without this
<ddc> bbrezillon: I know I've spent a great time and efforts on this but I guess it should be opened for more debate and get more feedback
<bbrezillon> ddc: I totally agree
<ddc> bbrezillon: :-)
konradoo77 has quit [Ping timeout: 240 seconds]
<bbrezillon> ddc: and answering to my proposals on the ML would help getting more feedback from other people
<bbrezillon> ddc: just propose what you suggested here
<bbrezillon> ddc: share your concerns
<bbrezillon> ddc: ...
<ddc> np
<bbrezillon> ddc: I don't ask you to agree with me, just to show your interest in these patches (or at least in the features they bring) ;-)
F1skr has joined #linux-sunxi
F1skr has quit [Client Quit]
akaizen_ has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
F1skr has joined #linux-sunxi
akaizen has quit [Ping timeout: 240 seconds]
skoperst has joined #linux-sunxi
rz2k has joined #linux-sunxi
F1skr has quit [Ping timeout: 272 seconds]
rzk has quit [Ping timeout: 255 seconds]
seppel has quit [Quit: Leaving]
indy has joined #linux-sunxi
Akagi201 has quit []
Quarx|2 has joined #linux-sunxi
Quarx has quit [Ping timeout: 250 seconds]
kuldeepdhaka has quit [Ping timeout: 250 seconds]
wingrime1 has joined #linux-sunxi
wingrime has quit [Read error: Connection reset by peer]
quitte has quit [Ping timeout: 260 seconds]
mawe242 has joined #linux-sunxi
wingrime has joined #linux-sunxi
wingrime1 has quit [Read error: Connection reset by peer]
kuldeepdhaka has joined #linux-sunxi
konradoo87 has joined #linux-sunxi
physis has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 246 seconds]
physis has quit [Ping timeout: 245 seconds]
rz2k has quit []
mawe242 has quit [Ping timeout: 260 seconds]
Black_Horseman has quit [Quit: Zwi se logou mou!!!]
wingrime1 has joined #linux-sunxi
wingrime has quit [Read error: Connection reset by peer]
mawe242 has joined #linux-sunxi
wingrime1 has quit [Read error: Connection reset by peer]
wingrime has joined #linux-sunxi
wingrime has quit [Ping timeout: 250 seconds]
hipboi has quit [Ping timeout: 260 seconds]
popolon has joined #linux-sunxi
popolon has joined #linux-sunxi
Quarx has joined #linux-sunxi
Quarx|2 has quit [Ping timeout: 250 seconds]
captainigloo is now known as djnz
gzamboni has quit [Ping timeout: 260 seconds]
physis has joined #linux-sunxi
konradoo87 has quit [Ping timeout: 250 seconds]
bengal has joined #linux-sunxi
hipboi has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
physis has quit [Ping timeout: 250 seconds]
morfoh has quit [Ping timeout: 255 seconds]
petr has quit [Ping timeout: 250 seconds]
speakman has quit [Ping timeout: 240 seconds]
speakman has joined #linux-sunxi
speakman has quit [Changing host]
speakman has joined #linux-sunxi
morfoh has joined #linux-sunxi
petr has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
ricardocrudo has quit [Remote host closed the connection]
ricardocrudo has joined #linux-sunxi
Akagi201 has joined #linux-sunxi
ddc has quit [Quit: Page closed]
CaptHindsight has quit [Quit: gone]
djnz is now known as captainigloo
CaptHindsight has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 255 seconds]
pwhalen has quit [Ping timeout: 250 seconds]
<libv> oliv3r: so what about the GPL violations?
konradoo77 has joined #linux-sunxi
<oliv3r> libv: yeah probably a million again
afaerber_ has joined #linux-sunxi
<oliv3r> but those get silently ignored as always
<libv> still, that's not good
<libv> as one of those violations is making us destroy nand contents
<oliv3r> incompatibility between their latest nand code and ours
<oliv3r> i know
<oliv3r> i'll persue it again
<oliv3r> i asked for the sdk first
<oliv3r> then when i have that, i can say that there's violations with it
afaerber has quit [Ping timeout: 244 seconds]
pwhalen has joined #linux-sunxi
pwhalen has quit [Changing host]
pwhalen has joined #linux-sunxi
afaerber_ is now known as afaerber
dack has joined #linux-sunxi
longsleep has joined #linux-sunxi
<longsleep> Hi folks, whats the status of the sunxi pwm mainline effort? I got a patch for the driver and wondering where to submit it.
<oliv3r> longsleep: depends, did you read the mainling_effort wikipage?
<wens> a 3rd version, huh?
<oliv3r> my point exactly :)
<longsleep> oliv3r: sure - that way i found the patch to lkml which i based on - but not all of pwm has been merged mainline and no other patch was sent since april.
<oliv3r> well step one is to contact the developer and find out why he hasn't sent in the rest :)
<longsleep> oliv3r: Yeah i did send email to Alexandre Belloni - but i wonder if there is some repository where this stuff is developed.
<oliv3r> step 2 would be to collaborate with him to finish what he started :)
<oliv3r> longsleep: what do you mean?
<longsleep> oliv3r: Well i expected to find a git repository where i could just send a pull request to. Or some information why nothing was done since April. I know that most work on that is done by volunteers - so i am asking here what do you think is the best way to move forward.
<oliv3r> git.kernel.org is the repo most patches are written against, there's sunxi-next, where all the new patches get accumlated I belive, but submitting patches is done soley via the ML
<longsleep> oliv3r: I have some questions on the mtd driver too for that matter :)
<oliv3r> longsleep: cool! bbrezillon hangs out around here, or on the ML
<oliv3r> bbrezillon: ^
<longsleep> oliv3r: yeah - i expected to find the pwm patch in sunxi-next - but it is not.
<bbrezillon> longsleep: yep, ask them
<longsleep> bbrezillon: oh very nice thanks
<oliv3r> longsleep: well it wasn't accepted yet was it
<longsleep> oliv3r: not to mainline yes - but shouldnt it be in sunxi-next first?
xavia has joined #linux-sunxi
<longsleep> bbrezillon: I got your latest mtd driver running on a cubietruck with current mainline kernel head. Mtd driver seems to work fine, i can flash stuff and read stuff from it. But i fail to mount jffs2 .. so the question is did you try that and is it supposed to work?
<oliv3r> longsleep: what happens is, once a patch is sent to the mainline ML, it gets acked, once acked, it gets merged into sunxi-next
<oliv3r> longsleep: do you have a repo with your patches somewhere?
<longsleep> i got a nand branch to, but no changes there yet
<oliv3r> longsleep: you can probably squash the fix :)
<longsleep> oliv3r: Well yeah - it is not cleaned up to be pushed somewhere.
<oliv3r> longsleep: probably it's okay to pick up where alex left off, if he does not respond that is
<bbrezillon> longsleep: JFFS2 is not supported on MLC NANDs => see http://lxr.free-electrons.com/source/fs/jffs2/fs.c#L523
<oliv3r> longsleep: anyway, clean it up, and send the patches to the ml
kuldeepdhaka has quit [Ping timeout: 240 seconds]
<longsleep> oliv3r: Ok - so how long do you think i should wait - i do not want to take over somebodies work without asking politely.
<oliv3r> well alex kinda did that too :)
<oliv3r> i started on a PWM driver a year ago :p
<longsleep> bbrezillon: Oh i see - so then another question - what is the proposed way to put a file system on the NAND with mtd then?
<oliv3r> but yeah april august, long enough, give him a few days to repspond to your mail; if you give him credit for his stuff, it's fine
<oliv3r> i didn't see your copyright, so yours needs to be added :)
<bbrezillon> oliv3r, longsleep: I can ask alex, but he's in vacation right now
<oliv3r> longsleep: ubifs
<oliv3r> bbrezillon: awesome :)
<oliv3r> oh, same last name?
<oliv3r> oh no simmilar :)
<longsleep> ok sounds great thanks guys
<bbrezillon> longsleep: UBI/UBIFS as oliv3r sais
<bbrezillon> said
<longsleep> i have no hurries as the PWM driver works great now for me. But i would rather see it upstream.
<oliv3r> the whole PWM framework needs fixes though
astr has joined #linux-sunxi
<oliv3r> expose it via sysfs or something to userspace :)
<bbrezillon> longsleep: if I remember correctly this was due to the maintainer not taking care of it
<longsleep> bbrezillon: ok i will try that. So my target is to boot the A20 from mtd NAND - do you guys think this is achievable?
<oliv3r> till or what was his name?
<oliv3r> hopefully in a few months! :)
<bbrezillon> longsleep: I don't recall exactly, but I think alex addressed all the comment made on his series
physis has joined #linux-sunxi
<bbrezillon> longsleep: quitte did it
<longsleep> bbrezillon: Well i think it works - if i can get U-Boot to read from mtd with UBI/UBIFS
<longsleep> bbrezillon: Ok great - sounds promising thanks.
<longsleep> oliv3r: What do you mean with the PMW framework needs fixes? The whole kernels PWM ?
<longsleep> oliv3r: Or sunxi one?
<oliv3r> longsleep: yeah, i don't think you can do anything via bash for example with the pwm framework
<oliv3r> there's only api calls
<longsleep> oliv3r: It is exposed nicely in sysfs and works great.
<oliv3r> ah they merged those patches allready too
<oliv3r> nice
<longsleep> Yeah
<oliv3r> what's the maximum memory we can have for a headless system?
konradoo87 has joined #linux-sunxi
<oliv3r> I got 511964 available right now
<longsleep> oliv3r: With the patches it even works :)
<oliv3r> awesoe
<oliv3r> awesome*
HeHoPMaJIeH has quit [Quit: Konversation terminated!]
konradoo77 has quit [Ping timeout: 245 seconds]
physis has quit [Ping timeout: 260 seconds]
<longsleep> Ok thanks oliv3r and bbrezillon for your help. I will investigate mtd with UBI/UBIFS and see where that brings me.
<dack> k.. need a little help here... http://linux-sunxi.org/Wifi#Driver_refuses_to_load_.28sunxi-3.4_kernel.29
<dack> How do I find the "usbc to which your realtek usb wireless chip is attached"
<dack> I have linux running and am able to run lsusb... is that info in there?
<dack> is usbc the class number?
quitte has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
konradoo87 has quit [Ping timeout: 272 seconds]
Skaag has joined #linux-sunxi
<libv> dack: take the second
<libv> try it
<libv> it is marked as used and it is not type 2 (otg)
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
<dack> libv: lsusb says the class number is 0, but that doesn't seem to work. The wiki page suggests adding a firmware, but the module doesn't list that firmware as something it needs to load.
<dack> libv: I get 8188eu module loading, but nothing in ifconfig
Skaag has quit [Ping timeout: 250 seconds]
Skaag has joined #linux-sunxi
<Turl> so they joined because 'oh shiny!'
xavia has quit [Remote host closed the connection]
xavia has joined #linux-sunxi
<dack> :P so "ifconfig wlan0 up" brought it up... It doesn't seem like the usb_wifi_usbc_num actually does anything
xeros has quit [Quit: xeros]
<amitk> Turl: at 4 years, Linaro is anything but shiny :)
<Turl> amitk: for chinese companies it's shiny still
_massi has quit [Quit: Leaving]
bonbons has joined #linux-sunxi
rafaelMOD has joined #linux-sunxi
petr has quit [Ping timeout: 255 seconds]
xeros has joined #linux-sunxi
<wens> amitk: chinese companies are slow to hear the news, and even slower to join the game
<wens> Turl: i don't know, would it be possible to have then build the mali stuff against a fairly recent kernel
<wens> given that arm has no intention of open sourcing the stuff :(
<wens> Which Allwinner SoCs would you like to see with mainline support? With which modules supported? In which kernel version (realistically!)? Why?
<wens> hmm....
protoCall7 has joined #linux-sunxi
<longsleep> [A[A[5~[6~
<wens> yikes, just noticed my site url on cnx-soft
<longsleep> whops sorry
petr has joined #linux-sunxi
physis has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 250 seconds]
<skoperst> "Allwinner develop their own SDK (Linux,U-boot, etc..) in house, and release a vendor tree to direct customers"
<skoperst> I guess they are also talking about the Android SDK. Is it the same one cubie is publishing for download(the whole system .tar.gz'ed)?
physis has quit [Ping timeout: 260 seconds]
<wens> most vendors start that way
<longsleep> bbrezillon: So i got UBI now, but seems like it thinks that bad blocks are not supported. So it fails formatting because this NAND has bad blocks.
konradoo77 has joined #linux-sunxi
<skoperst> wens: does those vendors publish this SDK?
<longsleep> bbrezillon: http://hastebin.com/oxevacijan.sm
astr has quit [Ping timeout: 240 seconds]
<wens> skoperst: they provide SDKs to their customers
<libv> a more formal engagement with the linux sunxi community?
<libv> isn't that an all out lie?
<wens> hehe
astr has joined #linux-sunxi
<libv> who in allwinner was this interview with?
<libv> as always, i have to go make a stink again, which will resolve the main issues, but which will sideline me
<wens> Ben-El Baz, marketing manager at Allwinner, and Linaro contact for Allwinner
<wens> (damn sneaky code)
<libv> oh, i skipped that bit :)
<libv> but that's amazing
<libv> in that one job description, they explained all you need to know about their involvement with linaro
<libv> and it only confirms what i stated back in march
<libv> they ticked their open source box
<libv> and that's good enough for marketing
<skoperst> that elbaz guy is a funny looking chinese
<libv> ...
<bbrezillon> longsleep: which version of mtd-utils are you using
<bbrezillon> ?
<skoperst> that elbaz guy is a funny looking chinese
<skoperst> woops
konradoo77 has quit [Quit: leaving]
bertrik has joined #linux-sunxi
mawe242 has quit [Quit: Leaving]
imcsk8 has quit [Quit: Reconnecting]
imcsk8 has joined #linux-sunxi
physis has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
<longsleep> bbrezillon: currently 1.5.0 - too old?
physis has quit [Ping timeout: 240 seconds]
ganbold_ has quit [Ping timeout: 264 seconds]
astr has quit [Ping timeout: 260 seconds]
<longsleep> bbrezillon: so latest release seems to be 1.5.1 - i will try that
<bbrezillon> longsleep: yep, MLC NANDs are not supported in 1.5.0
diego_r has quit [Ping timeout: 240 seconds]
<longsleep> bbrezillon: ok thanks - this means that someone should also push 1.5.1 into debian asap
<longsleep> bbrezillon: ah never mind, its in jessy already
astr has joined #linux-sunxi
petr has quit [Ping timeout: 250 seconds]
paulk-aldrin has quit [Remote host closed the connection]
Quarx has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
petr has joined #linux-sunxi
skoperst has quit [Quit: Page closed]
physis has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 255 seconds]
physis has quit [Ping timeout: 246 seconds]
konradoo77 has joined #linux-sunxi
protoCall7 has quit [Quit: protoCall7]
<longsleep> bbrezillon: Works like a charm with 1.5.1 !
<longsleep> bbrezillon: UBI device number 0, total 3670 LEBs (7636418560 bytes, 7.1 GiB), available 3666 LEBs (7628095488 bytes, 7.1 GiB), LEB size 2080768 bytes (2.0 MiB)
pwhalen has quit [Ping timeout: 245 seconds]
rafaelMOD has quit [Read error: Connection reset by peer]
<bbrezillon> longsleep: great! you can thank who the same problem a few days ago ;-)
<bbrezillon> longsleep: great! you can thank ddc who had the same problem a few days ago ;-)
pwhalen has joined #linux-sunxi
notmart has quit [Quit: notmart terminated!]
netlynx has quit [Quit: Leaving]
<quitte> I'm having trouble getting a ubiblock device. at some point it appeared in /dev but now it doesn't. there supposedly is an ioctl to create and destroy ubiblk devices. does anyone know anything about that?
<quitte> the volume was created static - so it should meet the ro criterium
<quitte> tried with and without the openwrt patches that automate the creation and with volume=0:rootfs as well as volume=ubi0:rootfs
<quitte> dmesg, mtdinfo and ubinfo: http://pastebin.com/5rnEregQ
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
deasy has joined #linux-sunxi
konradoo77 has quit [Ping timeout: 272 seconds]
protoCall7 has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
pwhalen has quit [Ping timeout: 245 seconds]
<longsleep> bbrezillon: whoohooo - works: Aug 21 21:57:55 localhost kernel: [13877.932669] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
<longsleep> bbrezillon: going home now - thanks again!
protoCall7 has quit [Quit: protoCall7]
pwhalen has joined #linux-sunxi
Zboonet has joined #linux-sunxi
<bbrezillon> quitte: still based on a 3.16 kernel ?
<quitte> bbrezillon: still? it was 3.13.7 before. getting to 3.16 was _horrible_
<quitte> but now the path is better paved to move to 3.17
<quitte> i found out that i need the ubiblock util. i should have that shortly
Akagi201_ has joined #linux-sunxi
Akagi201 has quit [Ping timeout: 264 seconds]
<bbrezillon> you'll either need ubiblock or you can specify ubi.block=ubiX:vol-name in your command line
Zboonet has quit [Ping timeout: 260 seconds]
<bbrezillon> that's what you'll need if you want to boot on a squashfs rootfs
<bbrezillon> quitte: ^
<quitte> /dev/ubiblock0_0 on /mnt type squashfs (ro,relatime)
gaby_ has quit [Quit: leaving]
<quitte> thanks. I'll try that command line. at least now i know it can be mounted
gaby has joined #linux-sunxi
<bbrezillon> quitte: oh sorry, its ubi.block=X,vol-name
<quitte> bbrezillon: is ubi.block= documented anywhere? one would think that i would have founded after all that searching
<bbrezillon> in the driver at least
<quitte> sigh.
nedko has joined #linux-sunxi
nedko has joined #linux-sunxi
physis has joined #linux-sunxi
<dack> have people gotten the sunxi_nand driver working on A20 devices? I've only gotten it working on my A10 Cubieboard.
pwhalen has quit [Ping timeout: 245 seconds]
pwhalen has joined #linux-sunxi
<bbrezillon> dack: yes, several people actually (me, rz2k, ddc, quitte petrosagg)
<bbrezillon> and I forgot longsleep
physis has quit [Ping timeout: 246 seconds]
<dack> bbrezillon: I haven't been able to get it to work on 2 different devices. Both have Hynix NAND chips that are listed as supported devices in nand_id.c
<quitte> http://pastebin.com/epwfurhF it works! well except for the overlay. but it looks like tomorrow I can finally attach the sata disk :)
<bbrezillon> dack: I'll need more materials to help you (boot logs, a more specific description of your problem, any other information that can help)
<quitte> is sunxi-nand that libnand thing, maybe?
<quitte> or yuq?
<libv> dack: did you manage to get to meminfo and script.bin?
<bbrezillon> dack: okay, that's not mine :-)
<libv> dack: or did you get hold of a livesuit image?
<bbrezillon> quitte: great!
<dack> libv: I have script.bin but not the meminfo yet... I have linux running, but it's hobbled because the memory information is wrong..
<libv> dack: boot android
<dack> bbrezillon: okay, what module are you using to access the nand?
<libv> dack: install an ssh server from the appstore
<libv> run meminfo over ssh
<Turl> libv: why complicate things that much?
<dack> libv: I have no idea what meminfo is... I tried running that as a command from a terminal emulator and I couldn't find it
<Turl> you can get a terminal app and do it there
<libv> Turl: true
<dack> libv: I used the terminal emulator to mount the nand and get the script.bin... I can't find the "meminfo" command, though.
<libv> Turl: but i prefer typing it over ssh, and using ssh for other things as well
<bbrezillon> dack: unfortunately, none you could use with a 3.4 kernel :-(
<libv> dack: did you read our howto on retrieving device information?
<dack> bbrezillon: ah.. you're using a newer one.
<bbrezillon> dack: yep
<dack> libv: yes. I haven't been able to find a USB cable to access things via FEL and I have no idea how to get it otherwise. I don't have a copy of the livesuit image either.
<libv> dack: run it from android _directly_
<libv> dack: what's so impossible about building a tool on your pc, transferring it to android and then running it from android?
<dack> libv: Are you talking about /proc/meminfo ? I ran "meminfo" as a command and it wasn't found
<libv> dack: again.
<libv> you did not read our retrieving device info howto.
<libv> under this grossly misnamed section called "Using the original OS" and then under "Working with android"
<libv> the absolutel last place anyone should go and look.
<dack> libv: yep.. I completely didn't see that. I see it now.
<Turl> libv: that's not very verbose
<libv> Turl: ?
<libv> Turl: feel free to fix the wiki.
ninolein has quit [Ping timeout: 245 seconds]
ninolein has joined #linux-sunxi
<Turl> libv: well, maybe verbose was not the right word
<Turl> it's rather unencouraging I suppose
<Turl> we should lower the barrier as much as we can to get people to do it
<quitte> imho verbose is not the worst word to describe what's lacking in the wiki
konradoo77 has quit [Ping timeout: 245 seconds]
<Turl> with the old meminfo we had a prebuilt static bin
<Turl> you could just wget, chmod, run anywhere
Black_Horseman has joined #linux-sunxi
Black_Horseman has quit [Changing host]
Black_Horseman has joined #linux-sunxi
<dack> yeah, it'd make sense to just have bin copy available online
<libv> Turl: let's first get the latest patches in
<libv> and then we could stick the binary somewhere on linux-sunxi.org
<dack> I've got it compiled now, though... Unfortunately I have to leave for the day. I'm glad I finally found out how to get the info without the USB cable, though!
<Turl> libv: there's already some crosscompiled bins on bin/ on sunxi-tools
<Turl> but dl.l-s.o would be just fine as well
<quitte> dack: while you're moving you might want to pick up a usb cable on the way
konradoo77 has joined #linux-sunxi
<libv> hrm, really?
<dack> quitte: ^_^ I have tons, just not one that does regular sized male to regular sized male... I have one in a drawer at home.. I just have to find it.
<libv> hrm, fel-pio
PulkoMandy has quit [Quit: Vision[0.9.7-H-20140108]: i've been blurred!]
<quitte> i have neveer seen one of those. odd.
<libv> dack: these ports do not seem like host ports
<libv> they look like device ports
<dack> So, no OTG port?
<libv> i doubt that there is the extra pin for id-ing in there, which allows the device to switch to host mode
<libv> dack: i would expect so
<quitte> I'd love to hear an otg physical and electrical connection for dummies
<libv> dack: but i said yesterday that, since you are in contact with the manufacturer, you should candidly ask them how you can flash an android to this device
<libv> quitte: www.wikipedia.org
<quitte> i never understood how otg is supposed to know wether it is host or client
<libv> dack: and ask them for a livesuit image
<libv> quitte: www.wikipedia.org
<dack> libv: yeah, I contacted a sales guy.. he clammed up when I asked for software. I think he wants me to purchase 100 units to get the software. :P
<quitte> libv: is that similar to encarta?
<libv> quitte: how about you type like... you know... usb... in the search entrybox there.
<Turl> quitte: it's the 2.0 encarta!
<Turl> but it doesn't have the 3D trips to places
<libv> dack: hrm, too bad
rafaelMOD has joined #linux-sunxi
<dack> libv: he doesn't seem to get that I'd have no interest in buying any more if I can't get it to work for my purposes
<rafaelMOD> Does anyone knows where I can find a documentation for generating a valid image for live suit?
<libv> rafaelMOD: when you joined, Chanserv msged you
<Turl> but it's only for a10/a13
dack has quit [Remote host closed the connection]
<libv> Turl: tbh, i am not sure we should provide a binary here
<rafaelMOD> libv: I know, I saw that but couldn't make it.
<libv> Turl: forcing people to compile this, means forcing them to get a toolchain
<libv> the only people who need this are those who are bringing up a device, and who should at one point work through the manual build howto
<libv> the question is... do we want people to scare this early on
<libv> and do we keep the really difficult stuff til the end?
<Turl> libv: people will keep on going if they see benefit and achieve things
<quitte> why would you try to manage that?
<Turl> if you need to waste an afternoon setting up a toolchain and build essentials to build some tools, that'd probably be quite discouraging to many
<Turl> if they get 'half' the task done with script.bin and meminfo, they will probably be happier to do it then
<libv> ok
<libv> i will provide a stripped binary in bin/
<quitte> i avoided building sunxi-tools because of the binary blobs.
<libv> is there anything stopping the latest round of patches from going on btw?
<libv> also, wens, have you played with the dram controller on a23?
<Turl> libv: I can have a second look in a bit if you want
<libv> Turl: yeah
pwhalen has quit [Ping timeout: 272 seconds]
pwhalen has joined #linux-sunxi
ricardocrudo has quit [Remote host closed the connection]
physis has joined #linux-sunxi
bonbons has quit [Quit: Leaving]
physis has quit [Ping timeout: 246 seconds]
gzamboni has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
bengal has quit [Quit: Leaving]
konradoo77 has quit [Ping timeout: 260 seconds]
nedko has quit [Quit: kernel panic]
ricardocrudo has quit [Remote host closed the connection]
<gzamboni> wens mnemoc oliv3r i had already those A31 files in http://dl.linux-sunxi.org/users/gzamboni/ downloaded from wens some time ago, its duplicated now, i will delete them
ricardocrudo has joined #linux-sunxi
<gzamboni> i didnt move them to the A31 dir as i didnt have perms for that
xavia has quit [Remote host closed the connection]
physis has joined #linux-sunxi
petr has quit [Ping timeout: 264 seconds]
bertrik has quit [Remote host closed the connection]
patap has joined #linux-sunxi
<patap> A80 datasheet http://pan.baidu.com/s/1sjrYP6P
Gerwin_J has joined #linux-sunxi
afaerber has quit [Quit: Verlassend]
ricardocrudo has quit [Ping timeout: 245 seconds]
Gerwin_J has quit [Quit: Gerwin_J]
afaerber has joined #linux-sunxi
<libv> patap: thanks
patap has quit [Ping timeout: 246 seconds]
petr has joined #linux-sunxi
<DagoRed> Has anyone tried to implement device tree in the kernel yet?
physis has quit [Ping timeout: 246 seconds]
<DagoRed> I have a pile of boards I'm sitting on and would love to get a more recent kernel running with a fair amount of support.
<quitte> DagoRed: what do you mean? mainline kernels use device tree blobs
<DagoRed> Well is there a chance for getting the sunxi kernel to get mainlined at all?
* DagoRed checking it out
<libv> DagoRed: which boards?
<DagoRed> 2 Iteaduino's (A10 and A20), and about 7 olimex boards with the A10, A10s, A13, and A20.
<libv> DagoRed: can you spend a bit of time checking the pages on our wiki and see what still needs to be done for them?
<DagoRed> I have the uboots set up and committed with the Arch Linux ARM group and just sittin on images for a later kernel right now.
<DagoRed> libv: no problem, I'm here to get my hands dirty.
<libv> DagoRed: is that the a13 micro?
<DagoRed> I just forked and cloned the git repository on my sabre lite (personal build box) so now to rummage through.
<DagoRed> Yes I have the a13 micro.
rafaelMOD has quit [Remote host closed the connection]
<libv> cool, that's the worst documented device from olimex atm (apart from the upcoming ones)
<DagoRed> oh fun....
<DagoRed> well... guide me and I'll do what I can.
<DagoRed> So is there a mailing list or anything I can get signed up on? Forums?
* WarheadsSE facepalm
<libv> DagoRed: oh, we need a good picture of the uart for the iteaduino page as well
<libv> DagoRed: it says "community" on the front page