<qi-bot>
[commit] Werner Almesberger: qpkg: turn pkg->installed into pkg->flags, allowing for future expansion http://qi-hw.com/p/wernermisc/a63823e
<qi-bot>
[commit] Werner Almesberger: qpkg: towards "struct id" without jrb reference - change iteration and lookup http://qi-hw.com/p/wernermisc/7058115
<kyak>
viric: great! could you document it for non-nix users? i.e. kernel options, cmdline, pecularities of ubi creation and then qemu parameters?
<wolfspraul>
kyak: which backend are we using for NetSurf in OpenWrt?
<wolfspraul>
framebuffer? sdl?
<kyak>
sdl backend
<wolfspraul>
what are the pros and cons between the two? why did we choose sdl?
<wolfspraul>
(just curious)
<kyak>
its linuxfb is broken
<kyak>
netsurf's linuxfb
<kyak>
the guy from #netsurf said
<kyak>
< kyllikki> right now its been reduced to a stub untill i get round to  it
<kyak>
and reason is that
<kyak>
< kyllikki> the API usage changed with the invention of kms and i  never have figured out why netsurfs usage blows up
<kyak>
however, netsurf has gtk2 interface
<kyak>
but i think it will be slower than sdl (need to check of course)
<wolfspraul>
ok got it
<wolfspraul>
sdl seems like a reasonable choice then
<kyak>
B_Lizzard tried gtk interface in OE (with X, however). Very slow
<wolfspraul>
sure let's focus on sdl, and maybe linuxfb one day if they fix it
<kyak>
they fixed already some things "for us"
<kyak>
i don't know if they are willing to go on
<kyak>
currently sdl interface has limited support for keyboard
<kyak>
in fact, only arrow keys work :)
<kyak>
but it becomes more or less usable with keymouse
<wolfspraul>
on the Ben, I think of NetSurf for 2 use cases now: develop 'local' apps in html+css, maybe later combined with some 'server side' (=local) scripting, or JavaScript if NS adds it
<wolfspraul>
and (along the same lines) offline document viewer, for example for offline wiki content
<viric>
kyak: I'll try to document that, and send that to qi-hardware
<viric>
But what is important for the reader device is having software + data that it can use to show things quickly and well, with little filesystem usage
<viric>
The way to generate the ZIM files is irrelevant for the reader
<kristianpaul>
sure
<kristianpaul>
i'm not talkign from the reader side ;-)
<viric>
ah :)
<viric>
zim looks hard to beat, on the reader side
<viric>
The devicetable is there because I don't want to become root to prepare the image
<kyak>
i don't really understand how the files will get inside the image?
<viric>
what files?
<viric>
I have all the files in the subdirectory 'root'
<viric>
-r root points to it
<kyak>
ah good
<viric>
How would I reflash my nanonote with that ubifs?
<viric>
booting in that special mode, right?
<kyak>
yeo
<kyak>
yes
<viric>
M-power ?
<kyak>
u+power
<kyak>
and then using usbboot
<viric>
ah
<kyak>
m-power is to boot from sd card
<viric>
I'll try if my ubifs image works on the nn
<viric>
I think I have nothing of value there
<viric>
why usbboot wants to be run by root?
<kyak>
maybe it needs some low-level access to your usb port, dunno
<viric>
my user has access to the usb device. I think it simply uses libusb... it should not need root
<viric>
maybe I have the permissions wrogn
<viric>
hm no
<viric>
kyak: hummm the '-e' on nanonote and block2mtd also look like being different
<kyak>
viric: i think the best is to generate ubifs manually from staging_dir/target-mipsel_uClibc-0.9.30.1/root-xburst
<kyak>
using your mkfs.ubifs and ubinize settings
<viric>
maybe
<kyak>
will try do it tommorrow.. time to get some sleep
<kyak>
viric: thanks for your help!
<viric>
what is your timezone?
<kyak>
GMT+3
<viric>
ah ok.
<viric>
good night!
<kyak>
:)
<viric>
argh. It looks like 'nerase 16 4080 0 0" erased the uboot too.
<viric>
I can't understand why.
<wpwrak>
viric: meanwhile, deep in the mind of your computer: "hmm, he made me erase u-boot in a pretty convoluted way. I can't understand why."
<viric>
convoluted? :)
<viric>
aren't 16 blocks the offset for the rootfs?
<wpwrak>
naw, i don't know what happened :)
<viric>
I imagine that for ubi, it's always the case that the flash has to be fully erased?
<wpwrak>
dunno. never touched UBI. way too complex for my taste.
<viric>
don't you use ubi?
<viric>
and, what has that to do with ubi? :)
<viric>
it's uboot that got erased :)
<wpwrak>
(use ubi) well yes, but i don't understand its internals much like i don't really understand the quantum physics going on in transistors, yet i use them ;-)
<wpwrak>
(what to do with ubi) well, you asked about it ;-)
<viric>
ah I already had forgot my question about ubi :D
<wpwrak>
your computer and you *are* similar ! you forget about the question, your computer forgot about u-boot. have you considered the possibility that you might be an AI running in a different virtual machine on the same hardware ? a hardware with memory problems. ;-)
<qi-bot>
[commit] Werner Almesberger: qpkg: rearrange things in prereq.c to free the stack paradigm for other uses http://qi-hw.com/p/wernermisc/d0a1a9e
<qi-bot>
[commit] Werner Almesberger: qpkg/prereq.c (print_debug, resolve): moved debug output to separate function http://qi-hw.com/p/wernermisc/e1404bb