<xiangfu> exit
<kyak> xiangfu: hey
<kyak> xiangfu: btw, mocp is working just fine for me, with the Makefile in git (only removed the BROKEN tag)
<kyak> it complains about terminal size, however.. But doesn't segfault
<xiangfu> kyak: oh.. hmm.. I only test in my laptop. which the .config is different. I will try in buildhost.
<xiangfu> kyak: I will try to find out why.
<kyak> xiangfu: i didn't try on buildhost, too..
<kyak> xiangfu: seems that stardict builds its own version of libsigc, and links against it. And it causes some problems for me. I tryed adding libsigcxx to stadict's dependecies, this should help (i hope)
<kyak> in the full build, it uses libsigc from openwrt
<kyak> also, when building stardict in minimal build, i foudn that it lacks for libstdcpp dependency
<xiangfu> kyak: oh. good job :)
<kyak> but.. this can be confirmed only in the evening :)
<xiangfu> I just send out some email to u-boot, send ben nanonote patches to upstream :)
<kyak> oh great! is our u-boot very far away from upstream?
<xiangfu> kyak: yes. it's eating time for me. I will be back in ~ 1 hour. talk to you later. sorry.
<kyak> bon appetit!
<xiangfu> kyak: Ingenic's u-boot very far from upstream. ours much much better. :)
<kyak> would be nice to get rid of u-boot some day :) and use grub
<lekernel> why?
<kyak> because uboot needs specially built uImage and uboot doesn't provide a great flexibility (menus, editing kernel cmdline etc) , like grub does?
<qi-bot> [commit] Andres Calderon: Has been moved the labels that overlap. http://qi-hw.com/p/xue/fb92de3
<viric> kyak: what dictionaries you use in stardict? You seem very interest in it
<viric> interested
<kyak> viric: russian<->english and english <-> german
<kyak> i mostly use sdcv however (console version of stardict)
<kyak> stardict fails (or failed?) to start on my minimal build
<kyak> i'm pretty much sure it will start now...
<viric> ok
<viric> I use, for similar situations, 'dict'.
<xiangfu> kyak: we can set kernel command in ben nanonote.
<xiangfu> 1. run /usr/bin/fw_setenv_default  which write the default u-boot envs to nand.
<xiangfu> 2. using fw_setenv bootargs .... for set the cmdline.
<xiangfu> kyak: I think we should create a package like "nandnote-full-system-files", put all gmenu2x, ... all files not rewrite openwrt base file to this package.
<kyak> viric: as i remember, "dict" is gtk1, and gtk1 can't work with framebuffer (needs X)
<kyak> xiangfu: yeah, we can use the fw_setenv_default for that, but with grub it's just easy as pressing 'e' during boot. and the menu?
<viric> kyak: 'dict' is a server program
<viric> kyak: and it comes with a console client
<xiangfu> kyak: hmm.. then we must write keyboard and lcd driver for grub.
<kyak> xiangfu: i think it is better to move such files to relevant packages. The files that are not a part of some pacakge, can be left as they are? (like /etc/inputrc)
<viric> kyak: you can install other clients too.  It works through serving in tcp/localhost.
<xiangfu> kyak: compare to grub. maybe kboot is much better.
<kyak> viric:  ah ok.. need to have a look
<kyak> xiangfu: maybe! i never really tried anything except for grub/lilo
<kyak> viric: put a word "60;N78" in your accentizer, it won't work ;)
<viric> kyak: eh... :)
<kyak> xiangfu: hm, i didn't think it was so hard.. a special driver for keyboard/lcd for grub?
<kyak> viric: how does it work anyway?
<kyak> parsing some dictionary?
<viric> kyak: yes
<kyak> oh ok
<viric> kyak: did you notice that you can click on words?
<viric> (in the 'accentizer')
<kyak> uep
<viric> I think it's a great tool... but I failed to spread it.
<xiangfu> kyak: I am not sure about grub. I just want say. if we can write those driver for grub, then we can write them for u-boot. if you have a keyboard in u-boot. then you can easy edit just as grub :)
<kyak> the tooltip is a little bit over the word though
<kyak> in firefox
<viric> kyak: I only learnt the very very minimal javascript+css for that ;)
<viric> I use the akcentiga almost always I need to read anything in Russian
<viric> (I wrote it some years ago)
<kyak> hmm, i didn't realize it is hard to put accents for foreigners.. but i guess, yes, it is hard.. there are not general rules for that, a lot of excpetions :)
<xiangfu> kyak: since the gmenu2x store in projects.qi-hardware.com, maybe we just put all files/usr/share/gmenu2x/* to gmenu2x.git
<kyak> xiangfu: having menu in u-boot would be cool ;)
<viric> kyak: My sixth sense for guessing the accent usually puts the accent in a totally wrong position ;)
<viric> kyak: and it's very hard to find texts with accents marked.
<kyak> xiangfu: do you think maybe it is better to have those files in gmenu2x in openwrt-packages?
<xiangfu> kyak: my plan on u-boot is first send to upstream  then add new feature, so we stop add new thing to u-boot. (I am a little slow on send ben nanonote to upstream :-(
<kyak> viric: believe me, there are a lot of native speakers who are putting wrong accents
<viric> I imagine. But not on almost every word I imagine. :)
<kyak> usually other people laugh in their faces
<kyak> no, not like that ;)
<viric> having a quick dictionary like that of clicking the words also helps a lot.
<kyak> xiangfu: this is a good plan!
<viric> And it's no client-server interaction.. the HTML has all the dictionary definitions. You can save the html and have the click-code working
<kyak> viric: http://slovari.yandex.ru/~:=838/!;>20@L%20C40@5=89/
<kyak> A;>20@L C40@5=89 )
<kyak> xiangfu: i think putting gmenu2x files in gmenu2x.git will lead to mixing between source code and configs... I think configs need to be provided by gmenu2x in openwrt-packages
<kyak> configs+icons
<xiangfu> kyak: yes. sound good, let's do it.
<kyak> viric: dict homepage - is it http://www.dict.org/?
<kyak> xiangfu: btw, you've shown a nice way of postinstall handling (in nightsky). There are still files in /root that need to be moved to relevant packages (like netsurf and mplayer)
<kyak> i don't know what to do with /root/.vimrc though :)
<kyak> vim is from openwrt
<xiangfu> kyak: yes I will work on the move those files to relevant packages.
<kyak> or /root/.tclshrc
<kyak> ok, great!
<xiangfu> kyak: I also not sure about .vimrc .tclshrc . let's keep it in files/ for now.  the plan is stick upstream as much as possible.
<kyak> yes, they live in file/ just fine for now..
<kyak> hmm, i just noticed there is a qstardict
<kyak> taking into account that cyrillic input is working in Qt, might be a better choice than stardict
<kyak> i wonder what's working faster
<viric> kyak: yes
<qi-bot> [commit] Xiangfu Liu: mv all gmenu2x stuff to it's package http://qi-hw.com/p/openwrt-xburst/32e4611
<qi-bot> [commit] Xiangfu Liu: move gmenu2x from openwrt-xburst.git to it's package http://qi-hw.com/p/openwrt-packages/e517e97
<qi-bot> [commit] Xiangfu Liu: remove temp file http://qi-hw.com/p/openwrt-packages/ce1b4fa
<qi-bot> [commit] Xiangfu Liu: add icon for snownews http://qi-hw.com/p/openwrt-packages/af56909
<viric> kyak: Qt on directfb?
<viric> xiangfu, larsc: yesterday I had a problem on 2.6.35
<viric> Leave a cpu intensive program run for more than 10 minutes
<viric> (maybe others can do the test)
<viric> And check its 'user time' and 'cpu time' (/proc/PID/stat some numbers there)
<viric> After more or less 11 minutes, the user-time counter stops, and all gets added into the system-time counter.
<kyak> viric: yes, Qt can run on top of directfb
<viric> A usual cpu intensive program you can run is "openssl speed"
<viric> It checks the 'user-time' counter to display the cpu time passed
<viric> and after 11 minutes of running, it starts saying 0.0;
<viric> monitoring with strace, I see that what accumulated as user time, it goes to system (kernel) time and the user-time counter stops.
<viric> Different runs make the stopping moment vary. But it's always between 10 and 11 minutes, for what I tried. I tried with gzip and openssl speed.
<viric> Can someone put his nanonote with the heavy job of 'openssl speed'?
<viric> Is there a report of what is ready for the nanonote in 2.6.36?
<viric> maybe noone here has a running nanonote? :)
<viric> xiangfu testing 'nerase', kyak with qemu, ... :)
<kyak> nanonote? i heard someinth about it..
<kyak> :)
<bartbes> viric: running? :O
<bartbes> :P
<viric> hehe
<viric> I mean with an OS there and able to run programs
<viric> I'll try to build a 2.6.36 kernel
<viric> for i
<bartbes> maybe I do..
<viric> t
<viric> bartbes: could you make it run for 11 minutes (at least) "openssl speed"?
<bartbes> if you keep the time, I'll surely forget
<viric> well
<bartbes> no openssl installed?
<viric> you can make it run until it finishes :) It may take around 20 minutes.
<viric> ah you don't have openssl?
<viric> bad.
<viric> sooo
<kyak> openssl binary is not installed, yes
<viric> another thing. Try to make it run:   gzip </dev/zero > /dev/null &
<viric> kyak: I cannot reproduce the trouble in 2.6.36 malta, btw.
<bartbes> viric: alright, it's doing that
<viric> bartbes: then, note the gzip PID, and paste from time to time /proc/PID/stat here.
<bartbes> and now we wait
<viric> (a line with numbers)
<bartbes> ugh, time for ssh, so I can copy-paste
<viric> ah
<viric> bartbes: you can run:   cat /proc/PID/stat | cut -d ' ' -f 12,13
<viric> that will choose the numbers I want to run
<viric> I want to *see*
<bartbes> viric: 3 0
<viric> ouch. maybe not those then
<bartbes> 663 (gzip) R 436 663 436 1025 663 4194304 168 0 3 0 17827 917 0 0 20 0 1 0 8550 1638400 127 2147483647 4194304 4653656 2142728432 2142727632 4417872 0 0 0 0 0 0 0 18 0 0 0 0 0 0
<viric> try 14,15
<viric> aha, 14,15
<viric> 17827 = user jiffies = 178.27 seconds of user-mode time
<viric> 917 = system jiffies = 9.17 seconds of kernel-mode time
<viric> So what I see here is that, around 64000 jiffies (640 seconds), the user-mode time jiffie counter STOPS, and then all the time goes to the system jiffies (kernel mode time)
<bartbes> 27413 1388
<viric> looks fine.
<viric> let's wait for the 640 seconds
<viric> bartbes: what kernel you run btw?
<bartbes> ehm..
<viric> (thank you very much for the test)
<viric> uname -a
<bartbes> root@BenNanoNote:~# uname -a
<bartbes> Linux BenNanoNote 2.6.32.10 #1 PREEMPT Tue Jun 15 17:53:33 CEST 2010 mips GNU/Linux
<bartbes> yeah did that already
<viric> ok
<viric> good test then.
<bartbes> 36223 1834
<viric> that looks fine. user time increasing a lot, system time increasing little.
<bartbes> so ehm
<kyak> bartbes: you are good to update your system :) pretty old summer image
<bartbes> apparently you know
<bartbes> what are those time values supposed to be anyway?
<bartbes> kyak: well did SDL get fixed?
<viric> bartbes: user time in centiseconds, and kernel mode time in centiseconds
<kyak> bartbes: hm, did it get broken?
<bartbes> well yeah, but is the meaning of it?
<bartbes> kyak: it did, sometime
<viric> bartbes: How much time the process is spending CPU time in user-mode, and how much time the process is spending CPU time in kernel-mode (inside system calls)
<kyak> bartbes: should be fine in the last testing image
<bartbes> kyak: no stables coming up?
<bartbes> 46725 2339
<viric> (I'm building 2.6.36 to test if I also see the problem therE)
<kyak> i think it's official;
<bartbes> gforth added, yay
<kyak> beware though that the rootfs is 512 Mb now. you shoud probably save your data from datafs
<bartbes> I don't think I have much data anyway
<bartbes> the thing I'm worried about is confs ;)
<kyak> oh. do youreally have a lot of modifications?
<viric> wait - are you overwriting the whole rootfs to update your openwrt in the nanonote?
<bartbes> isn't that.. necessary?
<bartbes> 69752 3461
<viric> bartbes: 69752! I could not reach this. So it seems you are not seeing the problem I was seeing
<viric> bartbes: maybe it was something particular of the 2.6.35 I was running then.
<bartbes> I will keep it running for a little bit
<viric> bartbes: thank you1
<viric> !
<viric> So, for openwrt... I have no idea, I never used openwrt on the nanonote.
<viric> But I expected it had some update system...
<bartbes> I also have jlime on my sd card
<bartbes> 82731 4062
<bartbes> looks like it's working properly
<kyak> opkg can update. however now i think reflashing a newer image is only supported
<viric> bartbes: yes. Fine. thank you very much :)
<kyak> i think it's considerably faster, too
<bartbes> root@BenNanoNote:~# kill 663
<bartbes> ash: cannot kill pid 663: No such process
<bartbes> wee
<viric> bartbes: I'll check on 2.6.36. Maybe the bug was introduced at some time before 2.6.32 and 2.6.35
<bartbes> peace and quiet returns
<viric> :)
<bartbes> I.. forgot that shutting down from ssh leaves my ssh client wondering what the hell happened...
<viric> ~.
<viric> That kills the openssh client
<bartbes> the server, not the client
<viric> ah
<bartbes> so I'll have to wait until it times out, or kill it
<viric> how you know it's the server?
<bartbes> because.. the server runson on the ben?
<viric> Isn't it shut down?
<bartbes> and I just shut down the ben?
<bartbes> well exactly
<bartbes> so the server is down
<bartbes> the client doesn't know that yet
<viric> type ~.
<viric> that kills the client :)
<bartbes> no it doesn't
<viric> what ssh client you useç'
<viric> ?
<viric> openssh client is killed by 'tilde dot'
<viric> sorry
<bartbes> openssh
<viric> enter-tilde-dot
<bartbes> yeah, but it needs to be on its own line
<bartbes> I think that's where it fails
<bartbes> and I may or may not have overridden that key combo
<viric> maybe the stop sequence on the ben is broken; it shuts down before the ssh server can properly finish.
<viric> bartbes: why would you override enter-tilde-dot? :)
<bartbes> oh hey, I finally got it to work
<bartbes> or it timed out..
<bartbes> viric: I could have changed the key
<viric> you should not forget the 'enter'
<bartbes> I had to do alt-gr+shift+tilde then dot
<kyak> hm, never heard of that magic ~. :)
<viric> enter-tilde-?  explains other combinations
<kyak> i had to kill the process manually
<viric> it's similar to the telnet ^]
<bartbes> kyak: and the enter is there because it needs to be on its own line
<kyak> hm
<kyak> need to try it
<viric> own line?
<viric> what own line? :)
<kyak> how openssh client distinguish - maybe i want to send ~ to the server?
<viric> kyak: enter-tilde-tilde sends enter-tilde
<kyak> no, i mean i want to type ~
<kyak> like cd ~
<bartbes> viric: you can't do:
<bartbes> a~.
<bartbes> but you can do:
<viric> it does not have any problem. You can type ~ whenever you want. You only have to care if you want to type it AFTER *enter*
<bartbes> lol, fail
<bartbes> ~.
<viric> and in that case, type it twice.
<bartbes> I just disconnected trying to type that
<bartbes> :P
<kyak> heh
<viric> There is not any magic. The parser takes the sequence "enter-tilde", and that's all.
<kyak> ok, great thing to try when i get to openssh
<viric> it's not about any line. :)
<bartbes> viric: not true
<bartbes> it searches for ~ at the start of the line buffer
<viric> I'm at an irssi session
<bartbes> or so some docs said
<viric> I might have echo disabled
<viric> I might have the terminal in raw mode  (so no line buffer)
<viric> (like what I have now at the irssi session :)
<bartbes> viric: yeah yeah
<bartbes> whatever
<bartbes> it just needed to be at the start of the line
<viric> haha
<bartbes> which corresponds to \n~
<viric> no no
<viric> it's Enter-Tilde
<viric> not \n Tilde
<viric> In xterm, vt100 and other terminals, the enter key in raw mode provides a scancode of \r, and not \n.
<bartbes> viric: that was to signify a newline!
<bartbes> :@
<viric> And mine was to signify a carriage return ;)
<bartbes> !$@# those scancodes
<bartbes> (censorship provided by Quality Boats, get your censorship today!)
<viric> hehehe
<viric> utime 31038, stime 25. let's see how far it goes.
<bartbes> until it overflows ;)
<viric> Will anything be faster in 2.6.36? Who knows
<bartbes> I wonder
<bartbes> can those counters overflow?
<bartbes> (well, why wouldn't they?)
<viric> few may be worried on that :)
<bartbes> oh it won't cause anything bad
<bartbes> just wondering if it can
<viric> I don't think anyone implemented infinite-precision arithmetic for those.
<viric> utime 60037
<viric> utime 64125
<viric> 66110
<viric> great great
<viric> I consider it fixed on 2.6.36
<bartbes> yeah thought so
<bartbes> I mean, why would you bother?
<viric> well, all benchmark reports from openssl get broken
<viric> as it uses the 'user time' as measure.
<bartbes> meh
<bartbes> :P
<viric> updating openwrt through reflash looks annoying
<xiangfu> viric: kyak have added flashing progress. which is better now :), but I would like advice flash from sd card. :)
<viric> progress where?
<viric> in usbboot?
<xiangfu> viric: in reflash_ben.sh
<viric> ahh.
<qi-bot> [commit] Xiangfu Liu: add nanonote-example-files pakcage to config.full_system http://qi-hw.com/p/openwrt-xburst/225b32c
<wpwrak_> lekernel: working on your fab ? ;-)
<wolfspraul> great article
<lekernel> wpwrak_: preparing said work
<wolfspraul> I saw a machine once at a lense maker, I think it was some sort of thin film as well, not sure
<lekernel> wpwrak_: right now I have friends who got hands on vacuum pumps (2 primary pumps, 1 mercury (!) diffusion pump, 2 turbomolecular pumps and even one ion pump)
<lekernel> i'm going to check that out mid January
<lekernel> I also found an old evaporator from the 70s that no one uses and I can play around with... problem it weights hundreds of kg and is 1500km from where I live
<wolfspraul> what do you plan to build?
<wolfspraul> (or manufacture)
<lekernel> mess around with semiconductors, OLED displays, etc.
<lekernel> nothing commercial, just a fun hobby
<wolfspraul> great
<wolfspraul> we find a commercial application :-)
<lekernel> hm, will be hard imo :)
<wpwrak_> lekernel: well, we need a better lcm ... ;-)
<lekernel> LCM?
<lekernel> display
<lekernel> ?
<lekernel> well manufacturing them myself won't probably be economically viable
<wpwrak_> yes. lcd module
<wpwrak_> naw, invent the ground-breaking technology. let other figure out how to produce it :)
<wolfspraul> roh: you there?
<roh> wolfspraul hey
<wolfspraul> ah hi!
<wolfspraul> I posted a few things for you the other day, about the m1 case
<wolfspraul> 2 boards are on the way to Sebastien, hopefully they arrive tomorrow or the next few days
<roh> nice
<wolfspraul> did you read what I wrote? was about tolerances I think
<wolfspraul> worst seems to be the DC jack
<wolfspraul> I didn't know how bad this is until I saw it now :-)
<wolfspraul> so that one needs a lot of tolerance left and right
<roh> eh.. nope.. email?
<wolfspraul> in the next run we may want to tighten that a bit
<wolfspraul> probably here in the channel
<wolfspraul> ok let's just redo it
<wolfspraul> you asked about tolerances
<wolfspraul> the connectors to watch out for are: 1) DC jack 2) line-in and line-out 3) vga maybe a little
<wolfspraul> in that order
<wolfspraul> DC jack needs at least 1mm left and right tolerance
<roh> ok in case of doubt i can always add some more space
<roh> 1mm is _huge_
<wolfspraul> if you want to try, you can unsolder the DC jack on the sample you have, then you see how much wiggle room you have
<wolfspraul> yes
<wolfspraul> I know
<wolfspraul> there was a back and forth about vendors, and the result is that the holes in the pcb are quite big
<wolfspraul> unsolder your DC jack on the sample, then you see it yourself
<wolfspraul> so DC jack is the worst
<wolfspraul> after that - line-in and line-out
<roh> well.. its a dc jack.. i think the contacts are quite normal (the holes)
<wolfspraul> yes 'quite'
<wolfspraul> but when you go into the details and tolerances well there are still differences
<wolfspraul> just unsolder and see yourself :-)
<roh> lets just try some boards in plural and see how it comes out
<wolfspraul> you can try the same for line-in and line-out
<wolfspraul> ok up to you
<wolfspraul> unsoldering the DC jack will give you a quick idea
<wolfspraul> how is it going with the case?
<roh> waiting for the rc2 board
<roh> got my spacers
<qi-bot> [commit] kyak: stardict: add missing dependencies http://qi-hw.com/p/openwrt-packages/6c23e13
<qi-bot> [commit] Werner Almesberger: ecn/ecn0007.txt: Revised via spacing (for the antenna) http://qi-hw.com/p/ben-wpan/fbd3e53
<kristianpaul> oh well..
<kristianpaul> i hope i wasnt too hard on those mails
<wpwrak_> kristianpaul: naw. you're right. carlos should be in a very good position to post about "interesting" things. so if he doesn't do it, he shouldn't complain that others are filling the void
<kristianpaul> wpwrak_: you'were righ about your comments yday
<kristianpaul> testing now, i got the SPI to parallel now, but still missing SYN part i hope get it soon
<wpwrak_> kewl. can you use DMA with that parallel interface ? i haven't examined the fancier GPIO features yet, but I would suspect that you can't.
<kristianpaul> hmm close but now i'm missing 4 nibbles per convertion :S
<kristianpaul> (fianlly got an esy way of use scp and not deal with www permisions :))
<wpwrak_> kristianpaul: downloads.qi-hardware.com works quite nicely, too ;-)
<kristianpaul> ahh well
<kristianpaul> thats for the dumps for sure :)
<wpwrak_> the problem may be that you're using values > 3. given that you get a sync every 4 clock cycles, that can't work
<wpwrak_> so one has to give ...
<wpwrak_> (well, or at least that's what it was like a while ago)
<kristianpaul> i realy need a verilog boof for chrismass after this
<kristianpaul> ah, wait i can move an if some where
<kristianpaul> wait
<wpwrak_> booK ? :)
<kristianpaul> nah ,)
<kristianpaul> just "following" the buying spirit
<kristianpaul> Well i think i may be too stric, cause once i got a  sync signal i can predict next one and so on... well if i really trust hardware...
<wpwrak_> why not just re-sync ?
<wpwrak_> or change as follows: have an LSR and an output buffer. shift into LSR, on sync, clock LSR to output buffer.
<wpwrak_> you need something like this anyway :)
<wpwrak_> so SYNC is not the beginning of a data packet but the end of the previous one
<kristianpaul> hmm  i dint consider that one
<wpwrak_> if there's the wrong number of clocks between syncs, you get garbage. but then, you lose in this case anyway.
<wpwrak_> if you really want to get fancy, you could have an "error" signal
<kristianpaul> ha you got me
<kristianpaul> but thats for later
<kristianpaul> for sure
<kristianpaul> but i *trust* on sync
<kristianpaul> may be i can do other modeling to keep eye on sync good behave
<wpwrak_> you mean you never reset ? :)
<kristianpaul> yes
<kristianpaul> no wait
<kristianpaul> i mean yes i do reset
<kristianpaul> look mcu_rst
<wpwrak_> so, no trust on sync then ?
<wpwrak_> naw. i mean "reset the shift"
<wpwrak_> the full system reset is something else :-)
<kristianpaul> ahh thats a problem
<kristianpaul> (reset the shift)
<wpwrak_> well, you don't need to reset the shift. just copy data over to the latch
<kristianpaul> aja
<kristianpaul> o just reset count
<kristianpaul> wait i'll commit
<wpwrak_> now that you have a shifter, there shouldn't be a counter ;-)
<kristianpaul> hehe
<kristianpaul> well that help me to..
<qi-bot> [commit] Cristian Paul Peñaranda Rojas: Code now uses a shift register, and sync once to sync signal http://qi-hw.com/p/ben-gps-sdr/0324a53
<kristianpaul> "The description style you are using to describe a register or latch is not supported in the current software release."
<kristianpaul> oh here we go
<kristianpaul> i wonder if sofware compilers have those kind of messages :S
<wpwrak_> "internal compiler error" ? ;-)
<kristianpaul> lol
<wpwrak_> you indentation style looks very confusing
<wpwrak_> youR
<kristianpaul> i know
<kristianpaul> it looks for me too
<kristianpaul> wjay you suguest?
<kristianpaul> what*
<wpwrak_> pascal style: if (...)\nbegin\n\t...\n\t...etc...\nend
<wpwrak_> so the begin/end are at the same level as the if
<wpwrak_> i hope you realize that the counter now does absolutely nothing :-) it's all input, no output
<kristianpaul> yes yes
<wpwrak_> why not   always @ (posedge clk) begin if (sync) out <= shift_reg; shift+ref <= { data,shift_reg[WIDTH-1:1]}; end   ?
<wpwrak_> (i hope i got the syntax right)
<wpwrak_> err .. s/shift+ref/shift_reg/
<kristianpaul> i'll comment it for now
<kristianpaul> but i may help
<kristianpaul> is my watchdog
<kristianpaul> well watch for now
<kristianpaul> i'm missing the dog
<wpwrak_> ah, i see. well, a bit of confidence ... :)
<kristianpaul> (confidence) sure you will :)
<wpwrak_> that doesn't look too bad :)
<kristianpaul> assign out = shift_reg;
<kristianpaul> that fits better
<kristianpaul> a bit close
<kristianpaul> i'm just afraid it start to shift data even when not sync signal is there :/
<wpwrak_> yes, it will shift without sync. but that's an abnormal situation anyway.
<wpwrak_> so what every you do it wrong :)
<wpwrak_> (assign) hmm, "procedural continuous assignment". seems to have the same effect as a normal assignment, no ?
<wpwrak_> (in this case)
<kristianpaul> order vs parallel
<wpwrak_> ah ... got it. but that's = vs. <=, not assign vs. <=/=
<wpwrak_> so ...
<wpwrak_> ... out = shift_reg; shift_reg = { data,shift_reg[WIDTH-1:1]}; ...
<kristianpaul> ah yes
<kristianpaul> sorry
<kristianpaul> assign is used for wiring to real world actually
<kristianpaul> thats why i now
<kristianpaul> s/why/what
<kristianpaul> s/now/know
<kristianpaul> argg typo
<wpwrak_> isn't the "real world" part something that's in the declaration ? (not sure)
<wpwrak_> i have a book on verilog, and it says that "assign" basically overrides assignments with <= and =
<wpwrak_> the example being a reset signal: while reset is asserted, you want to force the output to a given value, even if there's a clock or any other change of input
<kristianpaul> hmm you got me on that, i'm learning verilog btw ;)
<wpwrak_> so when reset gets asserted, you "assign" the reset value. when reset gets deasserted, you "deassign" it. if anything else tries to change the value with = or <= while "assign"ed, nothing happens
<wpwrak_> or at least that's how i understand it :)
<wpwrak_> don't worry, i don't even know verilog. i just have a book :)
<kristianpaul> The assign and deassign procedural assignment statements allow continuous assignments to be placed onto registers for controlled periods of time. The assign procedural statement overrides procedural assignments to a register. The deassign procedural statement ends a continuous assignment to a register.
<kristianpaul> space.gif
<kristianpaul> ops
<kristianpaul> I need read mre
<kristianpaul> hmmm i may want to do a 16bit register at once in order to save time
<wpwrak_> sounds like the great return of the counter :)
<wpwrak_> 16 bit shifter, count to 4 syncs, then out = shift_reg
<wpwrak_> or use a multiplexer. not sure which is more efficient.
<kristianpaul> neither me, actually thats  a question for xilinx eng
<wpwrak_> don't you get some chip resource usage info when you do the synthesis ?
<kristianpaul> sure
<kristianpaul> i can do becnhmark later
<kristianpaul> also i get timings
<wpwrak_> then you can just implement both and see which comes back smaller
<kristianpaul> sure
<kristianpaul> okay 16 bits looks good also to take the whole A port
<kristianpaul> but  thats not valid for a ben.. if i may want try on it later..
<wpwrak_> for then ben, you could implement SDIO ! ;-)
<kristianpaul> thats 8 bits?
<kristianpaul> or 4..
<kristianpaul> i always ask the same :/
<kristianpaul> let see
<wpwrak_> 4 bits + clock + command
<kristianpaul> ah ok i'll stick on 4 and let that work (16bit) to sofware
<wpwrak_> for sdio, things get a little more complicated ... e.g., the clock comes from the host
<kristianpaul> hmm
<wpwrak_> so you may need a buffer for the whole block
<kristianpaul> yeap
<kristianpaul> whats the clock rate?
<wpwrak_> but that's something you don't have to worry about now :)
<kristianpaul> yeap
<wpwrak_> there are several clock rate ranges. the host gets to pick what it likes.
<kristianpaul> ok i'll wire it later, well on fpga i already wired SiGE and ANT cable :)
<kristianpaul> gn8
<wpwrak_> sweet dreams ! :)
<kristianpaul> i'll dream with clocks for sure ;)