<xakh>
the blues are brighter on his, caps lock arrow is a different direction, silver separator between f keys and qwerty
<xakh>
etc
<xakh>
just thought it was interesting
<wolfspraul>
xakh: ok so which one do you think looks better?
<xakh>
I like mine. :)
<wolfspraul>
ok good
<wolfspraul>
:-)
<wolfspraul>
zear has a really early one, from one of our small runs
<xakh>
ahh.
<xakh>
so mine's just newer.
<wolfspraul>
later we changed the power button to black, and the divider between F keys and other keys to black
<wolfspraul>
and we made the red print on the keys brighter I think
<wolfspraul>
I don't think we changed anything with the blue, but there were several changes on the keyboard so I'm not sure
<wolfspraul>
so bottom line, yes, yours is 'newer' from the mass production run
<xakh>
I'm still one of the original 500, right?
<wolfspraul>
you mean first 500?
<xakh>
yeah
<wolfspraul>
probably, don't know
<wolfspraul>
we have sold around 700 by now, I think
<wolfspraul>
have to remove that banner on the wiki, it gets annoying... :-)
<xakh>
I felt all warm and fuzzy being in such an elite club ;)
<wolfspraul>
well it's a start
<wolfspraul>
of course we need to sell many more
<wolfspraul>
but the most important right now is to sell to a crowd that really gets the idea, and supports us in the long run
<wolfspraul>
as you see on the list we still have a few people that buy it and it immediately starts collecting dust. which is sad but well it's another sale.
<wolfspraul>
xakh: if you have ideas how we can reach more people that can really enjoy the device where it is today, please spread the wor.d
<xakh>
actually I get tons of compliments on this thing
<wolfspraul>
great
<xakh>
biggest problem for adoption is a lack of a windows client, since that's what a lot of people I know use
<wolfspraul>
what should that client do?
<xakh>
be able to reflash it
<xakh>
also, an easier way to reflash
<xakh>
though I really like the current system
<xakh>
it'd take quite a bit of explaining to a normal user
<wolfspraul>
sure
<xakh>
like a switch would work well
<xakh>
oh, and of course wi-fi
<xakh>
even just b
<xakh>
I'm actually going to try to cross compile netsurf
<xakh>
which is a tiny browser
<xakh>
I should have all the kinks worked out in time for the Ya image.
<mth>
this contains the mask init you committed today, but at the bottom of the page it says "created 1 month 3 days ago"
<larsc>
hm. must be git. I sqashed the timer fix into the original commit
<mth>
and it kept the original date?
<larsc>
i guess
<larsc>
hm. i'm currently looking at the sound dma issue and playback only works if i set the source width to 16bit and dest width to 8bit. which is a bit strange imo
<larsc>
and i'm playing 16bit samples
<mth>
is it using the fixed dma.h?
<larsc>
yes
<mth>
I have tested with source set to 16 and 32 and dest always set to 16 and both configurations work
<larsc>
ok. forget it i'm apperently to dump to read the specs...
<larsc>
got the width encoding wrong again
<mth>
speaking of DMA, do you have any plans for scatter/gather list support?
<mth>
if not, I could have a look at it
<mth>
it would make an efficient deferred I/O implementation of SLCD possible, I think
<larsc>
i implemented it once but deleted it accicentally :/
<larsc>
hm. the dma engine gets an irq when there are at least 16 free slots in the fifo. with 16bits sample size shouldn't it be safe to transfer 32bytes per irq?
<mth>
if source size is 32 bits, does that also mean the data must be aligned to 32 bits?
<mth>
for 16 bit stereo that would not be a problem, but I don't know if it can be guaranteed for 8 bit or 16 bit mono
<methril_work>
larsc: i was taking a look to the kernel organization
<methril_work>
it`s possible to organize the jz chips inside ingenic folder or something like that?
<methril_work>
i see som SoC manufacturers does like that and keeps the mips folder cleaner
<larsc>
methril_work: yes, sure. but currently there is only one jz chip supported in the qi tree
<methril_work>
i see
<methril_work>
but if we do frequent updates with the ingenic repos. it`s better if we adopt this structure (with them) :)
<methril_work>
are there any schedule for mainline inclussion?
<larsc>
soon
<larsc>
(tm)
<larsc>
:)
<methril_work>
i was talking with carlos almagro about a jz patch to support RTAI or RT_PREEMPT
<methril_work>
we need a roadmap for kernel too :)
<larsc>
i'm not sure what it takes these days to be linux-rt compliant, but given that most of it is already included in upstream linux it shouldn't be to hard
<larsc>
roadmap is: get as much done as soon as possible...
<larsc>
i'm planning to send patches in for review when the merge window for 2.6.35 has closed
<methril_work>
ok
<methril_work>
i`ll try to get hands on next week
<methril_work>
if i could help...
<larsc>
sure
<methril_work>
let me know
<methril_work>
time to back to work
<methril_work>
we stay tunned
<methril_work>
thank you larsc (2.6.35 inclussion is a plan) ;)
<larsc>
2.6.36
<larsc>
2.6.35 will be the next upstream release for which the merge window will close soon.
<larsc>
mth: it is possible to set a minimum period byte size, so i guess it's safe to always use  a dma_width of 32 for the buffer
<mth>
I don't know how much difference it makes in practice, but it sounds more efficient
<mth>
it might halve the number of reads
<larsc>
or quarter for 8bit samples
<mth>
by the way, do you know whether it's useful to clock down the JZ CPU when the load is low? or is it just as efficient to run it at max freq for a shorter time and then let it be idle?
<mth>
as far as I know, the gain from lower clocking comes from being able to lower the voltage supplied to the CPU
<mth>
but I don't think that embedded devices do those kind of things
<larsc>
downclocking to 100 Mhz saves approx 5mA
<mth>
even when doing the same amount of work per second?
<larsc>
when idle
<mth>
ah
<mth>
I thought it might stop its clock when idle
<mth>
(the clock to the CPU part, not the SoC part)
<rafa>
But you say that any usb cable should work right? So I will try with some usb cable at home (removing one connector and soldering the tiny wires inside)
<rafa>
kristianpaul: I am asking because I do not have knowledge about those cables.
<kristianpaul>
rafa: yes is a 4 wire cable
<kristianpaul>
serial need 3
<kristianpaul>
so it should work
<kristianpaul>
but
<kristianpaul>
hmm
<kristianpaul>
wait
<kristianpaul>
rafa: what are you thinkign to plug the usb cable?
<tuxbrain>
heheeheh you have missunderstod the word... is the lammer the lammer....
<xakh>
heh, still.
<xakh>
I'm taking a small text editor
<xakh>
leafpad, as my first project
<xakh>
and I'm a bit stuck.
<tuxbrain>
what happens
<xakh>
I set up my build environment for xburst
<xakh>
but I'm not sure what I need for the makefile
<tuxbrain>
you can use the one of the tutorial as template
<xakh>
okay, I see that, but I'm sort of new to compiling my own packaged
<xakh>
*packages
<xakh>
I've been spoiled with precompiled repos
<xakh>
so after I copy the makefile from the site you recommend
<xakh>
where do I go?
<tuxbrain>
:) I understand in fact that tutorial was my first experience on making my own packages
<tuxbrain>
let me review,
<xakh>
ok
<tuxbrain>
read from the part of "Creating a Package with OpenWRT" from the same tutorial, it descrive that you have to create a folder , then put the Makefile there in it's own folder inside, and then add that folder to the feeds.conf etc etc... after you have done all this you should be able to see your package  in the make menuconfig under the section you have defined and be able to select and compile it as other OpenWrt package
<xakh>
...
<xakh>
I'm still quite confused.
<xakh>
so I make a folder
<xakh>
then I put the makefile in its own folder
<xakh>
then...
<FrankBlues>
waves
<xakh>
haldo
<xakh>
I'm learning how to compile
<xakh>
and probably frustrating tuxbrain
<xakh>
now, the leafpad compiler already has a makefile.
<xakh>
you're telling me I need to make another?
<steve|m>
xakh: leafpad itself of course already has a makefile.. but you need to add a makefile for the openwrt buildsystem to know from the package
<steve|m>
xakh: I have no idea which explicit version your're using (haven't a nanonote myself), but I've been playing around with openwrt a few years back
<steve|m>
the makefiles are all structured the same way
<xakh>
mine's for xburst
<xakh>
ok
<xakh>
so what do I need to do from here to make this package?
<steve|m>
after you have the makefile, you should see your package in the menuconfig menu
<tuxbrain>
have you changed the key variables on the,lets call it,"OpenWrt Makefile", then name of the package, sections... etc etc?
<xakh>
I didn't know it existed before someone linked it just now
<xakh>
I was just going on your tut
<tuxbrain>
no just to "package",
<xakh>
okay sweet
<tuxbrain>
after that you should run
<tuxbrain>
./scripts/feeds update
<tuxbrain>
./scripts/feeds install -p myfeed
<tuxbrain>
sorry not running yet!
<xakh>
hehe ok
<tuxbrain>
we must be a little sure what is in the Make file, can you send me a an email with it?
<xakh>
sure
<tuxbrain>
david@tuxbrain.com
<xakh>
alright, sent
<tuxbrain>
you have wrong package definition, I suppouse you have based it on gtkperf, basically you have to substitute "gtkperf" by leafpad in any appearance
<tuxbrain>
I should also remove the Xorg in the PKG_BUILD_DIR
<tuxbrain>
PKG_BUILD_DIR=$(BUILD_DIR)/$(_CATEGORY)/$(PKG_NAME) should be enough
<xakh>
ok
<xakh>
does that folder have to exist, or will it create it?
<xakh>
also, what am I going to need to do to show it in /card on the nano, so I can easily put it in gmenu2x
<tuxbrain>
no is part of the OpenWrt magic
<tuxbrain>
mmm after you finis the proccess you will end with a ipkg file
<xakh>
oh ok
<tuxbrain>
you copy that ipkg file and put it some where (the sd card or the internal flash) where you can run "opkg  install thecreated.ipkg"
<xakh>
what else do I need to remove from the makefile to make this go?
<tuxbrain>
and then it will be installed directly on the rootfs of the nano
<tuxbrain>
mmm send me it again :)
<xakh>
ok
<xakh>
should be there now
<tuxbrain>
ok, at first sight and with my knowledge seems ok now, let's try and see what happens
<tuxbrain>
./scripts/feeds update 23:07
<xakh>
just like that?
<tuxbrain>
./scripts/feeds install -p myfeed
<tuxbrain>
yes
<xakh>
oops, wait
<tuxbrain>
I guess
<tuxbrain>
what?
<xakh>
still in category xorg
<xakh>
oops. ;)
<tuxbrain>
well it just means that when you search for it in the menuconfig will appear under that categorie, nothing else
<xakh>
I know, under neatness, changed it
<tuxbrain>
once you run the avobe instrucctions the real fun will beguin :P
<rafa>
kristianpaul: where did tuxbrain point that?
<kristianpaul>
rafa: it was time ago
<kristianpaul>
i was bugging here about serial port and bn
<kristianpaul>
s/bn/Ben nanonote
<xakh>
oops
<tuxbrain>
rafa: and in honor to true was Carlos Camargo + Xiang Fu I'm just an verbose executor
<tuxbrain>
mmm have you setup the xburst architecture in make menuconfig (step 1 of the howto)
<tuxbrain>
?
<xakh>
yeah
<xakh>
I did
<tuxbrain>
mmm strange
<xakh>
am I supposed to be running that inside the menuconfig?
<tuxbrain>
nop the scripts to update feeds not
<xakh>
hmm
<tuxbrain>
mmm have you already run "make" to complile the toolchain, kernel, etc?
<xakh>
o.o
<rafa>
tuxbrain: a verbose executor is always a good proof ;)
<tuxbrain>
xakh: what computer you have due this step can take a while (on Quad core about 30 mins)
<xakh>
it's a decent, but aging laptop
<tuxbrain>
then, if you don't mind, I will go to sleep :P
<xakh>
haha
<xakh>
alrighty
<xakh>
well, when you think you'll be back?
<xakh>
so where do I go to run make?
<tuxbrain>
in the root of openwrt
<xakh>
okay
<xakh>
so /openwrt/openwrt-xburst in my case?
<tuxbrain>
weekend is for family, so expect I can't do another tutorial session until monday
<xakh>
that's fine.
<xakh>
thanks for all your help
<tuxbrain>
yes that's the folder
<xakh>
I'll just run that other command after this thing makes
<tuxbrain>
give me that thanks when we finish to compile that package, i also want it on the Nano :)
<xakh>
alrighty!
<xakh>
I'm glad I'm not the only fan of leafpad.
<xakh>
after this, maybe something a bit tougher, like a browser?
<steve|m>
too bad
<xakh>
?
<steve|m>
...leafpad uses the same icon as gedit in ubuntu lucid
<tuxbrain>
yes when those commands finish correctly, enter in make menuconfig search for the package leafpad, mark it as <M>Â Â exit and run make again
<steve|m>
(sorry, accidentially hit enter) ;)
<xakh>
ok
<xakh>
yeah it does
<xakh>
but I took their old one with the pencil and the leaf
<tuxbrain>
why it's bad? I think the text editor icon is some what standard of freedesktop.org, isn't it?
<xakh>
should look good in gmenu2x
<xakh>
yeah, but I think the leaf + pencil looks way cooler
<steve|m>
well, once you get used to something.. I use gnome-panel for launching the most important applications
<wolfspraul>
but other than that I would never rename free software.I think we should credit the people and projects that we are using more, not less :-)