<furan>
how far are things from mali working on jellybean?
<Turl>
furan: mali works
<furan>
what doesn't?
<Turl>
hipboi: you typoed android on the rar name :) minor nitpick :P
<Turl>
on the folder inside the rar rather
<lundman>
whats this
<Turl>
lundman: latest mali props :)
<Turl>
for android
<furan>
so does this help us run jellybean?
<furan>
I am JB obsessed
<lundman>
havent even turned on a10 in 3 weeks, anything new to try
<Turl>
furan: JB ran already with the old stuff
<Turl>
lundman: didn't you use it as a NAS?
<furan>
oh jeez, then I need to build a rom for it
<furan>
turl sorry to bug you but did you start a repo?
<furan>
I am about to solder a nand socket to an mk802 and upgrade the nand to different types to see if I have the way the nand table works worked out
<Turl>
furan: yeah, just didn't make a local manifest for it yet though
<Turl>
but it's all on the github org
ZaEarl has joined #arm-netbook
<furan>
what do you mean by local manifest?
<furan>
(I'm still working out android stuff)
<furan>
nm googled
<Boulet>
furan, interesting
<Boulet>
do you have an external nand programmer also?
<furan>
no, but i've gotten livesuit to the point of being able to flash it (have to modify the nand table in the files in the image that livesuit loads into memory to do the flash)
<furan>
last time I tried this I just didn't have the values worked out, since they didn't match the datasheets
<furan>
also I'm worried that since brom reads the first page it might have hardcoded nand support, in which case with new nand you might have to always boot from a u-boot sdcard that jumps to nand
<Boulet>
what do you mean by "hard-coded" support ?
<furan>
well, brom executes code that reads the first page of nand and then executes code on the nand
<Boulet>
yeah
<furan>
so that code in brom may have fixed support for nand, since nand can have different read commands (it generally doesn't, but it can)
<furan>
e.g. the brom code may have its own table that it references to understand how to read the first page depending on nand id
<Boulet>
there are some universal read commands though
<Boulet>
that's possible yeah
<furan>
are there? for some reason the nand driver keeps a table of 'architectures' with nand read/write/etc commands for each arch
<furan>
I'm learning about talking to nand at the same time
<Boulet>
i think to remember there are basic read commands that every nand support
<furan>
that would be good
<Boulet>
but then, there is ECC correction, and that is a different story
<Boulet>
and also flashes can have different planes, can be SLC or MLC, blah blah blah
<furan>
yeah.
<Boulet>
but i think reading the first block should not be too difficult in an universal way
<furan>
how big is the read? I suppose if it is smaller than the smallest page size it might work
<Boulet>
ECC depends on the chip controller, so A10 will expect to find its own ECC scheme on the nand flash
<Boulet>
i don't know
<furan>
a10 nand driver keeps an 'ecc' field for each supported nand chip, I'm still confused about that one. might be num bits
<Boulet>
i programmed a flash controller 5 years ago on a DSP chip, it was SLC NAND, 64 pages of 2048+64 bytes per page
<furan>
cool
<furan>
what is the +64, to account for bad blocks?
<furan>
I noticed the page size+number in a lot of dataasheets
<furan>
usually that number grew with the page size
<Boulet>
those are used to store ECC values and other info that might be useful for your filesystem
<furan>
I see
<Boulet>
like logical to physical block translation
<furan>
nods
<Boulet>
some nand datasheet call this "spare", but on linux it's called oob data i think
<furan>
ok
<Boulet>
so when you read/write a page thru the NAND flash controller of A10, it should be able to calculate/apply ECC automatically
<Boulet>
which is great, because doing ECC in software is quite costly
<Turl>
hipboi: the kernel land changed quite a bit :P
<furan>
nods
<hipboi>
not that much
<furan>
is there an mk802 android depot, or some way for me to just pull the device config for mk802?
<Boulet>
you imagine, you have 2048 bytes, with a few extra bytes, you are able to locate and correct up to 8 (let's say) bits in those 2kb :) pretty cool
<Turl>
hipboi: the diff is quite big, they refactored quite a bit of things
<hipboi>
oh, yes
<furan>
nods
<hipboi>
btw, the rar is provided by my workmate
<Turl>
hipboi: is he the one that sells devices with you?
<hipboi>
no
<Turl>
hipboi: mali did proper kernel makefiles/kbuild/kconfig this time apparently :)