<wolfspraul>
kristianpaul: so you think the Ben might be shut down into a different (still zero power) state out of which it could start faster?
<kristianpaul>
wpwrak: hehe ;)
<kristianpaul>
wolfspraul: yes i do
<kristianpaul>
gusnao: hey there, you should update your ben to last firmware i think, you'll get surprized for all new apps
<gusnao>
kristianpaul, ok, thanks
<tuxbrain_away>
before try the Jay7 aproach of qemu, I would like to know what is wrong with this configure params and how to rid off of that checking I had follow the Canadian compilation instructions on that page http://www.airs.com/ian/configure/configure_6.html
<zrafa>
wpwrak: I have a bit of irc thanks to you :)
<wolfspraul>
I have something I cannot really wrap my mind around, maybe I find help here :-)
<wolfspraul>
so we made 100 jtag-serial daughterboards
<wolfspraul>
sent out about 30 to milkymist one rc2 buyers, recalled/replaced some
<wolfspraul>
some sent here and there for development reasons
<wolfspraul>
now the stock is down to 62
<wolfspraul>
and sinking (with every rc2 sale)
<wolfspraul>
the milkymist one rc3 run will be 80 units
<wolfspraul>
let's say 75 are 100% good = sellable
<wolfspraul>
so I need to make another batch of jtag-serial boards
<wolfspraul>
but how many?
<wolfspraul>
we will fix a few bugs, so new pcb
<wolfspraul>
currently I am thinking I make 200
<wolfspraul>
that's because my confidence that they will work is high from the first run, this time even flashing and testing will be faster with only free tools
<wolfspraul>
we need some to go with rc3, and some more to go with xue or other future milkymist-like boards
<wolfspraul>
does anybody want to buy some of them alone?
<wolfspraul>
the additional cost of making more is small, compared to the one-time costs of pcb making, smt run, and general overhead of a run
<wolfspraul>
so I could also make 300 or more :-)
<wolfspraul>
but I need some sufficiently sane reasons for that other than 'there will be some magic use case for them later'
<wolfspraul>
kristianpaul: wow that mimiandeunice stuff is great!
<wolfspraul>
she says it's licensed under cc-by-sa, but then she says "For commercial uses, I request you share money with me."
<wolfspraul>
I've seen this a number of times, typically such an additional 'request' is understood to be merely an option, but wanting to respect the author it does make me feel a bit strange.
<wolfspraul>
I guess the -nc license was not an option for her either.
<rjeffries>
how does the MM JTAG/serial board compare with other JTAG boards
<wolfspraul>
no idea. it is tailor made for the m1 case, both in hardware and software
<wolfspraul>
of course we follow standards whereever possible, but afaik there weren't many attempts (if any) at making this a swiss-army-knife type of thing
<wolfspraul>
which is totally fine by me. I will not try to market it stand-alone either. but if someone here says "make another 50 for me", then that's easy to do in the upcoming run.
<wolfspraul>
if xue remains in dormant state, and we reboot the idea of a mobile minimilky board, that one will use the same connector as m1 (and thus the jtag-serial board) for sure
<rjeffries>
wolfspraul what connector does it use?
<rjeffries>
is xua the camera board?
<rjeffries>
xue
<wolfspraul>
it has a usb mini-b connector on one side, to connect to the host computer (and export 2 usb interfaces, serial and jtag)
<wolfspraul>
on the other side, it has a 100mil 4-pin serial header, and 2*7 jtag header
<wolfspraul>
xue is the camera yes, but (I stand to be proven wrong), I'd say it's on life support right now, at least I don't see any action that makes me believe we will see a xue board or camera any time soon
<wolfspraul>
which means that once I worked down the list of my current manufacturing priorities, I will restart the idea of a mobile minimilky board from scratch
<wolfspraul>
my current manufacturing priorities are:
<wolfspraul>
1) milkymist one rc3 run (first work on improvements)
<wolfspraul>
2) another jtag-serial run to go with it (also including improvements)
<wolfspraul>
3) ben-wpan, both usb and 8:10
<wolfspraul>
want to get all those done asap
<wolfspraul>
and after that it's either xue, if it is closer to manufacturable state by then, or a mobile minimilky idea rebooted
<rjeffries>
sounds like 6 to 9 months of effort calender time
<wolfspraul>
well let's see. we learn and can reuse more and more.
<rjeffries>
is xue project fron Andres?
<wolfspraul>
yes
<wolfspraul>
but it's not in manufacturable state, and not getting closer the last 2 months
<wolfspraul>
so I first need to work down the current manufacturing stuff, then I'll get back to it
<wolfspraul>
btw, end of February is approaching and we need to finalize the 03-01 community news
<wolfspraul>
from valentine ascii art to ubb to gps baseband work - good stuff but needs a lot of polishing to be publishable
<wolfspraul>
I want to list a few of the new ports that were added into the openwrt image last month. so far I have Emacs, GNU Octave, zgv, supertux, sokoban, qball
<wolfspraul>
any additions?
<wolfspraul>
ah, I also need to mention Xiangfu's 02-23 release...
<wolfspraul>
ok I will add MPlayer and flite to the list
<wolfspraul>
kristianpaul: do you have some sort of screenshot for Lua on Milkymist One?
<wolfspraul>
(I'm talking to myself, I know. hoping that people will read the backlog later...)
<wolfspraul>
answer: yes, he has a screenshot, and it's cc-by-sa licensed, and I updated the community news already
<cfy>
can i change my keyboard in nn?
<cfy>
i found the g key is not good as others
<rjeffries>
XChat looks better than Smuxi
<wolfspraul>
cfy: no the keyboard is just one piece and individual keys cannot be exchanged.
<wolfspraul>
most likely if you feel that one key works less well than others, it's because of very small tolerances in where the plastic finger that pushes on the metal dome sits exactly, like not being centered.
<wolfspraul>
it may go away over time, or if you wiggle the key a bit
<wolfspraul>
ok I've made some progress on the community news
<wolfspraul>
what is still missing imo is something about fosdem, and more Milkymist news
<cfy>
wolfspraul: can i change a whole keyboard?
<wolfspraul>
theoretically yes, but I don't think anybody has replacement keyboards in stock, and we haven't really made any excess replacement keyboards either
<wolfspraul>
there are a total of 3 parts
<wolfspraul>
first the PCB itself
<wolfspraul>
then above that, a 'metal dome mat'
<wolfspraul>
the metal dome mat is glued onto the pcb
<cfy>
wolfspraul: oh.got it.
<wolfspraul>
sometimes if a key doesn't work very well, it may also be because that one metal dome over the 'g' is not in the best position for the underlying conductive area of the pcb
<cfy>
wolfspraul: i change my way to press g,then i is easier to press.thank you .
<wolfspraul>
then above the metal dome mat is the keyboard, a plastic/metal structure that is made in one piece
<wolfspraul>
most of the time the kind of problem you report goes away over time
<cfy>
oh
<wolfspraul>
it has to do with tiny tolerances
<wolfspraul>
we tried fixing some of these things on the spot, but that always made it worse
<wolfspraul>
whereas just waiting (and using) the Ben for a week made it go away :-)
<cfy>
hehe:)
<wolfspraul>
there may also be tiny particles enclosed between the pcb and (glued) metal dome mat
<wolfspraul>
sometimes those particles move when you use the key (are pushed aside)
<wolfspraul>
theoretically you could start over, lift the keyboard, remove the glued metal dome mat
<wolfspraul>
but removing the glued metal dome mat will surely damage it to the extent that you need a new one to glue onto the pcb
<wolfspraul>
and there may be glue residue from the old one
<cfy>
oh.got it
<wolfspraul>
and you need to clean both the pcb as well as the new metal dome mat so that it's actually better than before
<wolfspraul>
I suggest to just use the key for now, wiggle it a bit, and see whether it gets better.
<cfy>
okay
<cfy>
i think it's better now:)
<wolfspraul>
the problem is in centering or some obstacles (particles) between pcb, metal dome, and plastic finger that pushes the metal dome down onto the pcb, to make a contact
<cfy>
i press g then display g.
<wolfspraul>
well thanks for reporting. keyboard problems are rare, but I do hear it once in a while.
<wolfspraul>
just hard to actually improve the keyboard, and not make it worse :-)
<cfy>
:)
<wolfspraul>
next is a capacitive touch keyboard, I think :-)
<wpwrak>
wolfspraul: (jtag) i think it's the number you need for MM1 runs, plus the extra sales, plus the quantity you feel comfortable stocking forever. the extra sales would be something like 10, if the openmoko debug board is any indication. (i don't have its sales details, but i heard that some were sold for non-openmoko use, but you didn't hear much about these)
<wpwrak>
i wish 2011 was a leap year. that would increase the probability of getting wpan into the 2011-03-1 news ;)
<wpwrak>
well, not having wpan there gives ubb more room :)
<wolfspraul>
I feel very comfortable stocking those little boards for several years :-)
<wolfspraul>
because I think Milkymist will develop slowly (and strongly), and eventually take off when we have the right set of features and demand.
<wolfspraul>
but on the other hand making 300 or even 500 now seems just excessive
<wolfspraul>
unless I overlooked something
<wolfspraul>
the 03-01 news is shaping up
<wolfspraul>
hopefully tuxbrain can add a little about fosdem, and a picture or two
<wolfspraul>
then I need to dig a bit more about milkymist, I'm sure there was more last month
<wolfspraul>
(this month)
<wolfspraul>
wpwrak: can you glance over it now? did I forget something?
<wolfspraul>
(it still needs a lot of editing, so the only point right now is to look for missing news)
<Jay7>
wolfspraul: I hope to fit with kexecboot in 03-01 too :)
<wolfspraul>
oh wow. it would help me more if people polished or edited the existing snippets, rather than trying to rush in something on the last day.
<wolfspraul>
but sure, if it's working then let's get it in.
<Jay7>
well.. I'm waiting recipe for OE
<Jay7>
I hope tonight or tomorrow
<Jay7>
I'll add note to page after
<wolfspraul>
Jay7: btw, what's the full name of your wife? I only say Irina now...
<Jay7>
Irina Bushmeleva
<wolfspraul>
ah great, thanks
<Jay7>
may you add link to blog too?
<wolfspraul>
of course, that's great!
<Jay7>
10x :)
<wolfspraul>
it's just details details details, takes hours to polish and edit the news page
<Jay7>
yeah..
<wolfspraul>
I'm sorry for my ignorance, but what exactly is kexecboot and what will we be able to do once it is in Jlime?
<tuxbrain_away>
Jay7: native-sdk-image for qemumachine in progress
<tuxbrain_away>
my last chance
<kyak>
larsc: trying to built-in sound modules in kernel - so far so good. The only problem is that kmod-sound-core package gets selected (by AUDIO_SUPPORT) and built in any case. Therefore it tries to load the already compiled-in modules during boot.
<kyak>
It's not a big problem, but doesn't look very clean in dmesg
<kyak>
larsc: do you have an idea what could be done to build these kmod-sound-* as openwrt modules (i.e. not to include it in rootfs)?
<larsc>
kyak: remove the autoselect
<kyak>
autoselect, huh?
<larsc>
of the kmod-sound-core by AUDIO_SUPPORT
<larsc>
or a add a depends on @!TARGET_xburst_nanonote
<kyak>
i'm looking at target/linux/xburst/qi_lb60/target.mk
<kyak>
it has DEFAULT_PACKAGES
<kyak>
listing these sound modules
<kyak>
i'll try to remove it now
<larsc>
these should be removed, if sound support is built-in
<kyak>
i hope this would be enough
<kyak>
hmmm i wonder what needs to be done for the changes in target/linux/xburst/modules.mk to be seen by menuconfig..
<larsc>
touch package/kernel/Makefile
<kyak>
larsc: alsa-lib selects kmod-sound-core, too -\
<kyak>
seems we can't disable it just on our side, some upstream work is required, too
<wolfspraul>
tuxbrain_away: thanks that's a good start. I will do some more editing and polishing tonight or tomorrow.
<wolfspraul>
it's going to be a nice news update
<wolfspraul>
I only wish I had more time to translate what a lot of this tech stuff means for the end user.
<wolfspraul>
it's unfortunate that this is not really happening now, need to do more of that later...
<kyak>
larsc: so, if i add e.g. @!TARGET_xburst_qi_lb6 to kmod-sound-core DEPENDS, alsa-lib gets deselected, too
<kyak>
*lb60
<kyak>
and i think that even if alsa-lib will not autoselect kmod-sound-core, it will not be possible to build kmod-sound-core as "=m" (to provide it with other kmod's in packages)
<larsc>
well, if sound support is built-in kmod-sound-* shouldn't be built at all
<kyak>
not even as a separate package, right?
<larsc>
yes
<kyak>
ok, i agree with that
<larsc>
that won't work. something can't be built-in and a module at the same time
<kyak>
i will try to make a patch for alsa-lib that would disable the kmod-sound-core dependency for TARGET_xburst_qi_lb60. I hope it can be accepted by upstream
<kyak>
there could also be some other packages that have such dependency
<kyak>
do you think it is the way to go?
<kyak>
larsc: what's the difference between CONFIG_DEFAULT_kmod* and CONFIG_PACKAGE_kmod* ?
<kyak>
now CONFIG_PACKAGE_kmod-sound are not autoselected, but CONFIG_DEFAULT_kmod-sound* are autoselected..
<larsc>
CONFIG_DEFAULT_packge gets defined if the package is the default package list
<kyak>
hm... i did remove those from DEFAULT_PACKAGES
<larsc>
you probably need to refresh the config somehow
<kyak>
hm okay.. it's somewhere else. i just rm -rf .config .config.old && make menuconfig, selected our target and saved the config.. These are still in default pacakges
<kyak>
ok, removing tmp/ did help
<kyak>
Default-Packages were recorded there in tmp/.targetinfo
<kyak>
larsc: how i can check for TARGET_xburst_qi_lb60 in alsa-lib's Makefile?
<wpwrak>
wolfspraul: (ubb) ah, that's february news indeed. how long those barely three weeks felt ;-) maybe put the two UBB entries next to each other ? (or merge if having two separate entries was an accident)
<wpwrak>
wolfspraul: if non-accident, maybe split the "what is UBB" information (i.e. things from my mail and the wiki page) from UBB production (preorders/shop link). the latter should probably also mention (explicitly) that tuxbrain took the decision to produce the boards and that they're being made right now.
<wpwrak>
(trying to convert rms) nice caption ! ;-)
<wolfspraul>
agree on your ubb feedback
<wolfspraul>
it's still just a meshup right now
<wolfspraul>
yes, separating it into several lines is better
<wolfspraul>
thanks for your feedback!
<larsc>
kyak: i don't think that is a good idea. generally i think adding target specific options to a generic package is not a good idea
<larsc>
kyak: so it's unlikley for that change to go upstream
<larsc>
but you could have it as a local hack in the qi-hw repos
<larsc>
kyak: the syntax would be +@TARGET_xburst_qi_lb60:kmod-sound-core
<larsc>
+@!TARGET_xburst_qi_lb60:kmod-sound-core
<wpwrak>
wolfspraul: do you want to include lars' boot time enhancement ?
<larsc>
lars' and davids
<wolfspraul>
sure why not, but I will first edit/polish all the snippets I have there now.
<wolfspraul>
unfortunately only very few people are helping with that community news WIKI page :-)
<wolfspraul>
I am not happy with the wording of many of those snippets, I would like to spend more time to explain/translate what it MEANS, rather than just listing accomplishments.
<wpwrak>
dvdk: sorry, lars and david's :)
<wpwrak>
wolfspraul: yeah, the wording needs a little more flesh
<wolfspraul>
but in order to describe what it means, I first need to mentally zoom out and actually think about what it means, if anything :-)
<wolfspraul>
also I want to throw in a snippet about osmocom progress on that mtk 6235 phone, at least I had the plan
<wolfspraul>
but then they are not yet talking to the 6140 tranceiver IC, and who knows when/if they will. so it's just reverse engineering a few digital peripherals. not sure whether I should mention it or not.
<wolfspraul>
yes, although I am hardly capable of writing one consistant sentence about what this 'avrdude' actually does
<wolfspraul>
I can just guess. 'reflashing an Arduino'?
<wpwrak>
;-)))
<wolfspraul>
all Arduinos? or just some models?
<wolfspraul>
no idea
<wpwrak>
it's a utility to read/write/verify flash/eeprom/fuses of AVR chips. pretty much all of them, i think.
<wolfspraul>
writing good news is hard, it's a mix of technical correctness, translated to be easily understandable, correctly referenced facts (urls), etc.
<wpwrak>
things like the atmega attiny and so on. includes the arduino universe, of course.
<wolfspraul>
there you go. where is the sentence?
<wolfspraul>
"Ben NanoNote - now with AVRDUDE" (whatever that means) :-)
<wpwrak>
man avrdude says  avrdude -- driver program for ``simple'' Atmel AVR MCU programmer
<wpwrak>
"Avrdude is a program for downloading code and data to Atmel AVR microcontrollers."
<wpwrak>
that one doesn't sound too bad
<wolfspraul>
yes
<wolfspraul>
and that avrdude is now running on the Ben?
<wpwrak>
the main contribution is not the cross-compilation, which is quite trivial, but the driver for the nanonote's 8:10 gpios
<wpwrak>
i haven't tried building it for openwrt yet. not sure if autocrap is happy with the "light" host environment provided by openwrt. let's try ...
<wpwrak>
ah yes, looks good
<wpwrak>
let's see if it actually works ..
<wpwrak>
works like a charm :) now,let's update the readme ...
<wpwrak>
wolfspraul: tuxbrain is working on a more comprehensive AVR development environment on the ben, with gcc running there natively and such (and of course avrdude)
<wpwrak>
amazing. february was such a busy month, yet we're still 3 kB (compressed) short of the january list traffic
<kyak>
larsc: thanks for your hints! i'm doing final tests now..
<wpwrak>
(traffic) would be interesting to have list traffic and irc traffic statistics. maybe what's happening is a shift from the list to irc
<kyak>
i always said that IRC > ML :)
<kyak>
wpwrak: now count the words in mailing lists, it would be much less :)
<xiangfu>
!help
<wolfspraul>
man I'm glad werner beat me. I better bite my tongue.
<wolfspraul>
I did a lot of bla bla talking the last few days, some people may think I'm bored.
<wolfspraul>
better get some work done :-)
<xiangfu>
kyak: how to show the help of this bot?
<xiangfu>
panda|x201: what is your name in QQ group?
<kyak>
do you think it should respond to the !help?
<xiangfu>
kyak: that will be great.  I saw dvdk input one. :)
<wolfspraul>
ok I will edit more tomorrow
<wolfspraul>
some were already mentioned in 02-01, I don't want to mention the same app twice
<kyak>
yeah, i saw people doing that, too.. i'll do, isn't hard
<wpwrak>
i wish we had a format where it's easier to have an overview of things. maybe with one wide column for the text and a column on the left for a picture or two. then end each section with the remaining pictures. would require pictures to have relatively small thumbnails (maybe 300x200 pixels) to look right, and would need some means for making it easy for the reader to connect text with then spacially disjoint pictures
<dvdk>
wolfspraul: well Brainless is pretty new, the others packages have been mentioned before (but weren't part of the official image back then).
<wpwrak>
i think it's good to have all the key information on one page, so i like this better than microscopic thumbnails. but it still looks a bit disorderly. well, one could experiment with the material from existing news and see if a nicer layout is possible
<dvdk>
btw xiangfu, were was the phote with RMS shot?  just wondering.
<panda|x201>
xiangfu, oh, I'm not in your QQ group yet
<panda|x201>
xiangfu, I rarely use QQ for years
<panda|x201>
xiangfu, mostly, I'm a software engineer
<panda|x201>
xiangfu, I have face to face meet with Wolfgang last year and bought Ben from him directly
<wolfspraul>
panda|x201: ahh!
<wolfspraul>
did you also borrow a wifi card from me?
<wolfspraul>
I lost track of some of them :-)
<panda|x201>
woakas, yes, I'm the guy
<panda|x201>
wolfspraul, I still using your wifi card on my demo device
<wolfspraul>
oh that's good to hear - keep it then
<panda|x201>
wolfspraul, also without paying your cash yet
<wolfspraul>
you paid for the NanoNote I think, and the wifi card is loaned
<wolfspraul>
all fine
<wolfspraul>
great to see that you are still around, and the Ben is still being used
<wolfspraul>
very good!
<wolfspraul>
as you can see software is improving :-)
<panda|x201>
wolfspraul, yeah, of course, very positive progress
<panda|x201>
wolfspraul, also, I've promoted this device with most of the guys I met with
<panda|x201>
wolfspraul, it's one of my favourite gadget now
<wolfspraul>
nice
<wolfspraul>
how about Milkymist One? :-) can I upsell you to Milkymist One?
<wolfspraul>
he he
<wpwrak>
we should get that on video, for promotion ;-)
<dvdk>
xiangfu: try to sell him one next time you meet.  and tell him that it runs GNU Emacs :)
<dvdk>
but maybe RMS won't buy it unless it's named GNU Nanonote
<panda|x201>
wolfspraul, oops, what is Milkmist One?
<panda|x201>
wolfspraul, yes, I can buy your Milkymist One to show my royalty for qi :-)
<xiangfu>
dvdk: :)
<dvdk>
btw there's more truth in it than you might think.
<wpwrak>
dvdk: GNU/Nanonote ?
<wpwrak>
since it's hardware, shouldn't it have horns then, too ?
<wolfspraul>
panda|x201: read a bit on milkymist.org first, if you have a little time
<dvdk>
last time i mentioned the NN emacs port  on the emacs-devel mailinglist, RMS contacted me off-list and asked why openwrt weren't part of the GNU project.
<wpwrak>
maybe something for the future: gnu-horn shaped wireless antennas, maybe like the olpc's foldable "ears"
<wolfspraul>
panda|x201: it's a very different product from Ben NanoNote, but in the long run they belong together
<dvdk>
"do these people think their freedom is for the birds" or something.
<wolfspraul>
as a 'cool toy', I'm sure Milkymist One will qualify for that category in a few months, if it's not even in there already
<kyak>
xiangfu: --^
<xiangfu>
kyak: thanks
<kyak>
np :)
<wolfspraul>
panda|x201: it's more challenging that Ben NanoNote too, but it does take things to a new level in some important areas. check it out, let me know what you think.
<wolfspraul>
that's mostly just the production side
<wolfspraul>
the homepage of the project is milkymist.org
<panda|x201>
OK, step forward ...
<xiangfu>
dvdk: how did you reply RMS's email ?
<dvdk>
xiangfu: told him that it's mosty gnu software anyways, and he shouldn't be so conceerned about direct affiliation w/ the GNU project
<panda|x201>
wolfspraul, nah, I'm not an artist like VJ and DJ, so does milkymist still fit me then?
<wolfspraul>
not sure :-) you can look at it in many ways
<wolfspraul>
I get that kind of reaction a lot though "I'm not a DJ/VJ, it's not for me"
<dvdk>
xiangfu: then i told him that i'm a little dissatisfied with the GPL license in the open source hardware field.  but he didn't really respond to this.
<wolfspraul>
panda|x201: kristian paul is working on a GPS baseband for Milkymist (One)
<wolfspraul>
we had plans to work on a milkymist-based camera, though that project is dormant right now (to be resurrected)
<wolfspraul>
since it's a free IC design, there are many possibilities once we get the foundation right
<kyak>
dvdk: why did you start talking to rms in the first place?
<dvdk>
kyak: he started the offlist conversation.
<kyak>
hm, i might have missed the e-mail from him :)
<wolfspraul>
panda|x201: were you working on robotics stuff? (I forgot...)
<wolfspraul>
we need to explain better why milkymist one is interesting to a non-dj/non-vj
<panda|x201>
wolfspraul, yeah, we have a robotics studio locally in Beijing, www.ucrobotics.com
<wolfspraul>
ok, I gotta go. great that we reconnected, let's continue soon...
<wolfspraul>
and very nice to hear the Ben (and wifi) are still alive and with you :-)
<panda|x201>
wolfspraul, yeah, me too :-)
<wpwrak>
wolfspraul: (non-vj) maybe mention LHDL prominently there, too. play with a big fpga and *** Free and Open Synthesis ***\footnote{\fontsize=5pt in progress) ;-)}
<larsc>
llhdl
<wpwrak>
gaah. i knew i'd get the darn acronym wrong !
<larsc>
low-level hardware description language ;)
<wpwrak>
yeah yeah. it will have left my memory by the next time i need it, i'm sure of that ...
<confusedpear>
I need assistance with debian on my nanonote. I can't get the sd card to show up and mmcblk0p1 isn't in /dev
<xiangfu>
confusedpear: what is the "dmesg" when you insert the sd-card? what is your kernel version? where you download the kernel?
<confusedpear>
is the dmsg the text that ordinarily pops up when you put it in or do i need to look at with something?
<confusedpear>
if the nanonote is recognised in lsusb as device 007 does that mean that i should put usb(0?)07 for  ifconfig?
<xiangfu>
confusedpear: no.
<confusedpear>
so usb0 is fine?
<xiangfu>
yes.
<confusedpear>
I'm running ubuntu right now, I believe i've successfully pinged the nanonote but it is giving me permission denied on the echo command in the nat config section
<xiangfu>
confusedpear: try 'sudo ....'
<confusedpear>
I assume an echo isn't that important what does that command do?
<confusedpear>
I did
<confusedpear>
it references the folder when it gives me permission denied
<xiangfu>
confusedpear:echo "1" |sudo tee /proc/sys/net/ipv4/ip_forward
<xMff>
xiangfu: I have some patches for qi packages in preparation for upcoming openwrt changes, would you mind to commit them?
<xiangfu>
confusedpear: if you insert the card. kernel will output something like mmcblk0... attached.
<confusedpear>
it wasn't doing that
<confusedpear>
i suspect it wouldn't but would being exposed to cold weather affect the sd reader?
<kyak>
xiangfu: btw, as xMff just mentioned, we would need to catch up with the latest backfire backports, there are some important autoreconf changes there..
<xiangfu>
confusedpear:Â Â not sure that.
<xiangfu>
kyak: ok.
<xiangfu>
I will try to work on that tomorrow or the day after tomorrow.  :)
<xiangfu>
kyak: I will work on u-boot a little first tomorrow.
<kyak>
sure, it's a good thing joe has some patches already, very kind of him :)
<confusedpear>
yeah i got the card i was originally trying to mount to mount but it's not displaying the insert/remove message
<xiangfu>
kyak: joe?  joe-full? sorry I confuse.
<kyak>
xiangfu: jow aka xMff :)
<kyak>
sorry, mistyped it..
<larsc>
whats that black stuff called thats put ontop of the soc?
<kyak>
xiangfu: those ALSA warnings during gmenu2x start are gone now, and i hope that we also won some milliseconds with monolythic kernel :)
<xiangfu>
kyak: 'flite' have some noise in 02-23 kernel, I guess it's because enable CONFIG_I2C , I will test the new kernel. see if 'flite' work fine like before.
<kyak>
xiangfu: i remember i mentioned it once.. let me find it
<kyak>
"i noticed that playing the resulting file with aplay produces much better result than playing the output immediately"
<kyak>
i can confrm again that flite -t "test string" play.wav && aplay play.wav is much cleaner than flite -t "test string" play
<xiangfu>
kyak: oh. yes. I remember that now. I will test it again.
<kyak>
xiangfu: how do you think - should we mark console apps with a small "C" letter in the corner of the icon. Or maybe put them in a separate gmenu2x tab?
<kyak>
i feel there already are too many gmenu2x tabs :)
<kyak>
but we need to separate console and gui somehow
<xiangfu>
kyak: I would like the "C" letter.
<xiangfu>
since we already have those section. and I don't want like Console-applications  and GUI-applications :)
<kyak>
ok, we can start adding the C step by step. I'm sure this can be automated, too
<kyak>
xiangfu: you also mentioned the option for gmenu2x to start the setfont2. I like the suggestion from jirka to separate it per applications. i.e., some applications definitely profit from setfont2 fonts, but some really need colors etc
<kyak>
so it could be done per icon
<kyak>
or maybe just call the regular setfont with terminus-12, for example, for apps like mc or aewan
<kyak>
in this case, we are flexible
<xiangfu>
kyak: yes. that 's sound much better. as long as we don't touch too much gmenu2x code.
<xiangfu>
:)
<kyak>
no, it can be done from gmenu2x's icons
<kyak>
by exploiting it's "parameters injection" vulnerability :)
<xiangfu>
sure.
<xiangfu>
kyak: if we have terminus-12. I think most of the application will like using terminus-12. :)
<kyak>
i agree, it looks not so bad. But setfont2's 6x10 is still better when you don't need colors, but rather clean lines
<xiangfu>
the gmenu2x upstream active again. so I need send our patches to upstream. add nanonote support to gmenu2x upstream.
<kyak>
well ok.. hope the upstream will have a good run
<xiangfu>
kyak: I got goto sleep. see you.
<dvdk>
kyak: the small font hurts my eyes  :)
<larsc>
interesting ingenic signed a licensing deal with MIPS Inc. in january, so now it's actual legel to sell nanonotes ;)
<Jay7>
tuxbrain_away: I'm using that script to run native-sdk-image for arm target
<Jay7>
replace qemuarm with qemumips[el]
<Jay7>
may be need to look over qemumips -M ? before
<Jay7>
oh, qemu-system-mips
<Jay7>
        machine="malta"
