<kristianpaul> ?
<wpwrak> the page doesn't show a title. and the <TITLE> tag just says "Qi". terribly short if you want to refer to it :)
<kristianpaul> what tittle you want it to show?
<kristianpaul> Qi's mission is to promote and encourage the development of copyleft hardware.
<wpwrak> at least "Qi-Hardware" ;)
<kristianpaul> well,may beall this time we were Qi :-)
<wpwrak> ;-)
<kristianpaul> so Qi..
<kristianpaul> not more
<kristianpaul> donw
<kristianpaul> happy now wpwrak ?
<wpwrak> whee ! thanks a lot ! :)
<Phagus> Wow, this is pretty amazing...
<kristianpaul> what what??? !!
<kristianpaul> hi Phagus :-)
<Phagus> Hi. Hardware hacking!
<wolfspraul> ah yes, welcome to the club
<wolfspraul> :-)
<kristianpaul> ah, sure,  also try ask later about hardware manufacturing ;-D
<Phagus> I've always wondered about it. I have a ton of old computers, circuit boards, parts, etc, always wondered if I could do something impressive with them
<kristianpaul> aw_: you're in writing to the wiki, congrats !!
<Phagus> Is there a good newbie beginner's guide to this?
<Phagus> I'm a newbie engineering student
<kristianpaul> nanonote it self is a guide
<aw_> kristianpaul, hi, what's up?
<kristianpaul> aw_: http://en.qi-hardware.com/wiki/Special:ActiveUsers  177 edits in the last 30 days
<kristianpaul> sorry to distract you :-)
<wolfspraul> Phagus: what's your major?
<aw_> kristianpaul, oh~yeah. :-)
<kristianpaul> hopes is radio eng
<Phagus> wolspraul: It's just called "Computer Systems", it's a bit of engineering and technician stuff. Hardware, software, networking, programming, web design, administration. But I'm finding myself getting really interested in the engineering parts of stuff.
<wpwrak> kristianpaul: superluminar particle physics (applied) would be more interesting, though
<Phagus> kristianpaul: What's nanonote?
<kristianpaul> a pocket small computer, that was freeded and copylefted as much
<kristianpaul> both software and hardware side
<Phagus> Wow nice
<Phagus> Ethernet over USB? interesting
<akiwiguy> pops his head in
<wolfspraul> kristianpaul: oh cool, you tried toped :-)
<wolfspraul> wpwrak: hardware question for the expert. was is the best temperature to drink a beer at?
<Ayla> 3°C for the beer, 24°C outside
<kristianpaul> 24 is not a bit cold?
<larsc> haha!
<wpwrak> wolfspraul: puuh.  i never actually waited long enough to measure ;-)
<wpwrak> wolfspraul: a bit above freezing sounds about right, though. particularly if it's hot outside. of course, 24 C isn't hot :)
<wolfspraul> that cold? ok I will try :-)
<qi-bot> [commit] David Kühling: gforth: use a primary download location that actually works (downloads.qi-hw.com) (master) http://qi-hw.com/p/openwrt-packages/7e83fd1
<Ayla> mth: I think it would be much simpler to render the last frame of gmenu2x twice
<mth> Ayla: an all-SDL solution would be cleaner though
<mth> didn't the patch you made earlier solve it?
<Ayla> no, it does not work
<mth> you removed the "* bytes_per_pixel" part?
<Ayla> yes
<Ayla> here's what I have right now: http://pastebin.com/vqiTNVJh
<mth> maybe SDL itself already undoes the vertical scroll earlier?
<Ayla> it's restored after (SDL_fbvideo.c:1982)
<mth> could the fact that screen->pixels is not set to NULL cause problems?
<mth> it doesn't look like it's inspected afterwards
<mth> but then why would they have a test around that assignment?
<mth> in what way doesn't the patch work?
<Ayla> one time out of two, the launch of a binary from gmenu2x fails :)
<mth> launch fails as in "gmenu2x keeps running" or "gmenu2x crashes" or "launched binary has no video" or ...?
<Ayla> gmenu2x crashes and respawns
<mth> that sounds like the memcpy writes to the wrong location / out of bounds
<Ayla> yes, I believe
<mth> smem_start is a physical address, user space cannot write there
<Ayla> ah, that makes sense then
<mth> you should use the pointer returned by mmap
<mth> from wherever SDL stored it
<Ayla> mth: new attempt: http://pastebin.com/QtrjdSaE
<mth> use "this->screen->pixels" in the memcpy ("pixels" part is missing)
<mth> "mapped_mem + mapped_offset" is the address of line 0 in the frame buffer?
<Ayla> yes
<mth> then it looks ok to me if you add "->pixels"
<Ayla> whohooo
<Ayla> doesn't work
<Ayla> the binaries do launch, but I get garbage on the screen instead of the launcher menu
<mth> garbage until the launched app takes over, I assume?
<mth> always garbage or half of the times?
<mth> ah, "pixels" points to the *in*visible page
<Ayla> half of the times
<mth> anyway, the "pixels" pointer is not what you need; you need the pointer to the visible page
<Ayla> I just have to reverse the memcpy
<Ayla> and removing mapped_offset fixes the garbage
<mth> the destination should always be line 0
<Ayla> the comparison line 15 is incorrect
<Ayla> it should be '=='
<Ayla> as the buffers has been flipped
<mth> check FB_FlipHWSurface
<mth> surface->pixels = flip_address[flip_page];
<mth> looks like flip_page and flip_address is all you need
<Ayla> meh
<Ayla> looks like the solution is simpler then :)
<mth> note that flip_page is only initialized if SDL_DOUBLEBUF is set, so check that before using the value
<Ayla> mth: this seems to work fine: http://pastebin.com/vS9BvmNE
<mth> I'd prefer "flip_page == 0" over "!flip_page", since it's an index and not a boolean
<mth> but that's a minor thing
<Ayla> it is a boolean
<Ayla> see SDL_fbvideo.c:1439
<Ayla> they explicitely write "flip_page = !flip_page"
<mth> hmm, SDL itself is not consistent
<Ayla> but I can put flip_page == 0, I don't mind :)
<mth> yes, there they use it as a bool, but in "cache_vinfo.yoffset = flip_page*surface->h" it is an index
<mth> either way is both consistent and inconsistent with the existing code ;)
<mth> so commit whetever version you prefer
<mth> personally, I would have used "flip_page ^= 1;" instead of "flip_page = !flip_page;", but let's not change any more code than we have to
<Ayla> it works fine, I commit it
<Ayla> but I'm not sure about SDL_memcpy
<Ayla> lines 1923->1929 are here to prevent a bug in SDL_memcpy, apparently
<Ayla> (of SDL_fbvideo.c)
<Ayla> btw, why don't you commit the config files for uClibc and busybox?
<mth> I was just working on that commit :)
<mth> the rebuild finished, now I've got to check it
<mth> about SDL_memcpy: it is SDL_memset that is worked around there
<mth> you could use ordinary memcpy if you like
<mth> I don't know what the purpose of SDL_memcpy is
<mth> is it for extra performance (only likely if the system memcpy is poor) or is it for systems that have to memcpy?
<mth> to->no
<Ayla> both, I believe
<mth> in any case, both memcpy and memset should operate on arbitrarily aligned pointers
<mth> they can use special optimized code if pointers are aligned, but should have a (slow) fallback if not aligned
<mth> so I'd suggest to ignore the treat of possible bugs; if there are bugs, they should be fixed in memcpy/memset, not worked around
<Ayla> mth: pushed
<mth> I see the SDL patch; is the gmenu2x side also pushed?
<Ayla> one second
<Ayla> the gmenu2x modification was very fast to make
<Ayla> what takes me the most time is the commit message...
<Ayla> mth: the setenv is made only if UNLOCK_VT is defined, is that a problem for you?
<Ayla> I think I'll use another constant
<mth> I do prefer to have separate constants, even if they are in practice set on the same systems
<Ayla> do we even need a constant to enable/disable the setenv?
<mth> I think it can be enabled always
<mth> on some platforms it may have no effect, but that doesn't matter
<Ayla> here's the diff for gmenu2x: http://pastebin.com/8m574DW6
<Ayla> I added a link to your repo, if somebody need to find the patch
<mth> maybe deep-link?
<mth> someone not familiar with buildroot could have trouble finding it
<Ayla> I don't know its URL :)
<mth> "a SDL patch" -> "an SDL patch"
<mth> phonetically, "SDL" starts with a vowel
<Ayla> but S stands for "simple" :)
<mth> that's the deep link
<mth> it's a bit long though
<Ayla> thank you
<mth> the file/directory links on-screen actually use deep link URLs, but if you click some javascript trickery refreshes only the source view on the same page
<mth> if you open the link in a new tab you get the actual URL
<Ayla> maybe we can create a tinyurl then?
<Ayla> I never used that, I just hope it does not timeout after some days
<mth> I don't like shorteners
<mth> just spread it over two lines
<qi-bot> [commit] Ayla: GMenu2X now won't clear the framebuffer on exit. (master) http://qi-hw.com/p/gmenu2x/f6c456f
<mth> Ayla: it's not working here
<mth> could that be because I reversed one of the commits that suppresses the console?
<mth> I do see the loading dialog, but only a very short time, after that I see the console
<Ayla> that's normal
<Ayla> you reverted one of my commits...
<Ayla> when a console is displayed, type: echo 0 > /sys/devices/virtual/vtconsole/vtcon1/bind
<mth> yep, it works using that