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
cladamw has joined #qi-hardware
xiangfu has joined #qi-hardware
orson_zhai has joined #qi-hardware
wolfspraul has joined #qi-hardware
<unclouded> xiangfu: is there any source material for the Ben character printed on to outside of the NanoNote case?
orson_zhai has quit [#qi-hardware]
<xiangfu> unclouded, yes. I also try to find out that one. then will let you know.
<unclouded> xiangfu: thanks. So is the character I used slightly different then?
<xiangfu> unclouded, it's different.
orson_zhai has joined #qi-hardware
cladamw has joined #qi-hardware
jekhor has joined #qi-hardware
panda|x201 has joined #qi-hardware
jyfl987 has joined #qi-hardware
<jyfl987> xiangfu: ftp://ftp.ingenic.cn/3sw/01linux/01loader/u-boot/u-boot-1.1.6-jz-20110719-r1728-add-jz4770.patch.bz2
<xiangfu> jyfl987, wow. that u-boot-1.1.6 patch
<jyfl987> xiangfu: so it could be used for xburst-boot?
<xiangfu> what you mean?
<xiangfu> xburst-tools
<jyfl987> yep its xburst-tools
<jyfl987> xiangfu: i see someone are trying to port debian on ainol novo7(mips edition)
<xiangfu> jyfl987, we have the jz4770 usbboot source code. sent by someone work for Ingenic.
<pabs3> jyfl987: do you have a link about that?
<jyfl987> pabs3: do you mean what i said about debian port?
<xiangfu> pabs3, it's under 'debian-mips@lists.debian.org'
<jyfl987> xiangfu: got it
<pabs3> jyfl987: yeah
<jyfl987> lists.debian.org/debian-mips/2012/02/msg00014.html
<jyfl987> xiangfu: this guys's destination is closed to mine :]
<xiangfu> jyfl987, I have replied that email thread :)
<jyfl987> xiangfu: just saw that.
<jyfl987> xiangfu: and i hope those ac100 hacker can give help, i have an ac100 which have ubuntu installed,
<xiangfu> jyfl987, what is 'ac100'? I think all you need is JZ4770 program manual. :D
<whitequark> xiangfu: toshiba ac100
<whitequark> a very crappy ARM netbook, which is also very cheap
<jyfl987> whitequark: you got it
<whitequark> but the GPU is unsupported by Linux
<whitequark> which is why it's crappy
<whitequark> it is also proprietary and undoc'd
<xiangfu> :)
<jyfl987> whitequark: well it has tegra for linux
<jyfl987> whitequark: so its now have supported GPU :]
<whitequark> jyfl987: maybe you have other ac100? because a lot of people in my country bought it
<whitequark> and then found out that it won't actually work good
<whitequark> maybe there was a somewhat working blob
<whitequark> but no proper driver
<whitequark> I don't really remember, but there was a lot of disappointment over it and when I checked, it was awfully closed
<jyfl987> whitequark: you can go to #ac100 for help, i just use their ppa source at launchpad to get support
<whitequark> nah, I don't have one
<xiangfu> jyfl987, you needs jz4770 program manual. and maybe you can re-use the code from 'http://projects.qi-hardware.com/index.php/p/qi-kernel/'. there is v3.2 support for jz4740.
<jyfl987> xiangfu: how about SIMD? since ingenic use mips isa, its not a problem for me to learn that but SIMD is just another thing
<xiangfu> jyfl987, well. step by step. 1. maybe your jz4770 boot linux 2. then make it works better. :)
<xiangfu> s/maybe/make
<qi-bot> xiangfu meant: "jyfl987, well. step by step. 1. make your jz4770 boot linux 2. then make it works better. :)"
<jyfl987> xiangfu: ok
<jyfl987> xiangfu: just wonder if your kernel could use the kernel module provide by android kernel?
<whitequark> jyfl987: simd is not really documented but somewhat reverse engineered
<jyfl987> via ABI
<jyfl987> whitequark: can you show me a link?
<whitequark> jyfl987: sure, wait a few minutes
<whitequark> just fyi: in the mplayer port, they first assemble an accelerated .c codec to the asm source (.s)
<whitequark> then insert SIMD instructions with `.byte' and a weird AWK script
<jyfl987> whitequark: i have download that, if i got an exists document , i wont want to rework :]
<xiangfu> ( if your kernel could use the kernel module provide by android kernel) jyfl987 you mean the ben nanonote kernel?
<xiangfu> jyfl987, ben nanonote use upstream kernel. and some patches. you can find those patches at openwrt-xburst.git.
<xiangfu> jyfl987, sorry. I never look into android kernel.
<jyfl987> xiangfu: yes, i mean your qi-kernel
<jyfl987> xiangfu: if it could, then it wont need the source code for touch screen mcu driver
<jyfl987> xiangfu: just for my target, :] , i know its unacceptable for you
<whitequark> jyfl987: http://www.gp32x.com/board/index.php?/topic/50216-jzsimd-mxu-instructions-list/
<whitequark> this
<jyfl987> whitequark: aha, its a forth?
<jyfl987> i love forth system
<whitequark> jyfl987: er, I think that's some unrelated example code
<jyfl987> whitequark: thanks very much
<whitequark> the CPU is very certainly not a forth machine ;)
<jyfl987> whitequark: yes, maybe we could got a try of chunk moore's green array :]
* jyfl987 afk
Ayla has joined #qi-hardware
Ayla has joined #qi-hardware
Ayla has joined #qi-hardware
<qi-bot> [commit] Xiangfu: m1 patches: add fix-vga-vsync-pulses.patch (master) http://qi-hw.com/p/wernermisc/91da747
<xiangfu> wpwrak, I git push my commit on video parameters. :)
DocScrutinizer has joined #qi-hardware
mstevens has joined #qi-hardware
jivs has joined #qi-hardware
zedstar has joined #qi-hardware
antoniodariush has joined #qi-hardware
<xiangfu> have any idea on test plan of Milkymist One: http://en.qi-hardware.com/wiki/Milkymist_One_Firmware#Test_Plan ?
rejon has joined #qi-hardware
jekhor has joined #qi-hardware
<wolfspraul> xiangfu: nice, test plan! :-)
<wolfspraul> that's my only idea so far
<wolfspraul> :-)
<wolfspraul> TEST PLAN - YEAH!
<wpwrak> (usb issues) lemme write a post ...
ab5tract has joined #qi-hardware
Ayla has joined #qi-hardware
GNUtoo|laptop has joined #qi-hardware
T44 has joined #qi-hardware
<T44> hi
<T44> xiangfu: zear just told me that you might be able to help me, i am looking for someone that can read chinese
<T44> just a few words
<T44> from a schematic design
<xiangfu> yes
<T44> not sure if there is anything helpful
<T44> google translate helps me through various forum threads, but it cant help with pictures :)
<xiangfu> still loading the picture.
<zear> T44, it's relatively easy to transcribe the characters
<zear> the key is to count the number of strokes in each character and then look in lists of characters with that number of strokes
<xiangfu> left top (本图纸仅共参考，与实际电路可能略有不同) This drawing is only a reference, may be slightly different with the product.
<zear> although it's probably easier for japanese where they use only ~10 000 kanji, so the lists are relatively small
<T44> xiangfu: heh, actually already figured as much, the schematic doesnt exactly match the device :)
<xiangfu> right(保持开关) switch
<xiangfu> right(蜂鸣器示意图) the buzzer
<T44> aaah, thats what the mystery device is :)
<T44> that part didnt make much sense
<viric> xiangfu: what terminal emulator do you use in your workstation?
<viric> I wonder with what font
<DocScrutinizer51> mhm, panasonic.eu adverises mobile phone with 5730 modem chip
<DocScrutinizer51> might actually be semi-interewsting at least for me
<xiangfu> bottom(金属圈及触片示意图) Metal ring and the contacts film
<xiangfu> viric, gnome-terminal. but I am use the xchat.
<DocScrutinizer51> *allegedly* I couldn't flash any sw I build here locally to any MP device
<T44> right... thanks
<xiangfu> viric, font. I am use a Chinese font. :)
<viric> xiangfu: ah, do you use antialiased fonts in the terminal?
<T44> that wasnt very useful unfortunately :)
<DocScrutinizer51> still I could know what the modem is *actually* doing
<T44> xiangfu: thanks for your help, guess i'll just have to try to understand the rest of the schematic :)
<xiangfu> viric, I am use a free Chinese font: (http://wenq.org/) seems there is no english page. included by most linux system.
<T44> its a very confusing design
<xiangfu> viric, ( antialiased fonts) what this mean?
jluis has joined #qi-hardware
<viric> xiangfu: not only with foreground and background color, but also with pixels within the range
<xiangfu> T44 understand the rest of the schematic. yes. :)
<DocScrutinizer51> anybody interested in the precise URL?
<whitequark> DocScrutinizer51: what could I (or any other hw hacker) do with that phone?
<whitequark> it's tivoized anyway isn't it?
<DocScrutinizer51> NFC
<T44> bye
<DocScrutinizer51> afk for 60s
T44 has quit ["Leaving"]
<whitequark> NFC as in "near field communication"?
<DocScrutinizer51> back
<wpwrak> does NFC have any use outside marketing ? ;-)
<wpwrak> well, marketing and horror
<xiangfu> viric, I think my is "Anti-Aliased" font
<xiangfu> s/my/mine
<qi-bot> xiangfu meant: "viric, I think mine is "Anti-Aliased" font"
<viric> :) ok
<DocScrutinizer51> NoF*Clue
<viric> (I dislike antialiased glyphs for terminals)
<wpwrak> as in companies proposing some very scary lose-your-money-fast (codename "payment") systems
<wpwrak> DocScrutinizer: heh ;-)
<DocScrutinizer51> ~dict tivoize
<whitequark> DocScrutinizer51: bootloader which checks rsa signature
<whitequark> or: the great strawman of gpl3
<xiangfu> viric, I guess wpwrak is using "Non Anti-Aliased" font :-)
<DocScrutinizer51> actually has NFC ;-P
<viric> xiangfu: why would he?
<wpwrak> xiangfu: yeah. mainly X11 fonts 7x14 and 6x10 ;-)
<xiangfu> I saw his screenshot only.
<xiangfu> s/only/once
<qi-bot> xiangfu meant: "I saw his screenshot once. "
wolfspraul has joined #qi-hardware
<whitequark> DocScrutinizer51: as you're now into that modem stuff, can you enlighten me...
<whitequark> I ran `strings' (and IDA, but that was less interesting) on modem firmware, and it looks like it's some 20 year old codebase from ten different companies including stericsson, siemens, someone bought by intel and more
<whitequark> all loosely screwed together and patched three times in a row
<whitequark> (on Samsung Galaxy SII modem fw)
<DocScrutinizer51> ooops 5780 inside, not 5730
<viric> xiangfu: ah ok :)
<viric> DocScrutinizer51: what's good in a 5730?
<viric> or 5780
<DocScrutinizer51> the fact that I know it 'from inside' :)
<viric> ahh
<DocScrutinizer51> actually I'm the one working on the tickets against this modem here
wolfspraul has joined #qi-hardware
ab5tract has joined #qi-hardware
rejon has joined #qi-hardware
Ayla has joined #qi-hardware
LunaVorax has joined #qi-hardware
LunaVorax has joined #qi-hardware
wolfspra1l has joined #qi-hardware
<jivs> Hi
<rz2k> whitequark: you and grindars published any info about that coding horror on #xda-devs or #cyanogenmod channels/forums? wonder if anyone did same to sgs2 modem.
<jivs> trying to get dirtpan working with the latest qi-image
<jivs> the izcoordinator seems to run fine, but when i run iz assoc with another ben, there is no resonse
<jivs> can anyone here plz help to debug the problem
<wpwrak> does dmesg reveal anything ?
<jivs> it doesn;t load spi_atben.ko, so i am manually doing insmod
<jivs> after that it says spi_atben is ready for mischief
<jivs> is there anything else i could check
<wpwrak> hmm, with spi_atben not loaded, you could check whether communication works at all - by using the tools from ben-wpan
<jivs> http://pastebin.com/xTsLagaf :-result of lsmod after doing insmod
<wpwrak> that looks reasonable
<wpwrak> (tools) e.g., atrf-txrx
rejon has joined #qi-hardware
<jivs> ok
wolfspraul has joined #qi-hardware
<jivs> how imp. are kmod-fakehard and kmod-fakelb for atben to work?
<jivs> iz listphy doesn;t show any interface w/o these packages
<wpwrak> jivs: i think they don't matter at all
<wpwrak> oh, are these devices that worked before ? or are they new ones ? (the atbens and/or the bens)
<jivs> and shows wpan-phy0 and wpan-phy1 with those packages
<jivs> the atbens and ben work well when we use the dirtpan compiled separately in a kernel
<jivs> now we are trying to get it working with new image
<jivs> silly question, is iz required at all for dirtpan to work now?
<wpwrak> ah, then there's no point in testing with atrf-txrx. sorry, didn't realize what you were doing
<jivs> okay
<wpwrak> yes, you still need the IEEE 802.15.4 link layer
<jivs> okay
<jivs> could it be any thing missing on kernel or any package missing?
<wpwrak> don't know. nothing obvious comes to mind
<wpwrak> you seem to have everything i can think of
<jivs> has anyone ever got two atben working with the new qi image?
<jivs> the izcoordinator seems to run fine and listen for clients but clients never recieved any short address
<wpwrak> does the system have an MMC driver running ? if yes, you'd have to disable it before doing anything with WPAN
<jivs> i tried to run izcoordinator on ben with new image and iz assoc on ben with old kernel, doesn;t work
<jivs> hmm
<jivs> how can i check that?
<jivs> i have kmod-mmc_3.0-1_xburst.ipk kmod-mmc-spi_3.0-1_xburst.ipk installed on ben now
<wpwrak> echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
<wpwrak> should disable it
<wpwrak> also ks8995 looks suspicious
<jivs> does it give any message?
<wpwrak> and the at86rf230 driver is compiled as a module ? if yes, it seems that you didn't load it. but then i don't understand where your wpan-phy0 comes from
<jivs> wpan-phy0 might be coming from fakehard as well
<wpwrak> (mmc driver) hmm yes, it should spit out some errors because it can't figure out what to do with atben
<jivs> didn;t give any error for me
<wpwrak> i'd get rid of fakehard. it can only make things worse :)
<jivs> at86rf230 driver will be displayed on lsmod?
<wpwrak> assuming it's a module, yes. does dmesg | grep -i rf23 show anything ?
<jivs> i doubt i have at86rf230
<jivs> nothing
<wpwrak> then there's very little reason for atben to do more than sit there, looking pretty ;-)
<wpwrak> but you also have to get rid of the conflicting drivers. anything else that uses MMC will clash.
urandom__ has joined #qi-hardware
<jivs> lsmod has mmc_spi
<wpwrak> perhaps just unloading the critters will make them clean up properly
<jivs> do you thing that might be an issue?
<antoniodariush> wpwrak, do you have a list of the minimum required packages that we need to select from the toolchain to get it working
<wpwrak> mmc_spi is a little strange. not sure what it tries to do. i'd get rid of it.
<jivs> okay
<wpwrak> antoniodariush: i don't how things map into packages. i always build things from scratch, without going though openwrt
<antoniodariush> we used to do that as well but we'd like to avoid that and get it working out of the box
<wpwrak> (mmc_spi) that's an MMC driver that works on top of SPI. what's weird about it is that we have a perfectly good MMC controller. do if it uses the same pins, it would be a grossly inefficient alternative to the proper controller (and driver). if it uses other pins, i'd kinda wonder which.
<wpwrak> (mmc_spi) so that's another item where nothing good can come from having it
<jivs> i am recompiling w/o these packages now
<jivs> the at86rf230 driver is selected on the toolchain
<wpwrak> too bad xiangfu is probably asleep now. he must have tested the packaging and have a working sequence.
<jivs> but i am not sure if it is being build/loaded properly
<wpwrak> ks8995 is that sdio-wlan device, right ? do you actually have that ? if not, one more item to get rid of
<jivs> no we dont use that
<wpwrak> okay. so trading all the devices that don't make sense for the one that does ought to improve the situation :)
<jivs> :-)
<wpwrak> i don't know if there are internal dependencies in the openwrt build process that would knock out at86rf230. chances are that it's just not loaded
emeb has joined #qi-hardware
<jivs> is spi_gpio is needed?
zenlunatic has joined #qi-hardware
<wpwrak> sholdn't be. atben talks to the ports directly
<wpwrak> well, spi_atben
<wpwrak> ah yes, that's another driver that's missing
<jivs> ok
kilae has joined #qi-hardware
<jivs> [ 561.980000] at86rf230: probe of spi32766.0 failed with error -16
<jivs> actually when we are doing insmod on at86rf230.ko, it is giving that error
<jivs> hints anything?
panda|x201 has joined #qi-hardware
antoniodariush has joined #qi-hardware
<wpwrak> that's EBUSY. perhaps something else is in the way ?
<jivs> got rid of that error with echo jz470-mmc...
<jivs> testing further now
<jivs> yeh it works now
<jivs> got short address from coordinator
<jivs> thanks wpwrak
<jivs> will test dirtpan now
<wpwrak> whee ! :)
<jivs> thanks.. :-)
antgreen has joined #qi-hardware
<wpwrak> so it all works now ?
<antoniodariush> wpwrak, so far so good we only have a problem on the dirtpan now
<antoniodariush> "/dev/net/tun: No such file or directory"
Ayla has joined #qi-hardware
jekhor has joined #qi-hardware
Ayla has joined #qi-hardware
kuribas has joined #qi-hardware
zedstar has joined #qi-hardware
zedstar has joined #qi-hardware
uwe_mobile has joined #qi-hardware
mstevens has joined #qi-hardware
jekhor has joined #qi-hardware
abushcrafterforg has joined #qi-hardware
abushcrafterforg has joined #qi-hardware
* zenlunatic just got his BNN... about to unbox
<zenlunatic> is the screen supposed to be a little flickery?
<viric> zenlunatic: not that I remember. but maybe my retina has a longer integration time
<viric> talking about flickering...
<viric> These christmas, the governmet put the street decoration lights a lot using LEDs
<viric> which had such a power supply, that were lighting only half of the 50Hz AC cycle
<viric> and a long street blinking at 50Hz flashes instead of 100Hz was quite nocieable
<viric> noticeable
<viric> (I exposed the opposite way I was experiencing and deducing the situation)
<rz2k> lol
Artyom has joined #qi-hardware
<zenlunatic> seems to be a driver problem
<zenlunatic> cool... wheezy sees it
Ayla has joined #qi-hardware
LunaVorax has joined #qi-hardware
<DocScrutinizer51> whitequark: I have no idea what Samsung flashes to the modem, but I dwefinitely not seen such crap you mentionee, anywhere in gthe image I build every day
<DocScrutinizer51> whitequark: maybe OSE has some special curls for Siemens etc, and this might show up in a binary
<DocScrutinizer51> whitequark: also are you sure you've not scanned the APE stuff Samsung added? you know, I'm just talking about modem
unclouded has joined #qi-hardware
B_Lizzard has joined #qi-hardware
abushcrafterforg has joined #qi-hardware
jekhor has joined #qi-hardware
fossrox has joined #qi-hardware
urandom__ has joined #qi-hardware
LunaVorax has joined #qi-hardware
wolfspraul has joined #qi-hardware
wolfspraul has joined #qi-hardware