DocScrutinizer05 changed the topic of #qi-hardware to: 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 and http://irclog.whitequark.org/qi-hardware
gbraad has quit [Ping timeout: 256 seconds]
Luke-Jr has quit [Ping timeout: 245 seconds]
rz2k has quit []
Luke-Jr has joined #qi-hardware
pcercuei has quit [Read error: Operation timed out]
compcube has quit [Quit: Leaving]
Freemor has quit [Remote host closed the connection]
<DocScrutinizer05> lol!
<DocScrutinizer05> >> [2013-08-25 19:56:06] <patchvonbraun1> bounce: But to be honest, these dongles are just fine for radio astronomy, provided you have adequate filtering in front of them, and some low-noise gain. Which you always need anyway
<DocScrutinizer05> >> [2013-08-25 19:56:33] <patchvonbraun1> bounce: I'm using a plethora of dongles on the SBRAC dish
<whitequark> lol indeed
<DocScrutinizer05> the dongle: http://sdr.osmocom.org/trac/wiki/rtl-sdr The dish: http://www.sbrac.org
<wpwrak> and thus SETI (Summoning of ExtraTerrestrIals) enters an entirely new phase ...
apelete has quit [Read error: Operation timed out]
xiangfu has joined #qi-hardware
Freemor has joined #qi-hardware
wolfspraul has joined #qi-hardware
panda|x201 has quit [Ping timeout: 264 seconds]
apelete has joined #qi-hardware
apelete has quit [Ping timeout: 268 seconds]
panda|x201 has joined #qi-hardware
apelete has joined #qi-hardware
viric_ has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric_ is now known as viric
<cde> DocScrutinizer05 :)
lekernel has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
panda|x201 has quit [Ping timeout: 268 seconds]
pcercuei has joined #qi-hardware
gbraad has joined #qi-hardware
gbraad has joined #qi-hardware
panda|x201 has joined #qi-hardware
uwe__ is now known as uwe_
porchao has joined #qi-hardware
ffio has joined #qi-hardware
apelete has quit [Ping timeout: 260 seconds]
lekernel has quit [Ping timeout: 264 seconds]
panda|x201 has quit [Ping timeout: 240 seconds]
FDCX has joined #qi-hardware
lekernel has joined #qi-hardware
apelete has joined #qi-hardware
ffio has quit [Ping timeout: 260 seconds]
ffio has joined #qi-hardware
rz2k has joined #qi-hardware
wej has quit [Ping timeout: 260 seconds]
wej has joined #qi-hardware
xiangfu has quit [Ping timeout: 276 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
panda|x201 has joined #qi-hardware
wej has quit [Ping timeout: 264 seconds]
paul_boddie has joined #qi-hardware
<paul_boddie> Hello! Does anyone have any opinions/experiences with the nanosleep system call on the NanoNote?
wej has joined #qi-hardware
<paul_boddie> It doesn't seem very "nano", but I wonder if the NanoNote is fast enough to notice any intervals at that level.
<larsc> nano is GHz
<paul_boddie> Indeed.
<paul_boddie> Even hundreds of nano - tenths of micro - are probably asking a bit much from the poor Ben.
<paul_boddie> I think the call itself is probably expensive enough to burn up any delay of that order.
kilae has joined #qi-hardware
<larsc> yes
<paul_boddie> So I guess I should ask what the best way is to put delays into NanoNote programs.
<larsc> i = 100; while(--i);
<larsc> ;)
<paul_boddie> I've been doing I2C stuff, and without any delay I manage to race ahead of the slave unless I do an empty for loop. :-)
<larsc> I'd let the kernel handle I2C stuff
<paul_boddie> I haven't really had this problem with SPI stuff before now.
<paul_boddie> Can the kernel coordinate I2C stuff over the 8:10/MMC port?
<paul_boddie> I saw that wpwrak had done some SPI drivers which I should perhaps be looking at for my SPI experiments. (Or maybe I misremember.)
<mth> if you configure the pins as plain GPIO pins, you should be able to use the i2c-gpio driver with them
<mth> configure -> making sure no MMC driver claims them is probably enough
<paul_boddie> Thanks, mth! I suppose the only disadvantage that I can think of is that I'm then forced into "driver space".
<mth> you can send I2C messages from user space
<mth> with only the bitbanging done in kernel
<mth> see the i2c-tools package
<paul_boddie> Useful to know, thanks! If I ever get to the point of wanting to migrate some of this into a driver, it'd be a nice first step.
<paul_boddie> I guess it is this: http://www.lm-sensors.org/wiki/I2CTools
<mth> yes
<mth> search for "i2c"
<mth> specifically, for CONFIG_I2C_GPIO
<paul_boddie> Is this a recent kernel thing?
<mth> no, it has been there a few years at least
<paul_boddie> Maybe I have to dig a bit more in my kernel sources.
<paul_boddie> Ah, I see it now!
<paul_boddie> Thanks for the help once again! :-)
Jay7 has quit [Ping timeout: 245 seconds]
paul_boddie has left #qi-hardware ["Konversation terminated!"]
ffio has quit [Ping timeout: 240 seconds]
whitequa1k has joined #qi-hardware
whitequark has quit [Remote host closed the connection]
ffio has joined #qi-hardware
ffio has quit [Quit: WeeChat 0.4.1]
Jay7 has joined #qi-hardware
Jay7 has quit [Ping timeout: 240 seconds]
Ornotermes has quit [Quit: leaving]
Ornotermes has joined #qi-hardware
Jay7 has joined #qi-hardware
Jay7 has quit [Ping timeout: 256 seconds]
wej has quit [Ping timeout: 260 seconds]
wej has joined #qi-hardware
wej has quit [Ping timeout: 264 seconds]
wej has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]]
arossdotme has joined #qi-hardware
porchao has quit [Quit: Leaving...]
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
lekernel has quit [Quit: Leaving]
wej has quit [Ping timeout: 260 seconds]
wolfspraul has quit [Quit: leaving]
wej has joined #qi-hardware
gbraad has quit [Ping timeout: 245 seconds]
porchao has joined #qi-hardware
kristianpaul has quit [Remote host closed the connection]
arossdotme has quit [Ping timeout: 256 seconds]
rz2k has quit []