<dvdk>
larsc: so now we are allowed to use these non-aligned load instructions. haha.
<Jay7>
according to OE's contrib/qemu/run-qemu.sh script
<rjeffries>
Ben as a way to create arduino/avr code and then flash the target is pretty damn BIG news,
<Jay7>
great news
<Jay7>
Andrea have first prototype of linux-kexecboot for nanonote
<Jay7>
I'll test in following 4-5 hrs
<Jay7>
[16:48] <ant__> 1) does nanonote work with vanilla 2.6.36 + patches? why keristoffer's tree?
<Jay7>
[16:49] <ant__> 2) mkimage seems a bit not standard, why? custom u-boot?
<Jay7>
hm.. may be #jlime is better place to ask this
<Jay7>
because we are using jlime recipes as reference
<kyak>
rjeffries: you need to read instructions in thesycon's driver readme
<kyak>
it explains how to put correct Device ID/Manufacturer ID in inf file
<kristianpaul>
playing with parallel port
<kristianpaul>
kyak: I saw him last time jue ene 06 2011 09:52
<kristianpaul>
take that bot !
<kyak>
--)
<kyak>
well, nebajoth is the only hope to bring that article back and help rjeffries :) i'm not going back to windows to recall how i connected Ben to it
<rjeffries>
well now that I tried to get NN going w/Ubuntu I ran into an error. see mailing list
<rjeffries>
thanks kyak fro the hint
<rjeffries>
is the Ben NN device ID mfg ID published on wiki?
<rjeffries>
Note - if you use Ubuntu, consider removing the default connection-manager, and replacing it with wicd. The connection manager has issues with adding & removing networking hardware, while wicd ignores usb0.
<bartbes>
you're a bit harsh on nm
<bartbes>
I think I set it to ignore usb0
<rjeffries>
that note comes from the wiki
<rjeffries>
my near term goal is simply ssh from ubuntu to nanonote to have a human size keybaord and screen
<bartbes>
there we go:
<bartbes>
/etc/network/interfaces
<bartbes>
iface usb0 inet manual
<bartbes>
that ought to do it
<bartbes>
I think..
<rjeffries>
thanks I will try now
<rjeffries>
.
<rjeffries>
after editing the /etc/network/interfaces file to add: iface usb0 inet manual
<rjeffries>
do I need to reset ubuntu for this to take effect?
<Jay7>
we can bundle NN with g_storage which will contains user manual and some software (for windows - putty and usbnet driver)
<Jay7>
then user can switch usb mode from g_storage to g_ether
<Jay7>
via some interface
<Jay7>
is looking for latest working Qi's u-boot
<kristianpaul>
Jay7: that one u pointed seems be the right one
<tuxbrain_away>
Jay7: (g_storage) for me NN should have a g_ether, g_storage, g_input(keyboard) and a little app than let you chose whatever you want in some moment.
<Jay7>
tuxbrain_away: good plan :)
<Jay7>
opie and gpe have such applets iirc
<Jay7>
at least I have seen something like on Zauruses
<tuxbrain_away>
and if is posible mix at least input and ethernet... wow :)
<rjeffries>
well good news is Ben now talks to my Ubuntu
<rjeffries>
I'll solve NN to Internet voa Ubuntu
<rjeffries>
how hard can it be
<Jay7>
hehe..
<Jay7>
have resolved it w/o configuring NAT on desktop
<Jay7>
just added static route to home gateway and NAT it there
<Ineedhelp>
hello i have a asus xonar D2/PM 7.1 PCI i installed laatest driver and no sound with my logitech z5500
<xMff>
wrong channel, sorry
<Ineedhelp>
2 RCA to 2 RCA
<Jay7>
Ineedhelp: this is not general hardware help channel
<Ineedhelp>
Whitch channel is it then?
<Jay7>
qi-hardware.org
<Ineedhelp>
WHITCH CHANNEL CAN I FIND IT
<Jay7>
ask on #help
<rjeffries>
sorry ineedhelp this is not the place you need good luck
<Jay7>
there was idea about base64('qi-hardware') ;)
<Jay7>
yeah.. to have xburst-tools on my archlinux I need to build cross-toolchain
<rjeffries>
if/when I unplug NN from Ubuntu lappie, will it work automagically when I plug back in guess I'll just try
<GNUtoo|laptop>
#hardware
<GNUtoo|laptop>
is the hardware help
<GNUtoo|laptop>
but he's gone
<rjeffries>
if/when I unplug NN from Ubuntu lappie, will it work automagically when I plug back in guess I'll just try. nope
<Jay7>
hm.. xburst-tools for archlinux is looking for configs/stages in /usr/local, not in /usr
<Jay7>
do somebody know maintainer (ormris)?
<Jay7>
/usr/etc/xburst-tools/usbboot.cfg
<Jay7>
oh sh#t
<Jay7>
/usr/etc is pretty..
<Jay7>
have added patch as comment to package in AUR
<Jay7>
is boot with 'M' pressed causes to boot kernel from SD?
<Jay7>
or just change root for current kernel?
<kristianpaul>
M -> SD yes
<Jay7>
how kernel should be named?
<Jay7>
just /uImage ?
<kristianpaul>
yes
<Jay7>
/boot/uImage
<Jay7>
starting kernel... and nothing :(
<Jay7>
first attempt is failed
<tuxbrain>
Jay7: also there kernel images are not zimage are vmlinuz there is any other config parama I must setup on OE? or this will also work with qemu? btw I have to install qemu in my host (apt-get qemu) or there some place in OE and just I have to add it to the PATH?
<Jay7>
tuxbrain: use your host's qemu
<Jay7>
wrt kernel image - no idea.. it should just work
<Jay7>
just pass your image as -kernel
<Jay7>
is thinking from where to start to debug kernel..
<tuxbrain>
damn it doesn't generate the ext2 .. I have cheked it is on local.conf....
<Jay7>
bad that there is no serial..
<Jay7>
tuxbrain: what distro you are using?
<tuxbrain>
Jlime
<Jay7>
hm..
<Jay7>
well.. native-sdk-image is more minimal distro friendly
<tuxbrain>
what do you have?
<Jay7>
may be jlime have some other settings
<Jay7>
I've used minimal to build it
<tuxbrain>
ok just puting minimal on distro , roger
<Jay7>
this may require to rebuild all from scratch :(
<tuxbrain>
mean while build doesn't matter
<Jay7>
eh.. seems something is wrong with kernel image
<kristianpaul>
Jay7: You have last uboot version right?
<Jay7>
I've flashed one from link above
<kristianpaul>
good
<Jay7>
I'm looking over changes linux-kexecboot.inc does in kernel config
<Jay7>
may be lzma compression + gzip + uImage
<Jay7>
will try w/o all this stuff
<wolfspraul>
kristianpaul: he - it's great that Yi asked then! (about the cable length)
<wolfspraul>
you need to give us full feedback, every little thing :-)
<kristianpaul>
:p
<kristianpaul>
sure :-) i just answered
<wolfspraul>
yes, but it's amazing how long such things can go unnoticed.
<Jay7>
well
<Jay7>
it booted finally
<Jay7>
is looking on kexecboot @ NN
<tuxbrain>
Jay7: qemu: Too much memory for this machine: 384 MB, maximum 256 MB
<Jay7>
tuxbrain: replace -m value
<Jay7>
cool..
<Jay7>
now I should try to kexec something
<kristianpaul>
Jay7: boot? kexecboot?
<Jay7>
yep
<kristianpaul>
oh GREAT !
<Jay7>
I see it on NN :)
<kristianpaul>
pics !
<Jay7>
and it even looks alive :)
<Jay7>
moment, I'll prepare SD with jlime ;)
<kristianpaul>
You are in time for 2011-03-01 news ;-)
<kristianpaul>
ok
<tuxbrain>
Jay7: I know I'm start being very annoying but ... Could not load MIPS bios 'mips_bios.bin'
<Jay7>
wow
<Jay7>
tuxbrain: this is a bit over my knowledge
<tuxbrain>
the only thing that kind of do something is  -M mipssim it opens a window called qemu with something that looks like a console but commands there seems some kind of qemu previos to boot
<mth>
tuxbrain: which qemu are you using?
<mth>
there is a variant called qemu-jz which has hardware support that is not in the upstream qemu
<tuxbrain>
mth default in ubuntu lucid
<mth>
then there is no specific support for the Ingenic chips