mister Sno-bot , but its actually more like shaved ice falling this night - there has totally been no winter - potential for vermin and other insect disaster not to mention dried up brooks and rivers ...
touch wood or something - half-snot couldnt resist a small tryout
having compiled about 4 c programs in my life, one a patch to run fallout under wine on linux over 15 years ago and definitely not for a machine thats not the machine compiling on (compiled unreal engine once, took hours , got nothing b/c the asset store didnt even work) its not as straightforward as Vonger explains - but i think he's talking to l33ter folk than this
After some - (the good thing is we found out everything works and nothign broke in transit) - there's sound , there was network too with LUCI for easy
We get the screen working (you can apparently not just type make to do magic) and fbusb.ko in place but by then no more network, it gets an ip tho but luci doesnt connect anymore on the 19.xx version of openwrt
the touchdemo works too but it displays everything in reverse
and ... the boot sequence seems to go through the audio output too
tho writing dd if = /dev/zero or /urandom to /dev/fb0 goes pretty fast so that should do fps (thats just bash not assembled code so how fast the calculations would be , thing is the speed at which it fills the screen thats important here
that way you can write to a buffer file and move that to the screen like a virtual blitter or something
so thats GUD
and thats gud and gud, but the network wont accept the settings that worked before the screen worked
and actually as the core of the system the network is more important than the screen - - - so thats gonna be digging
apparently it doesnt do ext4 either so lucky an sd-card with fat was found in the box of many pandoras and all fine
xept that theres no link and the ethernet cable got crammed in the plastic casing and we're a bit skurrd to tug it out with force
its not like a 1cm³ machine is built for heavy pressure (unlikely) and even if its "only $17" some respect for the tools is very likely the better way to go at (everything)
the screen is REALLY small (the smallest they had : 4 inch) but the resolution is the same as the biggest : 400x800 so programwise that stays exactly the same - the perk is here : power consumption : this 4 inch thing consumes really dud to the power of naughtpointone something AND it has touch capability so it can be used for anything from control to entering pincodes (not sure how speedy it would be on swipiing or sig-patterns) but thats gonna take some disecting of the demo provided
so its unlikely we'll be bored for the rest of the year
slow as we are its gonna take a while
so the MIPS code ?
well if we can figure out what makes MAKE do magic then probably it should do that for mips code too
that said
we dont have a map of the piano
so we really dont know
if you lda 0 into d020 on a c64 the outer screen goes black
here ...
its probably a bit more complex (but the screen isnt, that seems to just take a full streem of rgb values - wether its possible to offset and directly access any pixel remains to be found)
at any rate
for that price
this is gud
YAY Vonger !
we might have some questions tho we always feel like a loss if we have to ask so before that we might have bricked it six times
its like SO much better if you dont have to ask and you get to the AHA ! moment (erlebnis, jawohl)
SO much better
tho we should have been in bed instead of hours poking at that thing
its hard to resist
but the takeaway for tonight is : all the hardware works
the better option would be to get the network working on this install
otherwise its upload a previous version image and sysupgrade backwards but then the screen probably wont wanna
but we got the compiled fbusb driver now
for the same system so in essence
if we can link it
that should work
we can figure out compiliing for mips later (c or asm ... its the 'for mips' part thats eluding)
right ?
o yea well so you see
no cars or the weather here, sorry for that
not very sexy huh ?
too bad
now for some serious crashing
ah,na yea, so
yes you can manipulate your "bufferfile" (if used with dd like the example) any way you like with an offset i suppose but the thing is can you poke directly via an offset at the screen itself like "start copying at pixel x" so you dont have to send the whole 800x400 pixels over every frame (and leave the others untouched)
like those c64 onescreen platformers for instance
or do you have to send over the whole frame every single time for pixel 0 to pixel 800times 400
but so whats actually more important is connecting to a machine on the network and telling it what to do
(for the purpose of the system)
BUT YOU KNOW ...
cant just ignore a true colour screen now that its there
we kinda would like to mail iMou and ask for the control codes to their cam but we think we already know the answer to that and digging it up with tcpdump from (likely encrypted) packages on the network ?
that's gonna require a totally snotless head in the first place
not wanting for something to do
not wanting to do something some say we should either
DONT, ITS NOT GONNA WORK OUT , WE DONT WANNA HUMANS ITS TOO LATE
(and theres no harem so dont bother)
stay weird
stay creative