<wolfspraul>
adamw_: hey, great patch! you slowly become a git expert, fantastic!
<adamw_>
he..just found those files seems temporarily generated. but I don't need them.
<adamw_>
the shop store in Kwuanhwa they said yes, the 300MHz probe is became more common.
<adamw_>
but well...since ours scope is only 100MHz, so I don't need to buy a 300MHz probe.
<adamw_>
but sure ideally an input probe with more wide range is always good for 100MHz scope. :)
<wolfspraul>
adamw_: how much was the 300mhz probe you found?
<adamw_>
ntd 1300 roughly.
<adamw_>
100MHz >> ntd 750
<wolfspraul>
hmm. the difference is just 20 USD. Should we just buy the 300mhz one?
<xiangfu>
will remove the ImageBuilder and Toolchain from config.full_system.
<adamw_>
why not? if you want. :)
<xiangfu>
adamw_: ;-)
<wolfspraul>
adamw_: ok I think the difference on a 100mhz scope will be minor. So buy the one that is easier for you. Since you are back already, no need to go out to kuanhua again. buy online. but if it's easier on kuanhua, buy there. Your time is also important :-)
<adamw_>
I'll directly buy two 300MHz probes while go back home along my way. :)
<wolfspraul>
ok great
<yizhang>
xiangfu: while i am in gmenu2x, press 'alt+ctrl+F2' will take me to the console. however i can only press 'alt+ctrl+F5' to get back to gmenu2x, 'exit' command will not do the same.
<yizhang>
xiangfu_:Â Â while i am in gmenu2x, press 'alt+ctrl+F2' will take me to the console. however i can only press 'alt+ctrl+F5' to get back to gmenu2x, 'exit' command will not do the same.
<yizhang>
is this an intentional feature or is it a bug?
<xiangfu_>
yizhang: not a bug.
<xiangfu_>
yizhang: if you using 'alt+ctrl+F2' goto console. you must using 'alt+ctrl+F5' go back, there are different 'Terminal'
<yizhang>
this is not a ash?
<xiangfu_>
in ctrl+alt+F2 is a ash :)
<wpwrak_>
(at&t pc) hehe ;-)
<wpwrak_>
kristianpaul: "no please no more discuss about changing NAND schema again ;-)" no discussion, just changes ;-)
<wpwrak_>
wolfspraul: doesn't the scope have three inputs, CH1, CH2, and trigger ? then you need three probes.
<wolfspraul>
hmm, good point don't know
<kristianpaul>
wpwrak_: :)
<wolfspraul>
wpwrak_: btw, --plot works as well (in pcbnew), now I'm doing --drc, and after that probably --pos (module positions)
<wolfspraul>
every one is different though, thanks to the magic myriad C++ dependencies...
<wpwrak_>
wolfspraul: (not that the scope vendors would usually include a probe for trigger - but hey, accessories are a nice market, too :)
<wolfspraul>
if I get stuck somewhere, I will cleanup what I have so far and upload the patch, then you can try. I think what you need the most is --drill and --plot in pcbnew, and I have those, need your feedback.
<wpwrak_>
wolfspraul: excellent ! i admire your c++ skills already ! :)
<wpwrak_>
wolfspraul: and your persistence in the face of ugly code :) if that IT and hardware thing goes sour, you can always have a stellar career in waste management ;-)
<wolfspraul>
so I do --drc now, then --pos, then --svg, --vrml, --bom
<wolfspraul>
since I'm at it, I may as well try to get it all out programmatically, could be helpful later
<wolfspraul>
I will also go back to eeschema and add netlist
<wpwrak_>
great. the next step would be to apply your patches to the latest svn version. and then see how they like them. with so much cool stuff, it'll be very hard to just dismiss it :)
<wolfspraul>
oh one by one
<wolfspraul>
first we get it applied to the old 2448, then you try to use it, feedback etc.
<wolfspraul>
you may very well run into segfaults, or you need additional cmdline switches, etc.
<wolfspraul>
let's first make it work well
<wolfspraul>
then, if we update our base version, of course there will be work in upticking those patches. but that's good stuff so I can slowly clean it up more.
<wolfspraul>
in parallel I can write to the kicad devel list and see whether they want to accept a few patches that lead to a cleaner separation of UI and data processing
<wolfspraul>
it's not too bad, but in a lot of places the two are still intertwined...
<wpwrak_>
yeah, once you've done it the first time, it shouldn't be too hard to update it.
<wolfspraul>
ah, don't say that
<wolfspraul>
those c++ dependency jungles are very fragile
<wpwrak_>
i think cleanup would be great. the lack of a proper separation is what prevented me from going any further with the command-line-driven file output
<wolfspraul>
for example the last few hours I am trying to trace down a weird segfault somewhere in the drc code
<wolfspraul>
if I run through the UI, it works
<wpwrak_>
;-)
<wolfspraul>
but when I try to run the same (well, probably not exactly the same) logic bypassing the gui stuff, there is a segfault somewhere
<wolfspraul>
argh
<wolfspraul>
but I try to make it work fast
<wolfspraul>
especially since --drill and --plot are ready for testing. so if I get stuck too long, I'll upload that first.
<wpwrak_>
ah, one important thing: you need to trigger the zone filling before outputting the layers (drc will do it)
<wolfspraul>
I thought --drc is fast, that was wrong...
<wolfspraul>
zone filling?
<wpwrak_>
ground areas and such
<wolfspraul>
no idea :-) let's see when you have it running whether it's usable or not. need a bit more time...
<wpwrak_>
of course, doing the zone filling there will also avoid the nasty problem of not having the zones filled (they make things very slow, so for working on the layout, it's convenient to unfill the zones), and then plotting - because kicad doesn't automatically fill the zones in this case. if you don't notice in time, you make a board without ground/etc. areas ...
<wolfspraul>
well one by one. I first try to introduce some scriptability into a lot of the GUI driven codepaths.
<wolfspraul>
then we can look at what it actually writes, and finetune more parameters.
<wpwrak_>
very nice :)
<wolfspraul>
it's not too bad, really.
<wolfspraul>
I like their work.
<wpwrak_>
in 2011, kicad will be twice as good as it was in 2010 ;-)
<wolfspraul>
they do try to separate stuff.
<wolfspraul>
of course there are still a lot of pointers here there, back forth, etc. and 'friend' and what not, but definitely it's a good work.
<wpwrak_>
(separate stuff) good. maybe they also cleaned things up a bit more since i last looked at the code
<wolfspraul>
he, my --drc just finally wrote a complete report without segfault.
<wolfspraul>
but a lot of flickering since I left the entire GUI codepath in. Now I only need to see when the segfault reappears as I remove the GUI stuff...
<wpwrak_>
what bothered me most were some very long and deeply indented functions - and c++'s inability to easily break them into more manageable pieces
<kristianpaul>
wpwrak_: (probe for trigger) i dint knew that, there is something distinctive on it?
<wpwrak_>
kristianpaul: it's the same kind of input. you basically have 2.5 channels. so if you have a trigger signal and want to watch two other signals, you can do that. you don't need this a lot, but when you need it, it's nice to have.
<kristianpaul>
Jay7: fb menu, well there is gmenu2x, do you know it?
<kristianpaul>
basically an app lanucher, with wallpaper and battery indicator is needed
<kristianpaul>
sure this uboot is bettet that nanonote's one
<kristianpaul>
;-)
<kristianpaul>
:s ./dumpif: double free or corruption (out): 0x00411008
<kristianpaul>
hmm is gone after replace calloc with malloc...
<qi-bot>
[commit] Cristian Paul Peñaranda Rojas: Copy data to memory if sync register is set to high (work in progress) http://qi-hw.com/p/ben-gps-sdr/1685166