#qi-hardware IRC log for Thursday, 2010-11-04

kyakxiangfu: by switching to upstream backfire, we also switched back to uClibc-0.9.30.1, is it right?05:05
xiangfukyak: yes05:05
kyakwhich means there are problems with Qt apps..05:07
xiangfukyak: just when Qt Apps exit.05:14
xiangfu0.9.32 make more app not working then 0.9.30 on Qt :)05:15
xiangfurecently I read the openwrt mail. the 0.9.30 is the only one well tested.05:15
xiangfuin openwrt05:15
B_Lizzardlarsc, is there any way softvol can be implemented in the kernel driver?07:28
B_LizzardHave the driver expose a a proper 0-100 limit to ALSA and process that internally07:29
B_LizzardI haven't had any success doing softvol in userspace and using dmix would be prohibitive07:29
kyakxiangfu: okay, i see07:57
larscB_Lizzard: nope08:04
B_Lizzard:(08:04
rafabartbes: hey.. I forgot to tell you, but lua is now on the repositoires of Muffinman10:35
kristianpauljuan64bits: hey11:07
kristianpaulor hola?11:07
juan64bitshola :)11:08
kristianpauljuan64bits: conoces alguna implementacion de un DSO que puedira adaptarse a SIE ?11:10
kristianpaulpor cierto sabes como va el proyecto del analizador logico de los estudiantes de la UIS?11:10
juan64bitsde DSO no conozco ... y del analizador lógico ni idea jejeje... en la unal también lo están haciendo pero no han adelantado mucho11:11
kristianpaul:-/11:12
kristianpaulsi algo me comento camargo..11:12
kristianpaulok11:12
kristianpauljuan64bits: vos conoces el funcamiento del ADC para SIE?11:12
kristianpaules que no he mirado mucho11:13
juan64bitssi, yo hice el ejemplo de ADC en QT que está en la wiki11:13
kristianpaulohh !11:13
kristianpaulpodrias apuntarme las partes claves para leer los datos de la FPGA?11:14
kristianpaules que compilar QT es un enredo, quisiera tener una version en C con SDL11:14
kristianpauljuan64bits: ya sabes que ya tenemos soportado SIE en Jlime ?11:14
kristianpaulcon el xcs3prog.. y el siggen11:14
kristianpaulfalta es el scop11:15
kristianpaullo bueno en jlime es que con el X podemos correr varias aplicaciones como gtkwave tal ves...11:15
juan64bitsah o, mm pues sería hacer el memorymap a la región 0x14000000, el periférico del ADC está de la posición 0 a la 2047, y se usan los cuatro primeros bytes para la configuración11:16
juan64bitshttp://en.qi-hardware.com/wiki/File:ADC.png11:17
juan64bitsel periférico era una prueba inicial y no tiene control de IRQ, esa sería el inconveniente11:17
kristianpaulno problema11:17
kristianpaulokmastarde intento hacer un printf u alog basico paracomprarbar que si puedo leer11:19
kristianpaulgracias juan64bits  !11:19
juan64bitsok.. cualquier cosa me preguntas11:19
kristianpaulok11:19
rafajuan64bits: kristianpaul : si qt4 es un requisito indispensable para sie/sakc yo puedo tratar de portarlo a jlime..11:21
kristianpaulrafa: pues hay varias apps ya en qt4 que no hepodido compilar11:22
kristianpaulalmenos que se crosscopile11:22
kristianpaulpero seria intesante poeder compilar cosas de qt4 en SIE11:23
kristianpaulque es lo interesante de jliem y sus 11000 paquetes11:24
kristianpauly no tener que crosscompilar cada rato11:24
kristianpaulclaro que empaquetar el softbasico como el siggen, el ejemplo del ADC  y el xcs3prog no es mala idea11:25
rafakristianpaul: wow.. no pense' que qt4 seria lo mas usado en mobile devices :P11:25
kristianpauljajaja11:25
rafakristianpaul: ya superamos los 16000 paquetes ;)11:25
kristianpaulohh11:25
kristianpauljuan64bits: vos usaste el qt creator para esos ejemplos??11:25
kristianpaulpor que eso si no creo se pueda correr en jlime ;-)11:26
juan64bitssi, qtcreator11:26
kristianpaulpor recursos y mouse..11:26
kristianpaulah11:26
kristianpaulbueno11:26
rafakristianpaul: pero porque no va a funcionar? (qt creator)11:26
kristianpaulpero es util si puediran compilar mas agilmente en la board juan64bits ?11:26
rafajuan64bits: son tus aplicaciones para la pantalla de la nanonote o sie?11:26
kristianpaulrafa: recursos mouse..11:26
kristianpaulrafa: es la misma11:26
rafakristianpaul: pero entonces?? no entiendo nada :(11:26
kristianpaulrafa: digo que ellos dise;an las apps en el qtcreator luego las pueden compilar en el SIE con Jlime11:27
rafakristianpaul: usan mouse en sie?11:27
juan64bits@rafa no entendí la pregunta jejeje11:27
kristianpaulno no11:27
kristianpaulrafa: qtcreator es un IdE para QT11:27
kristianpaulpara dise;ar apps11:27
rafajuan64bits: es que mis preguntas estan confusas porque soy yo el que no entiende :D11:27
rafakristianpaul: y les funcionan finalmente la aplicacion en openwrt en sie?11:28
kristianpaulrafa: yo creo si se pueden compilar apps de qt4 en SIE todo va bien11:28
kristianpaulrafa: si11:28
kristianpaulrafa: si en openwrt creo ya juan64bits maneja bien le cross compilado11:28
rafakristianpaul: y cross compilan con ese qtcreator?11:28
kristianpaulno se11:28
kristianpaulNO manejo QT11:29
kristianpaul:p11:29
rafajuan64bits: disenian las aplicaciones con qt creator.. y como las crosscompilan?11:29
kristianpauljuan64bits: comop compilas las appas para QT para SIE/Openqrt?11:29
juan64bitscon el QtCreator no crosscompilamos, aunque se puede. pero hay que dar más vueltas para configurarlo11:29
rafajuan64bits: como manejan qt en openwrt?.. tienen una libreria qt sobre el framebuffer?11:29
kristianpaulrafa: me imagino usan el toolchgain de ope nwrt11:29
kristianpaulexport blabla QT aqui y alla?11:29
kristianpaulqmake !11:30
kristianpaulno?11:30
juan64bitsaja qmake, pero con el qmake.conf para openwrt11:30
juan64bitsy el respectivo toolchain11:30
kristianpaultienes  manual sobre eso??11:30
kristianpaulo doc en la wiki?>11:30
juan64bitsy si es sobre framebuffer... linuxfb o directfb11:30
kristianpaulrafa: probe los binarios de los ejemplos en QT para openwrt y no me ejecutaron en jliem.. :/11:31
rafakristianpaul: okey.. me podes dar un tar.gz de una aplicacion qt de esas ?11:32
juan64bitsen la wiki estan las modificaciones al qmake.conf para generaar el makefile correcto11:32
rafakristianpaul: (los fuentes)11:32
kristianpaulrafa: http://projects.qi-hardware.com/index.php/p/nn-usb-fpga/source/tree/master/Examples/ADC/Scope-QT-src11:33
kristianpaulese es lde sofware ADC para visualizar11:34
kristianpaulmas informacion con juan64bits ;-)11:34
juan64bits(Y)11:34
kristianpauljuan64bits: el refresco del ADC no se como pobre..11:35
kristianpaulse puede mejroar?11:35
kristianpaulno se es como**11:35
kristianpaulpor  eso pensasba en SDL11:35
kristianpaulno es que ODIE qt11:35
juan64bitsclaro que se puede mejorar11:35
juan64bitsese era un ejemplo para comprobar que esta funcioando todo bien en la placa11:36
kristianpauludes si usan ese ADC en SIE?11:36
kristianpaulhmm11:36
kristianpaul:p11:36
juan64bitsno jejeje, por ahora no ha tenido un uso "serio"11:36
kristianpaulya sabia..11:37
juan64bitssupongo que alguno de los proyectos de curso lo estarán usando11:37
kristianpaul;-)11:37
rafakristianpaul: I did git clone of the link you gave me. Now I got:12:48
rafabinaries   Examples             lua                 Software12:48
rafacourse     KICAD_design_files   ORCAD_design_files  u-boot_sakc12:48
rafaDatasheet  linux-2.6.32.7_sakc  plasma              xilinx_lib12:48
rafadocs       lm32                 sie_fs12:48
rafawhat should I try ? :P12:48
kristianpaulrafa: /nn-usb-fpga/Examples/ADC/Scope-QT-src13:03
aisaDoes the Yeeloong Notebook use the same processor as the Ben NanoNote?13:05
aisahttp://www.lemote.com/en/products/Notebook/2010/0310/112.html13:05
kristianpaulnope13:06
aisahow would I tell this?13:06
aisaI get confused by "MIPS"13:06
kristianpaulnot ge13:06
kristianpaulis like x8613:06
kristianpaulintel is not the only13:06
kristianpaulther is AMD too13:07
kristianpaulsame in MIPS13:07
kristianpaulletmeo uses Loongsoon processors13:07
aisawhat do you mean by not ge?13:07
kristianpaulnot get13:08
kristianpaulben nanonote uses Xburst13:09
kristianpaulbut i wonder if the Loongsoon follow MIPS arch at all13:09
larscyes, they even got a license from MIPS13:11
kristianpaulhmm yes13:22
kristianpauleven i think next cpus will run x86 instructions13:22
kristianpaulrafa: did wotk for you that folder?13:23
kristianpaul.13:52
rafakristianpaul: I have not tried yet, I am reading how qt works for different platforms and how to crosscompile using that13:53
rafakristianpaul: from that I am reading we have all the tools on repository to do that, but no sure to build on nn, I'm talking about crosscompile13:55
kristianpaulhmm13:55
kristianpaulis too hard got wt build env on jlime?13:55
rafammhÂ?13:56
rafa?13:56
rafawhat?13:56
rafasorry, I did not understand that13:57
rafakristianpaul: what did you mean?13:58
kristianpauli wanr type qmake14:00
kristianpauland got my ADC14:00
rafaso you already built?14:00
rafakristianpaul: btw, qmake just generates Makefiles to build14:03
rafakristianpaul: after that you need to run make to build14:03
kristianpaulajap14:05
kristianpaulhm14:05
kristianpaulso14:08
kristianpaulthere is QT build Envrioment avaliable for Jlime?14:09
kristianpaulis this the qt4-core package?14:09
rafakristianpaul: I have no idea.. trying to learn about that right now.. if you look for qt on repositories you will find around 300 packages. SO better I read a while about qt development :) (i am reaking nokia docs currently)14:37
kristianpaulo14:39
kristianpaulk14:39
Ornotermesis any one familiar with linux (software)sd-stack?15:10
viricWhere is tuxbrain, btw?15:20
viricI wonder, is anyone going to sell SIEs ?15:20
kristianpaulviric: seems is sold out for now15:32
kristianpauli hear SIEv3 is coming15:32
kristianpaulmay be juan64bits can tell more about next SIE version and next production date?15:33
juan64bitsthe design  v3 is in process.... carlos camargo know more about that ...15:35
juan64bitsabout date15:35
viricahh really out?15:38
viricimpressive :)15:38
viricand how much were v2?15:38
virichave them to be...mmmm   "encargados"?15:40
virickristianpaul: I know that word in Spanish and not in English.15:40
viricpues, hace falta encargarlos?15:40
kristianpaulno se si ya se pueda15:41
viricok15:53
kristianpauli dont know if is posible order SIE now15:55
B_Lizzardlarsc, did I ever mention that 2.6.36 doesn't give me console output on boot and shutdown other than the initial kernel messages?16:05
B_LizzardI think that also prevents stuff like psplash of running during boot16:07
larscB_Lizzard: thats probably just a config issue16:10
B_Lizzardcmdline seems OK... I'm using the config from projects.qi-hardware...16:11
B_LizzardLemme check16:11
B_LizzardWhich config option would that be?16:13
B_Lizzard:/16:13
B_LizzardHmmm, maybe it's not a kernel issue.16:14
B_LizzardYeah, probably not a kernel issue...16:26
B_LizzardWhat could it be?16:26
B_LizzardI see in cmdline that console is defined twice, one with tty0 and one with ttyS016:28
B_LizzardMaybe stuff is ending up in the serial console?16:28
larscif its in the cmdline twice it should end up on both consoles16:43
B_LizzardYou mentioned a kernel config that could be responsible?16:44
larscuff16:45
larschm, framebuffer console is enabled16:47
B_LizzardMaybe CONFIG_FB_VIRTUAL?16:53
larscno16:59
B_LizzardHmmm17:01
B_LizzardIt's not my sysvinit either17:07
B_LizzardI can't think of anything other than the kernel17:07
B_LizzardMost definately is the kernel, I'm getting messages from init with 2.6.34 and no messages with 2.6.3617:31
larscok17:34
wpwrakOrnotermes: i worked with it some time ago (~2 years)17:39
Ornotermeswpwrak: i was thinking of digging in a bit in it to see if it would be at all possible to make a cheap mcu of some kind emulate a block device over 4-bit MMC/SD (instead of using gpio), what do you think?17:42
wpwrakOrnotermes: hmm, if you can find an MCU with a built-in SD device controller. i've never seen such a thing, but i guess it must exist somewhere17:44
wpwrakOrnotermes: i think it would be difficult to get the bus timing right just with software. maybe in 1 bit more, but i'm not even sure about this.17:45
Ornotermeswpwrak: i dont expect to find that, but since it is possible to use a cheap 8bit avr to bitbang usb with 1.5Mbit/s it soesent seem unlikely to work with SD either17:46
Ornotermespeople have done incredible things with simple hardware17:47
wpwrakhmm, it would depend on the ability to slow down the clock sufficiently17:48
Ornotermesi was thinking of looking a bit at old SD hardware17:49
wpwrakokay, low-speed SDIO is not too demanding. only 400 kHz, with 4 bit being optional. so it's 400-1600 kbps17:50
Ornotermesthe problem is SDIO, not all hardware supports it17:51
Ornotermesthere for i want to emulate a block device17:51
wpwrakinteresting idea ... :)17:51
wpwrakhmm, what's the problem with SDIO ? you'll probably need some driver for your peripheral anyway17:52
Ornotermesi think the spectec wifi cards works as block devices and there for don't require hardware with sdio17:52
wpwrakthat is, unless it's really just storage17:52
wpwrakreally ? that would be quite odd. possible but odd.17:52
wpwrakbut what problem are you trying to solve anyway ? on which host that's sd-capable but not sdio-capable do you want to use your peripheral ?17:53
Ornotermeswpwrak: i might be wron, but i think i heard/read something about wificards looking as block devices17:54
wpwrakah, found something. a complete sdio spec ;-) http://www.sandisk.com/Assets/File/OEM/Manuals/SD_SDIO_specsv1.pdf17:55
wejpthere are these special wifi sd cards that work in arbitrary devices using sd slots. those work just like storage devices, but "normal" wifi sd cards always use sdio17:55
Action: FrankBlues waves17:56
Ornotermeswpwrak: the problem is bens lack of expandability, and i rather put the load of bit banging on a external mcu rather than the cpu17:57
Ornotermesand a device that works on other hardware than just ben could be very useful not only for us17:58
wpwrakhmm, i see. not sure how efficient that would be, though. without sdio, you don't have interrupts. so you'd have to poll the card for events.17:59
Ornotermesand yes, some sort of driver would probably be needed, but it could even be a virtual fs that lets the software sun in usermode18:00
Ornotermeswpwrak: off course that is something worth taking under concideration but i still think it would be better than bitbanging things like spi from the sd-port, also it could give a whole buch of extra gpio18:03
wpwrakhmm, with caching and all that, you'd heavily depend on the host operating system's internals for this to work.18:03
Ornotermesdoes linux cache on block device level? i thought it cached on filesystem level?18:05
wpwrakwhat's nice about big-banging from the host is that you can make very simple and dumb boards. also, all the software sits on the host, so you don't need yet another cross-chain, knowledge about an MCU architecture, tools to flash the MCU, etc.18:05
wpwrakOrnotermes: linux caches on the block level. some file systems may have additional caches. e.g., msdos(fs) has a read cache for the FAT.18:07
Ornotermeswpwrak: the bad thing with bit-bang is that it takes more cpu time than the mmc-interface18:07
wpwrakyes, that's true18:07
Ornotermesi see, i thought it only cached on filesystem level because there is options like sync18:08
wpwrakof course, if you need to go from interrupt to polling, that may be even more expensive. but i could see a point in implementing SDIO with an MCU.18:08
wpwrak(sync) the file system can tell the buffer cache when it wants data to be committed to disk. (if it's that what you mean)18:09
Ornotermesmaybe it would be possible to have both even, mainly SDIO but failover to SD if there is no SDIO18:09
wpwraksure. there are a lot of possibilities :)18:10
Ornotermesany way, was thinking of trying some stuff on stm32 (if i get things working)18:13
Ornotermesand i think the linux source is a good way to get information18:13
wpwrakif you wan to implement an SD/SDIO device, the linux kernel isn't so helpful. you'll eventually have to look at it, because there will be bugs and it helps if you can catch things at a lower layer :)18:15
wpwrakwhat you need to understand are the SD and SDIO specs.18:15
Ornotermesyeah, it is atleast woth a shot18:16
wpwrakif you have a scope with at least 3 channels, that helps too. there's even an SDIO decoder in my TMC package.18:16
Ornotermesi trying to put my hands on this kind of card: http://hackaday.com/2010/10/12/arm-prototyping-on-the-cheap-with-stm32-discovery/18:16
wpwrak(channels) digital is sufficient. e.g., an MSO with 2 analog and some digital channels is fine. or some logic analyzer. unfortuntely, there are very very few PC LAs that are linux-friendly18:17
Ornotermesi also have a board since before with stm32 that i never have put to use (avr works too good with linux :P)18:17
Ornotermessadly i only have a cheap 2 channel scope18:18
Ornotermesbut i have a bus pirate18:18
Ornotermesbut that is probably too slow18:19
wpwrak(bus pirate) says up to 1 MHz logic analyzer. that shuold be enough for a low-speed SDIO card (400 kHz)18:21
Ornotermeswpwrak: sounds good18:23
Ornotermeswpwrak: i also got an idea how to slove the polling issue(if it works)18:24
Ornotermesif one would like to get the status and reads a status block, what if it instead of returning 0 would wait to return anything at all til there is something to report?18:28
steve|mfor all friends of awesome hacks: http://hackaday.com/2010/11/04/mac-se-reborn-as-a-server-and-mac-emulator/18:29
Ornotermeskind of a very long acces time18:29
Ornotermessteve|m: i saw it earlier today, it's a really cool project18:29
wpwrak(status block) hmm, but once you read it, it would be caches. also, if you don't respond, you get a timeout. so the host will think there's an i/o error.18:35
Ornotermesthe cache is ofc a problem again18:37
Ornotermesone could read new adresses all time but that would probably cache out everything else18:38
wpwrakyou would recycle cache entries, yes. also, there is readahead. so the file system may decide to read more than just one block, assuming you'll want the other blocks as well.18:40
Ornotermeshmmm, true18:41
lekernel(old mac) why do i find that boring...?19:03
wpwrakOrnotermes: an SDIO implementation with an MCU should be feasible. however, one problem is that you'll still have very tight timing if you bit-bang the I/Os. i.e., you couldn't do more than one timing-critical thing reliably in this device.19:05
steve|mlekernel: well, I like the linux framebuffer-via-usb thing most interesting :)19:06
steve|m*find19:06
wpwrakOrnotermes: i'm not sure how v-usb does it. i would suspect that it either had the same restriction or that it heavily relies on USB's built-in retransmission mechanism19:07
Ornotermeswpwrak: yes, i will try to find out how sd(io) select the clock speed19:09
wpwrakOrnotermes: if your MCU has DMA (or large FIFOs), you may be able to mitigate the timing issues, though.19:10
wpwrakOrnotermes: (clock speed) http://www.sdcard.org/developers/tech/sdio/sdio_spec/Simplified_SDIO_Card_Spec.pdf19:10
Ornotermesand i don't really know how v-usb does it, what i know is that it requires at least 12MHz to work and reads input on a hardware interupt pin19:11
wpwrakpages 29 and 3219:11
lekerneldoes what? (sorry didn't follow)19:12
Ornotermeslekernel: how v-usb handles usb bit banging19:13
lekernelhand crafted asm19:13
lekernelon avr all instructions execute in a fixed time, so all you have to do is some asm wizardry so that the bits are out at the right time19:14
wpwraklekernel: the question is: how do you get anything else done, besides USB communication ? there doesn't seem to be much tolerance, unless you accept that you may miss a transmission from time to time.19:16
lekernelinterrupts I guess19:18
lekernelno?19:18
Ornotermesstill, even if one use interupts it might take a buch of tics from triggering till the software get to check it19:19
lekernelno, the interrupt latency on AVR is low19:20
lekerneland aren't you able to use GPIO-triggered interrupts?19:20
lekernelie get an irq when some external pin changes value19:21
steve|mmy experience with v-usb is that it works quite reliable, even if a bunch of other interrupts are active (3 timers, TWI, SPI, etc.)19:21
Ornotermeslekernel: i don't relly know but what i read v-usb needs the highest dedicated interupt in use19:22
wpwraksteve|m: would be interesting if someone dug into it and figured out how many spare cycles it really has.19:22
wpwraksteve|m: or if it causes long "blackouts" during which interrupts are blocked19:23
wpwraksteve|m: e.g., can you make an interface for sustained SPI input to USB, without losing SPI data ?19:24
wpwraksteve|m: if yes, how many USB transmission do you lose ?19:24
wpwraksteve|m: and of course, up to which SPI clock rate ?19:24
lekernelyou could just use a ftdi-chip for that :)19:25
steve|mwpwrak: it worked fine for 200kHz I2C with an atmega168 @ 12MHz without any loss.. no data on spi19:25
Ornotermeswpwrak: most AVRs have hardware spi19:25
wpwraklekernel: so you're supporting chips that are largely undocumented ? :)19:26
lekernelthat or the AVR, it doesn't make much difference19:27
lekerneland the ftdi is faster and less work to get working19:27
wpwraksteve|m: I2C master, slave, or both ?19:27
steve|mwpwrak: master only19:28
wpwraklekernel: depends a lot on which FTDI and what you're trying to do. e.g., i got burned with the FT232 and bit-banging. the darn thing just doesn't work reliably.19:28
wpwraksteve|m: okay, that's not a challenge ;-)19:28
lekernelhttp://www.ll.mit.edu/publications/journal/pdf/vol14_no2/14_2subwavelength.pdf19:36
steve|min support of the FT2232 I have to say that it works fine as jtag adapter and supports odd baudrates :)19:36
wpwraksteve|m: as long as you can control the timing of anything besides the USB, you're fine. also, if the other thing gives you plenty of time to respond (e.g., enough to process a USB packet), you're fine too.19:36
steve|mwhat about one of those avrs with usb? Atmega8U2 or something19:37
Ornotermeswell, time to sleep19:37
Ornotermesgood night every one19:37
wpwraksteve|m: the FT2232 seems to be okay (except for the documentation situation, of course). but the FT232 seems to have issues. of course, without proper documentation, it's hard to tell where the problem is. maybe the chip itself is fine, just nobody has figured out how to use it correctly.19:38
wpwraksteve|m: V-USB was just an example for a timing-critical protocol implemented in software. what we're after is SDIO. also there, you need to respond quickly when the host sends a command.19:39
wpwraklekernel: how long until you'll have your own fab ? ;-)19:40
wpwrakand we have a new name for notches in corners. mousebite. this thing also exists in the cnc world, where you have to mill into a concave/inner corner if you want to fit something with a rectangular corner.19:45
steve|mwpwrak: ah okay.. quite some time ago I built a time-lapse cam and wanted to transfer the images via wifi.. one idea was to emulate an sd-card, but instead I went for a sd/usb dual card, toggling the "battery compartment open" switch to unmount the card, move the pics off, remount, take next picture etc.19:46
wpwrakone name i found there was "dogbone", referring to the orientation of the notch (you could have the same effect with an infinite number of different notches. "dogbone" is evenly placed beteen the two sides. "t-bone" would mill only into one, not the other, etc.). not sure if that's official, though.19:47
wpwraksteve|m: cool ! :) how did you implement the "SD card" ?19:48
steve|mwpwrak: well, I didn't implement it, I cheated an used something like that: http://cache.gizmodo.com/assets/resources/2006/06/buffalosd.jpg .. so I controlled the gpios of the cam with an avr and "unmounted" the card by toggling the battery compartment switch.. the card was connected via usb to a router with openwrt, where the card then was mounted etc.19:51
steve|mdidn't use it that long, but would have been interesting how long it'll take until the card fails :)19:52
steve|manyway, gotta go to bed.. n819:53
wpwrakheh, that's a crazy device :-)19:53
qi-bot[commit] Werner Almesberger: cntr/fw/include/cntr/usb-ids.h was never checked in. Oops ! http://qi-hw.com/p/ben-wpan/c28ab2c21:42
qi-bot[commit] Werner Almesberger: CAM setup update. Local relevance only. http://qi-hw.com/p/ben-wpan/0fc296021:42
qi-bot[commit] Werner Almesberger: Support design version 2 in the boot loader. http://qi-hw.com/p/ben-wpan/188bdb821:42
qi-bot[commit] Werner Almesberger: cntr/README update: name clarification and bugs list. http://qi-hw.com/p/ben-wpan/c91658e21:42
qi-bot[commit] Werner Almesberger: include/cntr/crc32.c was lost in the great involuntary purge. Add a dummy. http://qi-hw.com/p/ben-wpan/f5388ca21:42
qi-bot[commit] Werner Almesberger: Adapted firmware for V2 hardware. http://qi-hw.com/p/ben-wpan/4e568b021:42
qi-bot[commit] Werner Almesberger: Document that the input circuit does not reach the design frequency (3 MHz) yet. http://qi-hw.com/p/ben-wpan/8cb17bb21:42
qi-bot[commit] Werner Almesberger: Added burst counter mode to cntr tool, plus assorted small improvements. http://qi-hw.com/p/ben-wpan/df1706f21:42
qi-bot[commit] Werner Almesberger: cntr/README: cntr -r always returns an error, so we cannot use it with && http://qi-hw.com/p/ben-wpan/43f0bce21:42
qi-bot[commit] Juan64Bits: Adding M[0] M[1] configuration and fpga crystal http://qi-hw.com/p/xue/ca69a5422:14
qi-bot[commit] Mirko Vogt: add <http://downloads.qi-hardware.com/sources> as mirror for source http://qi-hw.com/p/openwrt-xburst/f88bb0123:26
--- Fri Nov 5 201000:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!