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
<whitequark>
pabs3: it may be a good x86 tool, but what's good for x86 isn't for a particular stack VM. so I think the integration would not be efficient.
<pabs3>
seems to load arm binaries fine
<whitequark>
interesting
<whitequark>
anyway... Currently Bokken is neither an hexadecimal editor nor a full featured disassembler YET, so it should not be used for deep code analysis or to try to modify files with it.
<whitequark>
I aim exactly for "deep code analysis", and I don't see a viable infrastructure for plugging that in
<pabs3>
its definitely not a mature project, interesting anyway
<whitequark>
yes, it's interesting, and I see that some parts of GUI are cleverly done
<whitequark>
but sadly not the codebase
<whitequark>
(decompiler) my thingy is already a complete disassembler, it can not assemble (because it's hard to define the operation of assembling an AS file), but it will quite certainly be a complete decompiler
<whitequark>
because some transformations require a full AST representation to be composed, and when you have full AST, you have just one step to get the source
<whitequark>
but I think I won't do any SWF decoding
<pabs3>
flasm does both assembly/disassembly btw. and the author has a non-free decompiler (to ActionScript): http://www.nowrap.de/flare.html
<whitequark>
as3 assembly isn't well-defined, and you don't have much use for it anyway, as it's a big pain to code directly for flash
<whitequark>
you need to look for variable, stack and scope compatibility at the very least
<whitequark>
so I don't see a use for it
<whitequark>
maybe that was different for AS2, but AS3 VM is rather stupid
<pabs3>
ok. anyway I guess this is pretty off-topic here :)
cladamw [cladamw!~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
guest_3423 [guest_3423!~nate@c-24-34-195-237.hsd1.ma.comcast.net] has joined #qi-hardware
<guest_3423>
I am starting a company and wondering where I can buy the best card readers (for debit/credit cards ) , and barcode scanners / makers
<guest_3423>
I.E what would be the popular companies that make these devices for whole sale
<guest_3423>
And how much would these devices typically cost.... A link /site/or phone number would be nice. Thanks for any help as I am new to xchat and somebody told me I should try an irc channel don't really know if this is the place , first time on irc
<guest_3423>
I am excited since this is going to be my first business.... so I don't want to get ripped of on this stuff
<guest_3423>
I have the building inspect or a OK it. And now the network and computer hardware is almost setup.... All I need is the cash registers , barcode readers/writters , and credit/debit card scanners. Anybody know sorry if I am being pushy I am excited
<pabs3>
this channel is for people making copyleft hardware, I don't think they make any of the hardware you are looking for, sorry: http://qi-hardware.com/
zear_ [zear_!~zear@h196n1-g-kt-a31.ias.bredband.telia.com] has joined #qi-hardware
zumbi_ [zumbi_!~zumbi@77.230.237.25] has joined #qi-hardware
rektide_ [rektide_!~rektide@deneb.eldergods.com] has joined #qi-hardware
marcan` [marcan`!marcan@marcansoft.com] has joined #qi-hardware
cladamwa [cladamwa!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #qi-hardware
orsonzhai [orsonzhai!~zhai@1.202.15.210] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@cl-498.udi-01.br.sixxs.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
pabs3 [pabs3!~pabs@d175-38-170-191.per801.wa.optusnet.com.au] has joined #qi-hardware
Artyom [Artyom!~chatzilla@84.23.62.51] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
panda|x201 [panda|x201!~hzhang@221.219.117.186] has joined #qi-hardware
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #qi-hardware
cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
Artyom [Artyom!~chatzilla@h6.net58.bmstu.ru] has joined #qi-hardware
<Artyom>
kristianpaul: hi! Are you here?
panda|x201 [panda|x201!~hzhang@221.219.117.186] has joined #qi-hardware
panda|x201 [panda|x201!~hzhang@221.219.117.186] has joined #qi-hardware
cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
blackrose1231 [blackrose1231!~blackrose@124.114.148.122] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
stefan_schmidt [stefan_schmidt!~stefan@guest213.ibr.cs.tu-bs.de] has joined #qi-hardware
rzk [rzk!~rzk@95-25-162-206.broadband.corbina.ru] has joined #qi-hardware
jekhor [jekhor!~jek@vulture2-nat-43.telecom.by] has joined #qi-hardware
DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware
rejon [rejon!~rejon@203.81.22.139] has joined #qi-hardware
mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
antoniodariush [antoniodariush!~antonioda@nat-sta-smtc2.tvu.ac.uk] has joined #qi-hardware
jivs [jivs!~jivs@nat-sta-smtc2.tvu.ac.uk] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
urandom__ [urandom__!~user@ip-88-152-212-215.unitymediagroup.de] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
jekhor [jekhor!~jek@mx2.promwad.com] has joined #qi-hardware
Ayla [Ayla!~paul@117.188.103.84.rev.sfr.net] has joined #qi-hardware
antoniodariush [antoniodariush!~antonioda@nat-sta-smtc2.tvu.ac.uk] has joined #qi-hardware
cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
wolfspraul [wolfspraul!~wolfsprau@p5B0AA732.dip.t-dialin.net] has joined #qi-hardware
mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
<kristianpaul>
Aryom yes.
<kristianpaul>
Artyom yes !
vladkorotnev [vladkorotnev!~Vladislav@94.41.25.55.dynamic.ufanet.ru] has joined #qi-hardware
vladkorotnev [vladkorotnev!~Vladislav@94.41.25.55.dynamic.ufanet.ru] has quit [#qi-hardware]
paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware
uwe__ [uwe__!~uwe_@dslb-088-064-223-216.pools.arcor-ip.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@cl-498.udi-01.br.sixxs.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
qwebirc66556 [qwebirc66556!503bdc3e@gateway/web/freenode/ip.80.59.220.62] has joined #qi-hardware
<qwebirc66556>
anybody knows how to make opkg update all packages?
mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware
qwebirc66306 [qwebirc66306!4766dbba@gateway/web/freenode/ip.71.102.219.186] has joined #qi-hardware
<rjeffries>
as an example of what's possible re specs for an under $100 handheld with (resistive) touch screen and lots of useful functions there's this $90 game unit running Android
<rjeffries>
no, it is not copyleft. but quite an interesting reference point IMO as to what is possible.
<wpwrak>
screen's too tiny. for milkymist, it would be nice to find a cheap 7"-10" screen, can be extra-wide if 10", with capacitative touch. as a finished module that doesn't need too many I/Os pins. ideally operating on a 5 V or 3.3 V supply. if you come across something like that, this may be interesting
<rjeffries>
wpwrak so you are thinking of a controller for Milkymist? that would make sense in the VJ conext. I understand iPads are used in that scene (not w/MM)
<rjeffries>
when OLPC ver 3 actually ships, the specs will be close to what you need. Linux already on board. although there are plenty of OLPC haters. they may have gotten it right this time.
<rjeffries>
"they" referring to OLPC, *not* the OLPC haters. ;)
<wpwrak>
rjeffries: yeah, just like they use iPads today (btw, M1 does actually support OSC, which is a common protocol for carrying MIDI and similar over TCP/IP)
<wpwrak>
we probably only need the display, not an entire device. but yes, some rock bottom cost droidblet may do, too. i'm not entirely sure what would be the less painful path from an engineering point of view - build up from scratch or defeat all the obstacles the sw/fw/hw of a ready product imposes
<rjeffries>
wpwrak finding something that's already packaged would be a win. no harm if the owner can also use it for non-MM tasks when he/she doesn't need it for MM
<rjeffries>
maybe you go client server, not unlike a VNC approach?
<rjeffries>
or is that too clumsy?
<wpwrak>
the harm would be more in making it work with our environment. e.g., finding a means of communication that works for both side. supply power. and so on.
<rjeffries>
well all tablets are battery operated, or can be charged over USB
<rjeffries>
MM has USB and many tablets have USB
<wpwrak>
you basically have to go up a few layers on one side, then connect on the usually complex point of compatibility, then go down again. if you just get the naked component, you save all that. and it's the same for software.
<wpwrak>
yes, if power over usb works, that's good. if communication over usb works with, say, OSC, even better.
<rjeffries>
I wonder if MM does feed out 5V on USB. you'd thinks so...
<wpwrak>
you'd still have a log of duplication of functionality, though
wolfspraul [wolfspraul!~wolfsprau@p5B0AA732.dip.t-dialin.net] has joined #qi-hardware
<wpwrak>
it does
<rjeffries>
s/log/lot/ ;)
<rjeffries>
understood
<wpwrak>
up to 500 mA
<wpwrak>
yeah :)
<rjeffries>
need to look up OSC protocol
<rjeffries>
ok, simple enough protocol. what is use case for this touch pad controller for MM?
wolfspraul [wolfspraul!~wolfsprau@p5B0AA732.dip.t-dialin.net] has joined #qi-hardware
<wpwrak>
rjeffries: same as midi. plus some extra control functions. e.g., image selection, patch selection. basically array of images and you pick one. basic stuff that's currently absurdly messy.
marcan [marcan!marcan@marcansoft.com] has joined #qi-hardware
wolfspraul [wolfspraul!~wolfsprau@p5B0AA732.dip.t-dialin.net] has joined #qi-hardware
wolfspraul [wolfspraul!~wolfsprau@p5B0AA732.dip.t-dialin.net] has joined #qi-hardware
kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #qi-hardware
<viric>
anyone using F8 in the nanonote?
<viric>
It looks to me like linux considers SYSRQ and F8 two different key values
<viric>
and sysreq happens always on leftalt+sysrq.
<viric>
I can't make it happen on leftalt+f8(value). I've to change the value of the f8 key to sysrq.
Artyom [Artyom!~chatzilla@84.23.62.191] has joined #qi-hardware
<kristianpaul>
i dont use any F keys*
Artyom [Artyom!~chatzilla@84.23.62.191] has joined #qi-hardware
<kristianpaul>
Artyom: hi
<kristianpaul>
s/F/Function
<Artyom>
hello Kristianpaul :)
<Artyom>
how is your work with namuru?
<kristianpaul>
having some issues getting the new data..
<kristianpaul>
i mean the flag
<Artyom>
And I have some good news :)
<kristianpaul>
oh
<kristianpaul>
tell us :)
<Artyom>
I had to switch to verilog
<kristianpaul>
oh !
<kristianpaul>
why? :)
<Artyom>
I connected namuru to wishbone
<Artyom>
wrote a test
<Artyom>
and it was successful
<Artyom>
And finally I used the program that I have already published and it worked
<kristianpaul>
but all this was with verilog version?
<Artyom>
So single channel acquisition, confirmation and pull-in is working on MM SoC (Digilent s3e500 port)
<kristianpaul>
i get lost
<kristianpaul>
wonderfull !
<Artyom>
yes all is in verilog
<Artyom>
I need some time to clean the code
<Artyom>
and then I will publish it
<kristianpaul>
what happened with vhdl?
<kristianpaul>
so the test program was ok?
<kristianpaul>
you said last time had some issues with wrong dealays or such
<kristianpaul>
those are great news anyway ! :)
<Artyom>
There was one stange thing when I tried to connect vhdl-namuru-port to wishbone. I had to work on falling edge of clock (otherwise there were errors)
<kristianpaul>
you just rewrote the whole vhdl code to verilog? including reset registers?
<kristianpaul>
erros.. hmm may be ise was very happy mixing vhdl and verilog ;-)
<Artyom>
And I decided that it would be better to have everything in verilog (as MM SoC is written in verilog). If I would find time to test gaisler's LEON3 then I would use vhdl ;)
<Artyom>
may be ISE, may be my weak knowledge of HDL ;)
<Artyom>
I just took namuru code, rewrote my test of each module from vhdl to verilog and I also studied VPI (or PLI) extension of verilog.
<kristianpaul>
how are you using VPI?
<kristianpaul>
or with wich porpuse?
<kristianpaul>
looks interesting i dint knew it about it
<Artyom>
verilog's vpi is very interesting thing. It allows to call C-functions from verilog code. So I could debug at the same time verilog and C-code. It's very powerful in my opinion. The main disadvantage is the speed. 3 seconds are simulating 1.5 hours
<Artyom>
kristianpaul: after reading 6 accumulators, I make some calculations to generate new code_frequency and carrier_frequency (during pull-in or tracking). And during acquisition I make next code_slew if threshold is not passed.
<viric>
that kernel thread is a must-read for kernel beginners like me, I think.
<kristianpaul>
Artyom: but no the prn code right?
<Artyom>
kristianpaul: And I start reading 6 accumulators only after status[1]=1 and new_data=1. prn code is set only once (next time only after you want to start to search for new satellite)
<kristianpaul>
Artyom: in your HDL namuru do you load ch0_epoch_enable bit by a separate register or just after ch0_epoch_load is loaded?
<kristianpaul>
i think was idea of mine to add separaate enable register for h0_epoch_enable,ch0_slew_enable,ch0_prn_key_enable
<kristianpaul>
and separate register to clear new_data_read,status_read flags
<kristianpaul>
or what do you think?
ManuZz [ManuZz!~opera@109.250.178.249] has quit [#qi-hardware]
<Artyom>
kristianpaul: Why do wnat ot use separate enable registers: ch0_epoch_enable, ch0_slew_enable, ch0_prn_key_enable? And why do you need separate register to clear new_data_read and status_read flags?
<kristianpaul>
why.. well
<viric>
larsc: after some time not touching any key, my screen got 'white' instead of switched off or black
<viric>
larsc: time to attach a gdb, if I can reproduce it again. I hope then I'll be able to check some registers
<kristianpaul>
i dont remenber i dint like how it was implemeted in namuru upstream
<kristianpaul>
how do you implemented it? :-)
<kristianpaul>
thw enable after write and clear after read :)
<kristianpaul>
do you get my point?
<Artyom>
kristianpaul: I previously used some additional commands (like clear_status and clear_new_data) because I had difficulties with connecting namuru-correlator to ARM through asynchronous memory bus (SRAM-like interface). But now I use MM SoC with synchronous wishbone bus. And now I got rid from these commands (status_clean and new_data_clean)
<kristianpaul>
I see
<Artyom>
kristianpaul: Now I use exactly namuru-code (the only difference is that I have implemented wishbone bus instead of avalon-bus)
<kristianpaul>
hmmm, dont do it for some reason but i cant remenber.. well if it works for you
<Artyom>
kristianpaul: I think i remember... There ware couple of bugs with reset-signal. May be something else. I've corrected them and forgot immediatly ;)
<kristianpaul>
unless the write cycle begin, but yes i need confirm for this the transfer cycle as well
<kristianpaul>
argh
<Artyom>
kristianpaul: I've copied this code from some bram-core
<kristianpaul>
he
<kristianpaul>
okay
<kristianpaul>
btw you feek the s3e500 is getting short in resources now?
<kristianpaul>
s/feek/noticed
<Artyom>
I tried to use only two of three (don't remember which exactly) in my vhdl code, like in the description of wishbone bus. And it didn't work. So I just copied the code from the bram-core
<qi-bot>
kristianpaul meant: "btw you noticed the s3e500 is getting short in resources now?"
jekhor [jekhor!~jek@vulture2-nat-46.telecom.by] has joined #qi-hardware
<larsc>
viric: if you ware using 3.2 this is expected behaviour since it misses the patch which fixes it
<kristianpaul>
Artyom: yup, ram0we (from bram), you always right !
<kristianpaul>
ok i'll do some fixing
<Artyom>
s3e500 is rather small. I use about 68% of it for lm32 without cache + single channel correlator. (no vga, ethernet, memorycard and all other unneccesary cores). But it's just a check of concept
jekhor [jekhor!~jek@vulture2-nat-44.telecom.by] has joined #qi-hardware
<kristianpaul>
Artyom: ok now i need to implement the other arms on the milkymist and make sofyware support it :)
<kristianpaul>
plus migrate the osgps part that get the fix..
<kristianpaul>
btw now the late and early arms are behaving right?
<kristianpaul>
BTW check this http://sdr.osmocom.org/ when have some time, the IF tunner supports a wide range of freq including GPS L1 ! :)
<Artyom>
no, still some unussual behaviour. I noticed it in the testbench of namuru-core. That's a question for the future ;)
<kristianpaul>
hmm
<Artyom>
I didn't run simulation for a long time. May be it's just a transient and after several seconds everything will be fine
<kristianpaul>
gota go i need do some herrands before 18:00 here, sorry..
<kristianpaul>
but thanks for the update and head up, now me behind ;) need move again..
<Artyom>
no problem, bye! It's time to sleep for me ;)
<kristianpaul>
good sleep then
<Artyom>
thanks :)
<kristianpaul>
s/herrands/errands
jekhor [jekhor!~jek@vulture2-nat-42.telecom.by] has joined #qi-hardware
skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
<viric>
larsc: ah, where is the patch?
<viric>
larsc: something to be ported? Maybe I could try to do that
jekhor_ [jekhor_!~jek@vulture2-nat-41.telecom.by] has joined #qi-hardware
jekhor [jekhor!~jek@vulture2-nat-46.telecom.by] has joined #qi-hardware
jekhor_ [jekhor_!~jek@vulture2-nat-46.telecom.by] has joined #qi-hardware
jekhor_ [jekhor_!~jek@vulture2-nat-41.telecom.by] has joined #qi-hardware