<qi-commits>
juhosg: backfire: ar71xx: create separate 'factory' and 'sysupgrade' images for the Planex boards (backport of r21175) http://qi-hw.com/p/openwrt-xburst/24ddbc0
<wolfspraul>
cost me only about 100 USD for the service
<wolfspraul>
so I am thinking about buying some used Hanvon e-books on taobao, then do the same thing which maybe helps us follow a few traces and decode a few pins
<wolfspraul>
for those C3100 pics they needed 5 boards, but only because I asked them to return each individual layer to me. I think they can do it with 2 boards.
<wolfspraul>
so the total damage would only be 2*used Hanvon device + 100-200 USD + a few days
<wolfspraul>
but I don't know which one you guys focus on nowadays - the old N516, or newer N526 or something newer still?
<larsc>
wolfspraul: well we mostly know how things are connected, so i'm not sure if it would be worth the effort
<larsc>
onlything still unkown is the protocol of the ts controller
<larsc>
...but i'm getting a logic anlayser soon
<mirko>
larsc, the merge screwed up some stuff
<wolfspraul>
larsc: not sure this got through, chinese govt is erratically fighting openvpn traffic now...
<wolfspraul>
which of the hanvon models are you or openinkpot most interested in nowadays?
<mirko>
larsc, busybox patches do not apply anymore correctly
<mirko>
i wonder how this can happen after a merge
<wolfspraul>
still the 516, or newer ones?
<larsc>
well, the main focus is still 516.
<larsc>
but mostly all the hardware connections are known
<larsc>
so i don't know if it would be worth the effort to take the pcb apart
<wolfspraul>
sure I got that, no worries
<wolfspraul>
for the future it's still good for me to know I can take pics to follow any trace in the PCB for 200 USD
<wolfspraul>
could speed up a lot of things
<wolfspraul>
plus I also need to go back to Hanvon one day
<zoltanh7211>
I have several questions about nanonote
<zoltanh7211>
Who could help me
<gnufs>
how can we say if we can without knowing the question?
<zoltanh7211>
Oh, sorry my net provider has long lag
<zoltanh7211>
My question is is it possible to expand this PCB to an table device?
<zoltanh7211>
Bigger touchscreen, and bigger memory?
<zoltanh7211>
The target what we would like to see is an multimedia capable table deviice maybe with wifi module, there is an copyleft solution?
<zoltanh7211>
gnufs?
<jxself>
zoltanh7211: If you're asking if the NanoNote could be endowed with a larger screen & more memory, sure. Go for it.
<zoltanh7211>
jxself: Our group would like to redesign the nanonote, keep as much hw as possible and run as os an rebulded Fedora - precisely -Â Â with 512 Mbyte RAM, and bigger (9 col) screen with touchpad.
<zear>
say, is the path length for file browser in gmenu fixed yet?
<zear>
if not, let me tell you what lines of code need fixing
<larsc>
i don't think that it's fixed
<zear>
it's in a few places in the code
<zear>
you'll have to look for the rest of them, but
<zear>
dirdialog.cpp, line 184
<zear>
path.substr(0,11)!="/card"
<zear>
you should replace 11 with the length of the path in " "
<zear>
in our case it's 5 or 4 (i don't know if it counts from 0 or not)
<zear>
i forgot to change it from the dingoo version, where it pointed to /usr/local
<zear>
if the length of the path is wrong, you won't be able to go up the dirs in browser
<zear>
also, this might be a good opportunity to change the path to "/" and see how well gmenu2x works with the nand filesystem
<zear>
larsc, you copy?
<larsc>
yes
<larsc>
is there any reason to set it not to /
<zear>
larsc, it was designed to run on an fat filesystem sd card
<zear>
i'm not sure if it can handle symlink loops
<zear>
and i bet there are some in /dev/ or /proc/
<zear>
it might scan the filesystem for ever
<zear>
additionally, it will show the capacity of the nand instead of sd card on the gui bar at the bottom
<zear>
eventually, we can set the automatic game/app scanner to look only in a selected dir, let's say /card
<zear>
oh and larsc, why do you use the pandora's theme? it's designed to run in 800x480 resolution, hence the huge icons and wrongly positioned wallpaper
<tuxbrain>
good night from spain nanonoters
<zear>
tuxbrain, you mean good night, or good evening? :)
<tuxbrain>
well it's 22:00 here
<zear>
yeah, but "good night" is when you leave
<tuxbrain>
whatever :)
<zear>
i think "good evening" is the proper greeting until the morning
<tuxbrain>
and going to sleep early is proper for health and here we are :)
<zear>
:D
<tuxbrain>
I see a lot of commits this two days :) , any release date scheduled?
<zear>
tuxbrain, larsc is improving/fixing gmenu2x, that's probably gonna go for the next release
<tuxbrain>
also I want to confirm that with the lastest uboot patch from xianfu, tp4,tp5 used as UART0 has no interference with keyboard and work like a charm :)
<larsc>
hm, looks like upstream gmenu2x is dead
<tuxbrain>
lars:time for a fork?
<larsc>
it is already
<larsc>
but i was looking forwared to sending our patches upstream
<larsc>
but nothing was commited in their svn during the last year
<tuxbrain>
I think we will use gmenu2x in different way than is pretended, we have a full distro than some in next future will full managed by opkg
<tuxbrain>
gmenu2x was intended to manage individual ports
<tuxbrain>
and mess with overclocking
<tuxbrain>
two characteristics we really don't need
<larsc>
the overclocking feature was one of the causes for screen flicker
<larsc>
hm and their bugtracker is full with spam
<tuxbrain>
lasrc: If I have time I will like to work with the "easy" part of pimping gmenu2x, (theme/icons/shortcuts...)
<qi-commits>
Mirko Vogt: as usbboot often exists with exit code 0 (success), even if an major error occured, we have to handle things differently... http://qi-hw.com/p/openwrt-xburst/76a779f
<mirko__>
usbboot does exit with SUCCESS even when flashing failed
<tuxbrain>
ok :) big league coding :P
<qi-commits>
Mirko Vogt: move /etc/opkg/opkg.conf to /etc/opkg.conf as otherwise we're not overriding the default configuration http://qi-hw.com/p/openwrt-xburst/f9b833c