<kristianpaul> lol
<mth> the last version I checked did, but I don't know if I'm fully up to date
<kristianpaul> ha, seems people here a kindle ;-)
<mth> I'm at 7aeb7a4f0a693a1e67209e8ec3439d71326529cb
<mth> that version I tested and have been using ever since I committed it
<Ayla> nice, it looks like kyak fixed one month ago the bug I'm having now
<kristianpaul> brr 23 C night, 32 C day..
<kristianpaul> amazing how people can relly on altera megafunctions even for a 3 bits serial in/out shifter, but i guess a hurry is the main cause
<kristianpaul> one counter left to migrate from altera megafunction to HDL..
<ezdagor> Why is it that with Debian, on the NanoNote there is around 2GB total drive space, but with OpenWRT there is only around 500MB?
<kyak> ezdagor: the openwrt image resides in a so called rootfs, which is 512 Mb. You have to mount the remaining space ("datafs") manually
<kyak> it seems like debian installation is just using the whole NAND
<kyak> if you are using one of the latest openwrt images, see the mtd.nn - it provides facilities to easily format and mount the datafs
<ezdagor> Ok. Thanks.
<kyak> np
<wpwrak> kristianpaul: freezing nights, eh
<wpwrak> kristianpaul: but just watch out, in something like 5 months, we'll catch up with you guys :)
<kyak> wpwrak: i'm writing this message from my Ben while laying on a couch :)
<kyak> it works better than i thought :)
<dvdk> cool
<dvdk> time to order one, too :)
<dvdk> is this w/ dirtpan?
<kyak> yeah
<dvdk> how does it work as a sip-phone ? :)  
<dvdk> kidding
<kyak> now my screen session is always with me around the house :)
<kyak> dvdk: it works fine when typing in ssh, but won't really work for huge data transmissions yet
<kyak> for example, receiving data from ftp at 2.5 K/s
<kyak> 500 b/s :)
<wolfspraul> sip-phone, why not?
<wolfspraul> 250kbit/sec should not be the problem, more roundtrip delays, encoding, noise, protocol inefficiencies, etc.
<wpwrak> kyak: whooo !! so cool !
<wpwrak> kyak: that's not even supposed to be possible yet ;-))
<kyak> well, it is :)
<kyak> wpwrak: what is the current consumption of atben module?
<wpwrak> kyak: what's your ping round-trip-time ?
<kyak> round-trip min/avg/max = 60.467/61.998/67.772 ms
<wpwrak> kyak: current should be around 15 mA
<wpwrak> kyak: hmm. that's atben to atusb ?
<kyak> approximately the same when pinging some internet host or the laptop
<kyak> yeah, atben to atusb
<wpwrak> kyak: very interesting. yours is about 2-3x faster than mine. what USB controller does the PC have ? UHCI or OHCI ?
<kyak> i have both EHCI and UHCI, trying to figure out where exacly is atusb plugged in..
<wpwrak> should be the UHCI. i think EHCI is only used for high-speed.
<kyak> but it's definitely not OHCI
<kyak> then it's UHCI
<wpwrak> very interesting. something happens a lot faster in your PC than in mine.
<kyak> my laptop is very old
<kyak> but, atben and atusb are like 20 cm away from each other right now
<wpwrak> oh, distance shouldn't matter for this
<kyak> are you interested in my kernel config?
<kyak> might be something there
<wpwrak> (distance) well, up to the range limit :)
<wpwrak> (config) yes, please :)
<kyak> oh i must mention one thing
<kyak> the qi-kernel didn't build quite well, i had to use this patch:
<kyak> this one here, and i had exactly the mentioned problem
<wpwrak> ah, interesting. didn't hit that one.
<wpwrak> perhaps because i'm on 64 bit
<kyak> yeah, i didn't hit it either when doing defconfig
<kyak> but then i used my distribution's kernel config as a base
<kyak> and i hit it
<wpwrak> maybe it's the high-res timers
<kyak> it could be.. btw, the kernel from defconfig didn't work at all with atusb
<kyak> the system was frozen
<wpwrak> did you see when it froze ?
<kyak> when i inserted atusb
<kyak> then i used my distribution's config and make localyesconfig
<wpwrak> bah :(
<kyak> and it started to work fine
<kyak> if i was in console when inserting atusb, it would output masses and masses of messages to tty and then freeze
<wpwrak> a yes, masses of junk are always a bit of a problem
<wpwrak> sometimes i just add code to the end of the trace to disable interrupts and loop
<wpwrak> like this: http://pastebin.com/npRn7SxP
<kyak> these messages didn't end up with the "kernel panic" meesage
<kyak> or perhaps the "kernel panic" message was earlier?..
<wpwrak> hard to tell :)
<wpwrak> hrtimers make it 0.3% faster. must be something else then ... your kernel is SMP mine isn't. wonder if that is the difference.
<wpwrak> it's a scarily big switch, though
<wpwrak> ah, CONFIG_PREEMPT. let's see ...
<kyak> # CONFIG_USB_OHCI_HCD is not set - perhaps your's is set and it is using OHCI (just as guess)
<wpwrak> naw, i have an UHCI too
<wpwrak> does your CPU have HT ?
<wpwrak> CONFIG_PREEMPT made it some 0.06% faster :)
<wpwrak> hmm, you have CONFIG_IEEE802154_DRIVER_DEBUG=y
<wpwrak> that should slow things down quite a bit
<wpwrak> CONFIG_NO_HZ, 0.02% faster
<kyak> yeah, i thought about disabling *_DEBUG, will do it on next rebuild
<kyak> my laptop's CPU
<kyak> guess there is no HT
<wpwrak> CONFIG_TREE_PREEMPT_RCU makes it 0.3% faster
<wpwrak> oh, there is. it's SMP and HT.
<wpwrak> not such an ancient laptop then
<kyak> if i had four cores, would it be 4 times faster? :)
<wpwrak> twice at best. you already have two cores :)
<wpwrak> CONFIG_CGROUPS+CONFIG_CGROUP_SCHED make it slower again