<wpwrak>
whitequark: for atben, they're in tools/lib/atben.c
<wpwrak>
whitequark: atusb doesn''t bit-bang but uses the SPI controller in the MCU. code in atusb/fw/spi.c
<wpwrak>
whitequark: there's also unusual bitbanging in tools/atrf-xtal/atben.c (unusual in the sense that they're not used for the regular register interface)
<wpwrak>
whitequark: of course, none of this has anything to do with the kernel :) for that, you need to look at the qi-kernel tree. there, i just use the regular spi-bitbang driver, slow as it is
<wpwrak>
whitequark: so the answer depends a lot on what exactly you're looking for ;-)
<Model_M>
Does the libncurses-dev package provide the libraries for gcc-mips?
<wpwrak>
hmm, what is "libcurses-dev package", what are "the libraries" and what is "gcc-mips" ? ;-)
<wpwrak>
there are certainly libcurses-dev packages in existence that provide libraries compiled with gcc for some MIPS target
<Model_M>
Hmm, well I just recently got the nanonote, so I'm only familiar with the packages provided at qi-hardware.com So I refer to the libncurses-dev package provided there. As well as the gcc compiler provided there. The libraries would be the libraries required to compile a program using ncurses.
<wpwrak>
there are two distributions there, openwrt and jlime. they're unfortunately not library-compatible. but as long as you pick things consistently from the same, what you wrote ought to be correct.
<wpwrak>
(the distribution the ben comes with is openwrt)
<wpwrak>
ah, and i don't know which version they pre-install. so if it's very old, you may have to upgrade first
<qi-bot>
[commit] Xiangfu Liu: new package: gtkguitune: for tuning guitars and other instruments by using the method of Schmitt-triggering http://qi-hw.com/p/openwrt-packages/6c1f174
<kyak>
xiangfu: note that link from qi-bot is not working -\
<kyak>
The build was successfull, see images here:
<kyak>
should be "openwrt-xburst.trunk-full_system-06012011-1849/"
<wolfspraul>
kyak: which link is not working?
<kyak>
wolfspraul: the one qi-bot is announcing once the build has finished
<wolfspraul>
oh it does?
<kyak>
yep..
<Fusin>
i guessed it ;)
<kyak>
Fusin: you might've noticed that qi-bot is referring to him as just "Bill"
<kyak>
they are good friends
<wpwrak>
first nokia, now qi-hw ... what's the world coming to ?
<Fusin>
i thought his name came from the fact, that those who use his software are passing a Gates of Bills, hence Bill Gates :P
<Fusin>
s/a/
<Fusin>
shitty waiting-day
<Fusin>
waits technician from telco to reconnect his DSL-line...
<wpwrak>
Fusin: always fun to have to wait for some to ring your doorbell :)
<wpwrak>
interesting ... if i have two pointers  volatile uint32_t *foo, *bar;  and i use them in an assignment of the type  *foo = *bar = value;  then gcc seem to drop one of the stores
<wpwrak>
hah, worse. it does the equivalent of
<wpwrak>
*bar = value;
<wpwrak>
*foo = *bar;
<wpwrak>
it has a certain logic to it ... but seems wrongish nevertheless
<Fusin>
as Mr. Spock said: fascinating.
<wpwrak>
ANSI C leaves this ambiguous. the value of the assignment should be "the value stored". that could be either.
<wpwrak>
ah well, splitting the assignment then
<Fusin>
and Yoda says: Not the logic important is, results matters
<larsc>
wpwrak: the compiler did exactly what you told it
<wpwrak>
Fusin: atrf-gpio says "hzHhhl"
<wpwrak>
larsc: depends on how you interpret what the "stored" value of an assignment expression ought to be. the value that was _written_ or the value that can be _read_ after writing.
<Fusin>
hrhr
<whitequark>
wpwrak: regarding the bitbanging, I was interested in the method used to access atben, so it probably rules out atusb stuff and in-kernel spi driver (you don't use that right?)
<whitequark>
wpwrak: particularly, I was looking for a 'good' way to remap mcu registers to userspace
<wpwrak>
larsc: but yes, in the ANSI C standard, it reads more like the second interpretation. and also in the narrative of K&R 2nd ed.
<wpwrak>
whitequark: for atben, i have all sorts of access methods :)
<whitequark>
wpwrak: the code in tools/lib/atben.c is simple enough
<whitequark>
just an mmap
<wpwrak>
whitequark: (atben) my tools use bit-banging from user space, but usually encapsulate it in a library. in some cases, they bypass the library, though. for "real" use, you'd use the kernel driver, which is currently based on the bit-banging spi driver. (but i have to try and see if i can't make it a lot faster with an optimized driver. speed may matter here.)
<wpwrak>
yeah, if you look past all the power cycling stuff, atben.c isn't too bad
<whitequark>
wpwrak: talking about power cycling, how did you determined the right intervals (the ones you provide as a reference, i.e. 2ms and not 10 for poweron)?
<whitequark>
just used a scope and measured them directly?
<wpwrak>
i don't remember. maybe i just tried some values until it worked ;) but a scope may have been involved, too
<whitequark>
could you point me to atben schematics?
<whitequark>
wpwrak: looks like it is not very complicated. at least not significantly more than cc2500-based circuit
<whitequark>
there is one problem for me through. atrfs are not imported to russia
<wpwrak>
strange. the ti stuff has US export restrictions (or at least had it last time i checked), while the atmel stuff doesn't. i thought those restrictions were there mainly to keep you evil commies at a distance ? ;-)
<whitequark>
the problem is not with export restrictions at all
<whitequark>
there's just no people working with them here, and so no one buys them
<whitequark>
the same applies to any other non-very-common chip
<wpwrak>
any chance that digikey.ru could be of use ? they probably know how to get things through customs efficiently (if possible at all)
<wpwrak>
the difference between knowing how to do international shipments and only thinking one knows it can sometimes be rather significant. such as 3x the shipping cost and 5x the customs processing cost
<wpwrak>
(from examples i have here)
<whitequark>
from the banner on front page: "THE COST OF DELIVERY TO RUSSIA IS $120"
<wpwrak>
ah, pricy ...
<whitequark>
huh, chipfind.ru promises delivery of anything from Farnell, from one part
<whitequark>
the minimal cost is around $20, and there's no delivery fee
<wpwrak>
neat
<whitequark>
they deliver it for ~18 days, through
<whitequark>
still much better than nothing :)
<wpwrak>
i.e., 7 days at customs :)
<whitequark>
there's still same problem with RF parts
<whitequark>
*passive RF parts
<wpwrak>
you mean the balun ?
<whitequark>
yeah
<whitequark>
hm, there's no problem. farnell has them too, for like $0.5
<wpwrak>
there are two: the one from johanson and one from wuerth. the latter is more expensive.
<wpwrak>
WURTH 748421245
<wpwrak>
JOHANSON 2450FB15L0001
<whitequark>
digikey has Wurth ones for $4
<wpwrak>
they should have both
<wpwrak>
USD 2.58 @1
<wpwrak>
the johanson is USD 1.27 @1
<whitequark>
I've looked up costs on that russian proxy. also, johanson is ~$0.5 somehow
<wpwrak>
if you're determined, you can also make a discrete balun
<wpwrak>
0.50 for MOQ 1 ? or 1000 ? :)
<whitequark>
for 1
<whitequark>
for 1000 it's even cheaper
<wpwrak>
you have some funny pricing in russia :)
<whitequark>
I guess it has something to do with nuclear physics
<whitequark>
you know, the particles with negative mass
<whitequark>
somewhere customs will take away 5x the real cost, and that'll get compensated due to law of conservation of money
<wpwrak>
that sounds like the most plausible explanation indeed :)
<whitequark>
so I guess that my workflow should be like this:
<whitequark>
order ben, atben & atusb [wait a month], then play with RF stuff a bit to understand how it works, then order atrfs and related parts [wait a month while I can learn to make two-side pcbs], and then try to assemble something working
<whitequark>
(and then accidentally fry everything and start over.)
<wpwrak>
sounds like a plan, yes :)
<wpwrak>
you could of course even order the parts before the boards arrive. pipelining :)
<wpwrak>
aw_: all this is being run by fidelio:/home/schhist/schhist_update_all
<wpwrak>
aw_: if you only want to run it locally, then you'd use schhist2web from the eda-tools project, directory schhist/
<wpwrak>
aw_: first argument is the path to the target project's top-level directory, then the relative path from there to the top-level schematics, and finally the name of the output directory
<wpwrak>
aw_: e.g., if your project is called "foo" and your schematics begin at foo/bar.sch, you could simply cd to foo, then run ../eda-tools/schhist/schhist2web . bar.sch whatever
<wpwrak>
(where "whatever" is the name of the output directory)
<wpwrak>
you can then fire up a browser on that foo/whatever/index.html