Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<Guest35674>
I assume I need to compile gmu to have mp3 rubbish support right?
DocScrutinizer05 has quit [Ping timeout: 244 seconds]
pabs3 has joined #qi-hardware
LunaVorax has quit [Ping timeout: 255 seconds]
wej has quit [Ping timeout: 272 seconds]
wej has joined #qi-hardware
xiangfu has joined #qi-hardware
pabs3 has quit [Remote host closed the connection]
DocScrutinizer05 has joined #qi-hardware
pabs3 has joined #qi-hardware
xiangfu has quit [Quit: Leaving]
Ayla has joined #qi-hardware
xiangfu has joined #qi-hardware
<Guest35674>
what do I need to do to add mp3 yuck support? recompile gmu,sox,mplayer? or for gmu is there a lib I can get from some were? like the devs 7.2 package?
<Guest35674>
right bed time.
Guest35674 has quit [Quit: Ex-Chat]
<kristianpaul>
you can lock terminal with byobu ;)
rejon has quit [Remote host closed the connection]
Ornotermes has quit [Ping timeout: 272 seconds]
Ornotermes has joined #qi-hardware
nikescar_ has joined #qi-hardware
nikescar has quit [Read error: Connection reset by peer]
rejon has joined #qi-hardware
Ayla has quit [Ping timeout: 268 seconds]
Ayla has joined #qi-hardware
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
rejon has quit [Ping timeout: 276 seconds]
Ayla has quit [Quit: dodo]
GCW-Now has joined #qi-hardware
<GCW-Now>
Does anyone know of an Ingenic 4770 Vivante GC860 OpenGL driver or the ITE IT6610 if so please contact me gcwnow@gmail.com
GCW-Now has left #qi-hardware [#qi-hardware]
rejon has joined #qi-hardware
porchao has joined #qi-hardware
panda|x201 has joined #qi-hardware
guanucoluis has quit [Quit: Leaving.]
panda|x201 has quit [Ping timeout: 248 seconds]
rejon has quit [Ping timeout: 248 seconds]
jluis|work has joined #qi-hardware
rejon has joined #qi-hardware
kilae has joined #qi-hardware
jekhor has joined #qi-hardware
kilae_ has joined #qi-hardware
kilae has quit [Ping timeout: 245 seconds]
kilae has joined #qi-hardware
kilae_ has quit [Ping timeout: 252 seconds]
ni6htc0d3r has joined #qi-hardware
ni6htc0d3r has left #qi-hardware [#qi-hardware]
<xiangfu>
wpwrak, Hi
rejon has quit [Ping timeout: 246 seconds]
LunaVorax has joined #qi-hardware
LunaVorax has quit [Ping timeout: 276 seconds]
lekernel has joined #qi-hardware
GNUtoo has joined #qi-hardware
alexander has joined #qi-hardware
alexander has quit [Read error: Connection reset by peer]
alexander has joined #qi-hardware
alexander is now known as Guest99112
Guest99112 has quit [Read error: Connection reset by peer]
alexander_ has joined #qi-hardware
LunaVorax has joined #qi-hardware
<LunaVorax>
Hi
<alexander_>
hi
<alexander_>
its me again driff name
jekhor has quit [Ping timeout: 256 seconds]
<wpwrak>
xiangfu: heya !
paul_boddie has joined #qi-hardware
kristoffer has joined #qi-hardware
xiangfu has quit [Ping timeout: 252 seconds]
<paul_boddie>
Hello! I was looking at USB gadget drivers on the NanoNote, and it looks like you can't use the combination drivers because of limitations on the number of endpoints in the jz4740 code. Is this a hardware thing?
urandom__ has joined #qi-hardware
<paul_boddie>
I get -ENODEV when the Ethernet-plus-serial gadget tries to bind the serial endpoint, or something like that.
<paul_boddie>
This being in drivers/usb/gadget/f_acm.c, if I recall correctly. The kernel log reports "can't bind" and a status of -19 (-ENODEV). Anyway, that's my report on the matter for Internet users of the future. :-)
<paul_boddie>
I also found that the jz4740 code won't compile with debugging enabled because it appears to think DEBUG expands to a function call. I may try and make a patch for that, but debugging practices in the kernel seem to be somewhat chaotic.
xiangfu has joined #qi-hardware
woakas has joined #qi-hardware
<lindi->
paul_boddie: usb host hardware has limits yes
xiangfu has quit [Ping timeout: 276 seconds]
<mth>
lindi-: the gadget driver uses the USB device controller, not the USB host controller
<paul_boddie>
I found that g_ether and g_serial worked fine on their own. There appear to be other drivers that might allow the USB port to work with different "protocols", but I'm not sure what their limitations are.
<mth>
and I think the UDC driver has more limitations than the hardware does
<lindi->
mth: ok but that shares the endpoint buffers of the host controller?
<mth>
afaik the two controllers are completely separate
<lindi->
usually they are on the same chip
<lindi->
really?
jekhor has joined #qi-hardware
<mth>
not 100% sure, but I've never read anything about shared buffer space
<mth>
larsc might know more about this
<paul_boddie>
In any case, I can live with one or the other, although it doesn't appear possible to build multiple gadgets in the same kernel build and dynamically choose between them, so I suspect that there may be some architectural limitations in the kernel, too. Or maybe they don't anticipate anyone doing that.
<mth>
you could build the gadgets as modules and load/unload them that way, I guess
<mth>
paul_boddie: if you know of a way to make cdcether work reliably with Windows on the host, I'd like to hear about it
<paul_boddie>
Still seems a bit weird that you can only choose one in the menuconfig, though, and that you have combination gadgets. Maybe changing the "personality" of endpoints is seen as being bad behaviour.
<mth>
it works out of the box with Linux and Mac OS X, but not with Windows
<paul_boddie>
Fortunately, I don't have to use Windows. I remember trying to get IRDA networking running between Linux and Windows, but Microsoft had done their usual protocol extension stuff, and although it was documented that Windows might send bad stuff and that you could work around it, the Linux driver just refused to talk to it by default.
kilae_ has joined #qi-hardware
kilae has quit [Ping timeout: 276 seconds]
xiangfu has joined #qi-hardware
<xiangfu>
wpwrak, Hi.
<xiangfu>
(network problem)
rejon has joined #qi-hardware
xiangfu has quit [Ping timeout: 244 seconds]
<whitequark>
paul_boddie: you're trying to build g_serial and g_ether as modules and switch between them, right?
<larsc>
mth: do the new pwm patches look good to you?
<whitequark>
I've tried that on a different board with the almost same processor (Jz4725B, has exactly same UDC IP core), and it worked for me
<paul_boddie>
whitequark: I actually didn't compile them as modules, but it's encouraging to know that you can have them both and switch them in and out on the same kernel.
<paul_boddie>
I just wondered why they'd bother to have combination modules, but I suppose it has something to do with simultaneously advertising both kinds of service.
jluis|work has quit [Remote host closed the connection]
<whitequark>
paul_boddie: ah, simple then
<whitequark>
when you compile both in the kernel, you're stating that you want to use them simultaneously
<whitequark>
and the jz4740 UDC doesn't have enough endpoints for that
<paul_boddie>
I thought so. Thanks for confirming that!
<whitequark>
OTOH you might have some success with CDC-ECM (as opposed to CDC Ethernet), as the former is less complex
<whitequark>
it was developed for exactly this application
<whitequark>
note that CDC-ECM doesn't work on Windows AFAIK
<paul_boddie>
I was just using the usual CDC Ethernet driver, which is g_ether, I think.
<whitequark>
yeah
<whitequark>
it's more complex than ECM one
<paul_boddie>
I'm talking to a Linux host, so I guess I don't have the same interoperability problems as others have.
<paul_boddie>
I'm actually looking to play a bit with the USBIP driver, just for fun.
<whitequark>
USBIP? what's that?
<paul_boddie>
USB over TCP/IP. It's in the staging drivers directory.
<paul_boddie>
The TCP/IP part seems overkill to me. I may look into using plain file descriptors rather than sockets.
jluis|work has joined #qi-hardware
<mth>
larsc: I didn't do a thorough review, but reading the patches I think he changed everything as we discussed
<whitequark>
paul_boddie: erm, so what do you want to do exactly? usb over tcpip over usb?
<mth>
whitequark: cdcether doesn't work with Windows either, in practice
<paul_boddie>
USB over something, perhaps not TCP/IP, which would use USB as the underlying transport. Just for fun, as I said. :-)
<paul_boddie>
USBIP provides a host interface. That's the crucial distinction.
<whitequark>
mth: ah, maybe. I didn't really work on Windows for 5 years or so
<mth>
I had two friends with Windows netbooks try to connect to the A320 and neither of them succeeded even after trying various things for over an hour
xiangfu has joined #qi-hardware
<alexander_>
I am working on a decent cl countdown script. it plays sounds using "aplay /somesound 2>/dev/null &". If a sound is still playing when the next one starts. the next one does not play. any advice? this works on my desktop
<larsc>
make sure the dmix plugin is enabled and used
<alexander_>
were is that set?
<larsc>
aplay -D, but in theory it should be the default if it is enabled
<alexander_>
thanks
<larsc>
what does aplay -L list?
<alexander_>
nope don't work.
<alexander_>
aplay -L lists one card can post the full info
kilae has joined #qi-hardware
<alexander_>
default:CARD=LB60
<alexander_>
QI LB60
kilae_ has quit [Ping timeout: 268 seconds]
<alexander_>
I have had this problem before on puppy. I think it was solved by telling it to use alsa not oss
<larsc>
aplay will use alsa, I'm not even sure there is oss support on the nanonote
<wpwrak>
in fact, the "ub" script tries to turn it off in case it's there :)
<wpwrak>
"ub" tries to turn off at86rf230 and the mmc driver, so that nothing in the kernel uses the 8:10 card slot
<xiangfu>
when I run 'echo spi*.0 >unbind' . I got no such device. is that normal?
<wpwrak>
yes, that's okay
kilae_ has joined #qi-hardware
<xiangfu>
don't want broken anything... :-)
<wpwrak>
actually .. the "no device" is a bit surprising. it suggests a partial initialization. but okay, if there's no spi under the at86rf230, then that's fine.
kilae has quit [Ping timeout: 246 seconds]
<wpwrak>
very important: when you do the "make ... on", the programmer must be disconnected. only connect it after the "make ... on"
<xiangfu>
yes.
<wpwrak>
the ben is extremely fragile when it comes to inrush current on the 8:10 card port. even a small external capacitative load can crash it.
<xiangfu>
I do that exactly follow readme. when 'poke 0x10010318 4' it crash nanonote.
<wpwrak>
hmm. do you have another ben you could try ? maybe this one is even more sensitive than they usually are
<xiangfu>
trying another nanonote
<wpwrak>
solved the ATtiny167.conf mystery. the next time you pull, ATtiny167.conf will be deleted. run make -C common to get it back
<xiangfu>
another ben success on 'make -C pgm/fw prog HOST=root@ben'
<xiangfu>
wpwrak, (ATtiny167.conf) got it.
<wpwrak>
(success) excellent ! :)
<xiangfu>
wpwrak, for reflash the bootload. I have to reboot and setup them again right?
<xiangfu>
can I reflash bootload right after reflash programmer?
<wpwrak>
yes, you can do everything in the same session
<wpwrak>
the ben should be able to stay up very long. the main reasons why you may have to restart it are some short-circuit when inserting a board in the programmer (shouldn't happen very often since the fixture already guides the board) or when power is turned off by accident and you aren't quick enough to turn it back on
<xiangfu>
wpwrak, after reflash. the led blinking very fast. after led walk. is that normal?
<xiangfu>
I cannot see if it display image correct. :-)
<xiangfu>
I cannot figure out if it display image correct.
<wpwrak>
hmm. after the led walk, the application should be in standby mode and there should be no led activity
<wpwrak>
you can get some weird behaviour if the power source is weak. try this:
<wpwrak>
connect usb, make -C fw/app flash
<wpwrak>
leave usb still connected. afther the "make ... flash", the boot loader jumps to the application. pressing the button should then wake things up.
<xiangfu>
when I plug usb.
<xiangfu>
the 1~2 led on.
<xiangfu>
then I run the make -C fw/app flash
<xiangfu>
output looks normal.
<xiangfu>
then the device start to walk led.
<xiangfu>
after walk led.
<xiangfu>
half of the leds blinking very fast.
<wpwrak>
hmm, that's strange
<xiangfu>
half leds I mean: 1, 3, 5, 7, 9 .. is blinking.
<wpwrak>
that sounds like a power supply issue
<xiangfu>
2, 4, 6, 8,... are off.
<wpwrak>
also, when the "make ... flash" finishes, the device should go dark
<wpwrak>
did you pull the latest versions of everything ?
<xiangfu>
yes. I think so.
<xiangfu>
let me try again.
<wpwrak>
also please make sure the avrdude run really succeeded. avrdude prints a lot of stuff and it's easy to overlook an error. if it says that it verified the efuse ("avrdude: 1 bytes of efuse verified"), then everything is okay
<xiangfu>
this time seems right.
<xiangfu>
last time I plug in the 'programmer'. none of the leds is light.
<xiangfu>
not. the yellow led is light.
<xiangfu>
s/not/now
<qi-bot>
xiangfu meant: "now. the yellow led is light."
<wpwrak>
no lights in the programmer would be odd indeed :)
<xiangfu>
reflashing..
<wpwrak>
perhaps avrdude didn't even detect the device and never changed the boot loader. that would explain weird behaviour since the boot loader i had flashed originally is not compatible with the current application. (they share some interrupt handling, and that has changed)
rejon has quit [Remote host closed the connection]
<xiangfu>
wpwrak, ok.
<xiangfu>
you update the avrdude to 5.11.1
<xiangfu>
I am still with 5.10.
<xiangfu>
updating..
<wpwrak>
you need the latest versions of all the patches from ben-blinkenlights. there are things the regular avrdude or avrdude 5.10 with older patches can't do. e.g., multiple configuration files
<xiangfu>
wpwrak, README 123. there is a typo.
<xiangfu>
fw/app/flash --> fw/app flash
<wpwrak>
fixed. thanks !
<alexander_>
How the heck do you temporary change the console so ones text fills the screen? fonts don't look like the way. what about changing the resolution?
<alexander_>
The aim is full screen countdown.
emeb has joined #qi-hardware
<wpwrak>
xiangfu: i just noticed that the cap sensor may be unreliable when on battery power. on usb power, it should be fine, though. in case of persistent trouble, you can try leaving off the top of the case and touching the sensor directly.
<xiangfu>
wpwrak, great. I can see the smile by waving the device.
<wpwrak>
yeah ! :)
<wpwrak>
image selection (the 2nd menu item) should also work. so you can pick the vampire or the ufo.
<alexander_>
oh to use the script # decentclcountdown 00:01:00
<alexander_>
# decentclcountdown 00:01:05
<paul_boddie>
alexander_: What are you using to show the numbers? The console?
<alexander_>
yep
<alexander_>
bash
<alexander_>
printf
<paul_boddie>
If you want more control, you could use something that accesses the framebuffer. SDL seems to work quite well if the framebuffer is available.
<alexander_>
I know but thats a lot to lean about. I didn't think it would be so hard to have a huge font size. somehow. Its the last hurdle. the rest is easier improvements.
<xiangfu>
wpwrak, it like I tap once. the image change once.
<xiangfu>
wpwrak, the image selection under 'menu' not working here.
<paul_boddie>
You could use pygame if you don't want to write stuff in a systems programming language. :-)
<alexander_>
gets close
<wpwrak>
xiangfu: if you tap once and the image changes, then you're in the image selection
<xiangfu>
wpwrak, ok. great.
<wpwrak>
xiangfu: you have, in this order: run, image selection, image speed / width, and run endlessly
<wpwrak>
xiangfu: image speed isn't implemented yet. all the rest should work.
<xiangfu>
wpwrak, ok. got it. trying endless.
<xiangfu>
wpwrak, I can adjust the width by waving slow or fast. :-D
<wpwrak>
yes, manual speed control ;-)
<alexander_>
I quite like bash maybe on year I'll dabble in python but that would be need more days I don't have currently in less I need to dabble for my biz
<alexander_>
on =one
<xiangfu>
wpwrak, how long is the battery life? if I run under endless mode?
<wpwrak>
i haven't tried it yet. i would estimate about 5-10 hours. also depends on the image.
<paul_boddie>
alexander_: You can get a lot done in shell script, certainly.
<xiangfu>
wpwrak, got it.
<alexander_>
I know. just go on the puppy linux forums
<alexander_>
pail_boddie: Ding! I should ask on the puppy forum