<Fallenou>
that's why I think /ramdisk is just IMFS
<Fallenou>
since it's a directory in the rootfs
<Fallenou>
gotta go to sleep
<Fallenou>
see ya
<kristianpaul>
bye
<kristianpaul>
he, first crash... lets see what i did wrong
<kristianpaul>
reading seems okay, but for reasong writing crash the system :/
<kristianpaul>
but simulation went okay..
<kristianpaul>
well, writing to the gps "buffer" is not a wanted feature, but i still want to know what's wrong..
<rejon>
what filesystems can the mm1 read from that microsd?
<rejon>
kristianpaul Fallenou lekernel
<kristianpaul>
i had tested fat16 so far rejon
<rejon>
not vfat
<kristianpaul>
hmm
<rejon>
yes
<rejon>
vfat is default fat16
<rejon>
that workred kristianpaul ?
<kristianpaul>
i'm noob on filesystems, i just got a microsd wolfspraul sent me, pluged to my copmuter and gparted told the fat16
<kristianpaul>
rejon: yeah, but not with my 1Gb kingstone and 512Mb toshiba microsd.. :-/
<kristianpaul>
rejon: are you having problems reading a memory card?
<kristianpaul>
SandDisk is the brand of the card
<kristianpaul>
the other one seems unbraded (not counting a shiny HBTX sticker on the bottom)
<rejon>
ok
<kristianpaul>
I want to mean, memory card reader in milkymist may be not work with all cards.
<kristianpaul>
Also not write support avaliable
<wolfspraul>
rejon_: memory card support is buggy, you need a little luck that the card you have works
<wolfspraul>
or maybe it's not buggy, but our drivers are not robust/flexible enough to handle the infinite variations on the standard you find in real life cards
<wolfspraul>
this actually reminds me again of the value of including a 1gb or 2gb card together with the product...
<wolfspraul>
another thing to look into, maybe
<wolfspraul>
rejon_: I've sold my last rc2 unit!!!
<wolfspraul>
seriously that's big news I think, for the project
<wolfspraul>
the ability to move ourselves forward with cash income is the #1 thing we need for long-term success
<wolfspraul>
so as of today, I'm officially out of stock, which is bad (but good motivation)
<rejon_>
yes, great
<rejon_>
an african guy
<rejon_>
wanted to buy one on the spot
<rejon_>
yesterday
<rejon_>
and have another offer for something in vietnam
<wolfspraul>
ouch
<wolfspraul>
man now I have no stock
<kristianpaul>
lekernel: btw, you should  take a look at http://nuttx.sourceforge.net/, seems have lots of missing drivers in rtems like SD/MMC support and USB host stack (with included debug)
<wolfspraul>
well u know me, now I can hit myself to work faster :-)
<kristianpaul>
will take a look too
<wolfspraul>
rejon_: there may still be a few units at tuxbrain and hackable devices/kd85
<wolfspraul>
were you able to reflash your m1 with the latest software?
<kristianpaul>
he, you are good with mediawiki "tags"
<kristianpaul>
cool, nuttx allow execute separte linked programs too
<wolfspraul>
if you reflash the latest 05/09 snapshot, it should boot right into rendering mode (although boot time will be ca. 35 seconds)
<wolfspraul>
and after that you can click through patches with the left button (the one towards the IR)
<kristianpaul>
boots in 3 seconds with no gui :D
<wolfspraul>
the reason the boot time increased so much is because we currently compile all patches, there is no precompilation or caching yet
<wolfspraul>
we'll get it back down
<kristianpaul>
well 5 seconds..
<wolfspraul>
but you can click through all patches, which is nice
<kristianpaul>
oh
<wolfspraul>
kristianpaul: I'm talking about the 05/09 image, which will get you into a mode where you can click through all patches, and they all need to be compiled first (currently)
<kristianpaul>
i dint knew it that (compile all patches)
<kristianpaul>
yes sure wolfspraul
<kristianpaul>
ha, you mising ack wire!!
<kristianpaul>
okay, now other hours to test this ix
<kristianpaul>
s/ix/fix
<kristianpaul>
hour*
<kristianpaul>
hum i think build-rescue is not been delete with make clean at flash/ dir and also byt clen_all
<kristianpaul>
orr..
<kristianpaul>
is the third time i haved to delete the content of that folder my self..
<wolfspraul>
kristianpaul: don't understand. what do you want?
<wolfspraul>
you are proposing a fix to a build target?
<kristianpaul>
may be, yes
<kristianpaul>
i need to confirm first..
<wolfspraul>
ah ok, I misread what you said
<kristianpaul>
no no, i wast to clear on word, i admin
<wolfspraul>
I thought you said "this is the third time I propose to ..."
<wolfspraul>
but you said "this is the third time I had to delete..."
<wolfspraul>
got it now :-)
<kristianpaul>
i just noticed this, because a non-ending error was solved by deleting the content of build-rescue
<kristianpaul>
;-)
<wolfspraul>
sure - inadequate error handling in build scripts can lead to many unpleasant and hard to track down surprises
<kristianpaul>
wolfspraul: i'll install Xilinx ISE on fidelio, is okay with you?
<kristianpaul>
wee 11.2M/s
<kristianpaul>
:-=
<kristianpaul>
cloud computing is not bad at all ;-)
<wolfspraul>
sure of course if that helps you
<wolfspraul>
not sure the specs of the server are enough for it, but if you need anything, let me know
<wolfspraul>
download speed should be good, yes :-)
<kristianpaul>
seems as fast as my pc, well it is Athlon mine is sempron
<kristianpaul>
and NO i will not even try to run two P&R instances.. on my pc, i dont want end burning out something
<kristianpaul>
argh, what is wrong... with 0xf0000000 ..
<kristianpaul>
hum, the system freeze even from the upstream bitstream version, so it should be newby mistake related with pointers..
<lekernel>
what are you trying to do?
<kristianpaul>
i cloned the minimac core, in order the re-used the dual ported ram memory, plus add the shift core that sync data coming from the L1 SiGE front end
<kristianpaul>
so I decied wrote a small commad to write and read that memory
<kristianpaul>
reading is okay. but when i write from this address (0xf0000000) the system just crash
<kristianpaul>
i tried same procudere from soft usb and ethernet cores, and no crash
<kristianpaul>
i tried with my hacked milkymist core and the upstream one