**** BEGIN LOGGING AT Fri Jul 31 02:59:59 2015
Jul 31 05:18:57 <R0b0t1> DocScrutinizer05: I looked at that, but it seems to just backup my settings
Jul 31 05:19:07 <R0b0t1> which, eh? maybe you meant something different
Jul 31 10:25:35 <R0b0t1> has anyone tried to RE nolo yet
Jul 31 10:28:35 <KotCzarny> http://talk.maemo.org/showthread.php?t=75504
Jul 31 10:28:39 <KotCzarny> this guy played with it
Jul 31 10:30:39 <R0b0t1> neat
Jul 31 10:31:11 <R0b0t1> any way to put u-boot on device not on the device?
Jul 31 10:31:22 <R0b0t1> through USB or something
Jul 31 10:32:12 <KotCzarny> http://wiki.maemo.org/Updating_the_firmware/Cold_Flashing
Jul 31 10:32:22 <KotCzarny> but look for u-boot threads if you must
Jul 31 10:32:32 <KotCzarny> ~uboot
Jul 31 10:32:32 <infobot> N900 uBoot is a siamese twin binary [uBoot+stockMaemoKernel] that resides in kernel NAND partition /dev/mtd3 aka "kernel". You can't uninstall it, rather you'll nuke it when you flash/install another kernel like stock maemo kernel or powerkernel. To start other than stock maemo kernel via uBoot, you have to provide the according kernel image files, or http://talk.maemo.org/showthread.php?t=81613
Jul 31 10:32:46 <KotCzarny> ~u-boot
Jul 31 10:32:46 <infobot> from memory, u-boot is http://talk.maemo.org/showthread.php?t=81613
Jul 31 10:34:02 <bencoh> "on device not on the device" ?
Jul 31 10:34:06 <R0b0t1> yeah I tried searching and couldn't find any of that stuff
Jul 31 10:34:12 <bencoh> what do you mean ?
Jul 31 10:34:15 <R0b0t1> I did get u-boot to compile successfully though!
Jul 31 10:34:27 <R0b0t1> bencoh: I mean, controlling the device via USB and not running commands on the device.
Jul 31 10:34:36 <KotCzarny> see above
Jul 31 10:34:43 <KotCzarny> especially cold boot wiki entry
Jul 31 10:34:53 <R0b0t1> I'm kind of miffed so much n900 development focuses on modifying the device from the device, that's the annoying way to do everything :\
Jul 31 10:34:58 <R0b0t1> yeah now that I know what they call it
Jul 31 10:35:07 <bencoh> I'd ask Pali about that
Jul 31 10:35:39 <bencoh> but I guess uboot can be treated like a regular "kernel" from nolo's point of view
Jul 31 10:35:49 <R0b0t1> yeah
Jul 31 10:36:04 <bencoh> and thus you might be able to just load uboot wih flasher or 0xffff
Jul 31 10:36:17 <bencoh> then again, Pali is probably your best bet :)
Jul 31 10:39:26 <R0b0t1> yeah I went to highlight him but he wasn't here
Jul 31 10:39:53 <R0b0t1> his kernel fork compiles though, which is far better than some of the devices I've used...
Jul 31 10:45:14 <KotCzarny> http://i.imgur.com/OK9ew.jpg
Jul 31 10:45:58 <KotCzarny> i shall make me some cat boot logo
Jul 31 10:46:29 <APic> Kudos.
Jul 31 10:58:40 <KotCzarny> this n900 is really awesome in the way you can even boot nolo via usb
Jul 31 10:58:46 <KotCzarny> with zeroed nand
Jul 31 10:59:23 <APic> Yes.
Jul 31 10:59:34 <APic> Metafallbacks.  B-)
Jul 31 11:00:13 <Luke-Jr> what? if NAND is zeroed, then NOLO is gone, isn't it?
Jul 31 11:00:25 <KotCzarny> yes, but you can make it boot nolo via usb
Jul 31 11:00:36 <KotCzarny> unless i misread the thread
Jul 31 11:00:51 <KotCzarny> luke-jr: http://wiki.maemo.org/Updating_the_firmware/Cold_Flashing
Jul 31 11:01:23 <Luke-Jr> Oh O.o
Jul 31 11:10:46 <bencoh> yes, this device is awesome :)
Jul 31 11:13:27 <Luke-Jr> was*
Jul 31 11:13:34 <KotCzarny> IS
Jul 31 11:13:44 <Luke-Jr> sorry, N900 is dead
Jul 31 11:13:53 <bencoh> noooo! :)
Jul 31 11:14:12 <Luke-Jr> https://pbs.twimg.com/media/CK1B8zpWIAANAIx.jpg:orig
Jul 31 11:14:12 * KotCzarny checks, nope, alive and doing what i want it to do
Jul 31 11:14:35 <bencoh> Luke-Jr: yeah, just not the size form-factor though
Jul 31 11:14:40 <Luke-Jr> it's better :P
Jul 31 11:14:55 <Luke-Jr> N900's size/form-factor has always been one of its weaknesses
Jul 31 11:14:56 <bencoh> but yeah, might be going for pyra too (not as a replacement)
Jul 31 11:14:56 <KotCzarny> but its ugly
Jul 31 11:14:58 <KotCzarny> :)
Jul 31 11:15:12 <KotCzarny> n900 size is ok
Jul 31 11:15:20 <KotCzarny> keyboard could be bigger a bit
Jul 31 11:15:22 <KotCzarny> but its ok
Jul 31 11:15:27 <Luke-Jr> I miss my Zaurus keyboard.
Jul 31 11:15:34 <Luke-Jr> I hope Pyra's is comparable.
Jul 31 11:15:40 <bencoh> a bit too thick, and screen is small by today's standards, but ...
Jul 31 11:15:44 <KotCzarny> i miss my thinkpads keyboard on everything
Jul 31 11:16:14 <bencoh> Luke-Jr: all the layouts look horrible ... I dunno what they're going to release, but ... ^^
Jul 31 11:16:21 <bencoh> (pyra I mean)
Jul 31 11:17:24 <Luke-Jr> final kb layout: http://boards.openpandora.org/uploads/post-1-0-88080100-1438221841.jpg
Jul 31 11:18:05 <KotCzarny> do they have 1point click or are sliding down?
Jul 31 11:18:16 <KotCzarny> i hate those cheap keycaps that wiggle
Jul 31 11:18:18 <Luke-Jr> KotCzarny: I don't understand that question
Jul 31 11:20:13 <bencoh> Luke-Jr: meh ESC at the top
Jul 31 11:20:58 <KotCzarny> +1 bencoh
Jul 31 11:21:10 <Luke-Jr> at least it should all be remappable
Jul 31 11:21:10 <KotCzarny> but at least its there
Jul 31 11:21:30 <bencoh> yeah
Jul 31 11:21:32 * Luke-Jr wonders if N900 even has an Esc, since he never uses it..
Jul 31 11:21:41 <bencoh> n900 has no esc key
Jul 31 11:22:07 <R0b0t1> Luke-Jr: what is
Jul 31 11:22:08 <KotCzarny> i think its fn-ctrl
Jul 31 11:22:08 <Luke-Jr> if I was going to complain, I think it'd be at the Ctrl key being so far from the thumbs
Jul 31 11:22:10 <bencoh> mine is remapped to Fn+{the key next to backspace}
Jul 31 11:22:14 <KotCzarny> or shift ctrl
Jul 31 11:22:15 <Luke-Jr> R0b0t1: ?
Jul 31 11:22:20 <R0b0t1> http://boards.openpandora.org/uploads/post-1-0-88080100-1438221841.jpg
Jul 31 11:22:22 <bencoh> Luke-Jr: that too
Jul 31 11:22:30 <Luke-Jr> R0b0t1: Pyra
Jul 31 11:22:30 <bencoh> R0b0t1: pyra
Jul 31 11:22:41 <KotCzarny> last time i booted rescueos it was mapped there
Jul 31 11:22:50 <bencoh> Luke-Jr: oO didn't see it was in the middle oO
Jul 31 11:22:54 <KotCzarny> and then found it on n900
Jul 31 11:22:56 <bencoh> seriously ...
Jul 31 11:23:03 <Luke-Jr> as much as I like what they did with the editing keys, I might decide to remap those to Ctrl/Alt
Jul 31 11:23:48 <bencoh> KotCzarny: fn+ctrl is "compose"
Jul 31 11:23:56 <bencoh> shift+ctrl doesnt do anything special here
Jul 31 11:24:13 <KotCzarny> maybe its in console only 
Jul 31 11:24:14 <bencoh> I guess it's in rescueOS only
Jul 31 11:24:21 <bencoh> or console
Jul 31 11:25:35 <R0b0t1> pyra looks pretty good
Jul 31 11:26:00 <bencoh> woot marxian just released a RSS reader <3
Jul 31 11:26:34 <Luke-Jr> Pyra's biggest flaw seems to be void of cameras
Jul 31 11:28:01 <bencoh> and size (doesnt fit in your pocket)
Jul 31 11:28:21 <R0b0t1> I'd say it's competing with something like the nvidia shield
Jul 31 11:28:24 <R0b0t1> it doesn't need to
Jul 31 11:28:33 <R0b0t1> but it'd be neat if they could get something that works in a smaller formfactor
Jul 31 11:29:20 <bencoh> and it doesnt slide ... but that's an issue only if you think of it as a phablet on steroids (which it's probably not)
Jul 31 11:31:50 <Luke-Jr> bencoh: what? Pyra should fit in pockets, I think?
Jul 31 11:32:42 <R0b0t1> large pockets. might be tight in a lot of jeans
Jul 31 11:38:05 <bencoh> a really large one
Jul 31 11:38:15 <bencoh> wont fit in mine
Jul 31 11:38:25 <bencoh> or the backpocket maybe
Jul 31 11:38:27 <KotCzarny> i dont mind clam designs
Jul 31 11:39:52 <R0b0t1> dangit
Jul 31 11:40:03 <R0b0t1> I think I'll have to wait for pali, all of these guides gloss over a lot of stuff
Jul 31 11:40:21 <KotCzarny> learn. read. try.
Jul 31 11:40:35 <bencoh> R0b0t1: might be time for a spare n900 :]
Jul 31 11:40:40 <R0b0t1> well I know enough that I'd just be flailing blindly at this point
Jul 31 11:41:00 <R0b0t1> sadly I don't have easy access to a serial terminal to be able to control the system like on my other devboards
Jul 31 11:41:21 <bencoh> there is a way for that, but ...
Jul 31 11:41:30 <KotCzarny> ...
Jul 31 11:41:38 <KotCzarny> i've pasted n900's serial pinout before
Jul 31 11:41:46 <KotCzarny> you dont even check those links, do you?
Jul 31 11:41:58 <bencoh> https://wiki.maemo.org/N900_Hardware_Hacking
Jul 31 11:42:11 <KotCzarny> yup, pasted it few days ago for the same question
Jul 31 11:42:15 <R0b0t1> I do
Jul 31 11:42:20 <R0b0t1> I don't want to have to open it up
Jul 31 11:42:21 <R0b0t1> ;-;
Jul 31 11:42:34 <R0b0t1> "easy access"
Jul 31 11:42:37 <R0b0t1> not "any access"
Jul 31 11:43:35 <bencoh> you dont need to "open it up" but it's still not "easy", and you need a level shifter
Jul 31 11:43:38 <bencoh> (or a 1.8V ttl)
Jul 31 11:44:50 <bencoh> I wouldn't play with that
Jul 31 11:45:13 <KotCzarny> especially that once can have easy usb networking
Jul 31 11:45:18 <KotCzarny> *one
Jul 31 11:45:34 <KotCzarny> or fbconsole
Jul 31 11:45:47 <bencoh> KotCzarny: fbconsole/usbnet in ... bootloader stage ? :D
Jul 31 11:46:01 <bencoh> he wants to reverse nolo and/or play with uboot ;)
Jul 31 11:46:18 <KotCzarny> not only that
Jul 31 11:46:40 <KotCzarny> but for nolo, its just poking in the dark
Jul 31 11:46:44 <KotCzarny> unless you know arm asm
Jul 31 11:47:26 <R0b0t1> I have a 1.8V tty. If I can find some springy pins laying around, I'll use those so I don't have to solder to the pads.
Jul 31 11:50:29 <KotCzarny> or make 'connector' from cut plastic/wood with holes
Jul 31 11:56:59 <Luke-Jr> if Pyra works out for me, I'll probably be willing to sell my spare N900
Jul 31 13:55:17 <R0b0t1> jeb
Jul 31 13:55:18 <R0b0t1> ffffff
Jul 31 18:50:23 <stryngs> For monitor mode on the n900, is there a way to keep the NIC able to connect and associate with an AP?
Jul 31 18:50:33 <stryngs> I know the current way does modprobe and such to enable the hacked driver
Jul 31 18:50:41 <stryngs> Was curious on thoughts to enable both?
Jul 31 18:51:02 <L29Ah> use the fresh kernel ;)
Jul 31 18:51:56 <stryngs> frsh kernel?
Jul 31 18:52:00 <stryngs> What do u  mean?
Jul 31 18:52:02 <stryngs> kp is what i have now
Jul 31 18:52:26 <stryngs> kp53 is most recent, yes?
Jul 31 18:52:34 <KotCzarny> he means 4.x
Jul 31 18:53:50 <stryngs> Hmm
Jul 31 18:53:57 <stryngs> I'm using: kernel-power-flasher_2.6.28-10power53_armel.deb
Jul 31 18:53:59 <stryngs> Right now
Jul 31 18:54:04 <stryngs> Are u saying I should use something else?
Jul 31 18:54:20 <stryngs> kernelpower-bootimg, flasher, headers, modules
Jul 31 19:10:10 <Pali> stryngs: kp53 contains also "hacked" wlan module
Jul 31 19:10:18 <Pali> ~packet-injection
Jul 31 19:10:28 <Pali> bah infobot is dead
Jul 31 19:10:30 <stryngs> Right
Jul 31 19:11:01 <stryngs> Pali: What I was wondering, is, if there is a way to enable monitor mode via iw 
Jul 31 19:11:12 <stryngs> versus having to run the script and modprobe the modules
Jul 31 19:11:22 <Pali> stryngs: with packet injection modules, answer is yes
Jul 31 19:11:38 <Pali> you need to unload normal and load packet injection modules
Jul 31 19:11:43 <stryngs> Right
Jul 31 19:11:55 <stryngs> And those modules, they take away the ability to connect to an access point, correct?
Jul 31 19:11:56 <Pali> but now in kp53 should be packet injection module stable for everyday use
Jul 31 19:12:25 <Pali> no, packet injection modules are just backported wl1251 modules from upstream kernel to 2.6.28
Jul 31 19:12:42 <stryngs> So that leads me to two questions now:
Jul 31 19:12:54 <stryngs> Monitor Mode/Packet Injection mode, EATS up the battery life
Jul 31 19:13:01 <stryngs> You're saying they are stable for normal use?
Jul 31 19:13:24 <Pali> in kp52 packet inkection wl1251 module sometimes crashed kernel
Jul 31 19:13:30 <Pali> in kp53 this should be fixed
Jul 31 19:13:56 <stryngs> Ok, perhaps I need to play around with how I'm enabling monitor mode then
Jul 31 19:14:08 <stryngs> Do you have the URL for the most current and proper way to load the modules Pali ?
Jul 31 19:14:14 <stryngs> I know yer the author and all =)
Jul 31 19:14:21 <Pali> monitor mode of course will eat more battery then normal managed mode
Jul 31 19:14:30 <stryngs> Right
Jul 31 19:14:40 <stryngs> I thought the simple act of modprobing the hacked drivers is what caused the drain
Jul 31 19:14:53 <Pali> but normal mode of packed injestion wl1251 module should use same battery as stock module
Jul 31 19:15:06 <Pali> no it should not
Jul 31 19:15:12 <stryngs> Ok, very cool
Jul 31 19:15:15 <DocScrutinizer05> ~botsnack
Jul 31 19:15:15 <infobot> DocScrutinizer05: thanks
Jul 31 19:15:26 <stryngs> And the location for directions on enabling injection and drivers Pali ?
Jul 31 19:15:30 <Pali> but if you ifconfig wlan0 up then it will eat battery
Jul 31 19:15:38 <DocScrutinizer05> ~listkeys inject
Jul 31 19:15:40 <infobot> Factoid search of 'inject' by key (3): cmd: inject (.*?) ;; inject a robot who's sole job it ;; hot beef injection.
Jul 31 19:16:08 <Pali> there is some problem in wlancond/ic2/... when wl1251 is loaded *after* starting that daemons they can eat more battery
Jul 31 19:16:20 <DocScrutinizer05> ~forget inject a robot who's sole job it
Jul 31 19:16:21 <infobot> i forgot inject a robot who's sole job it, DocScrutinizer05
Jul 31 19:16:25 <Pali> and there is another thing: you need wlancond from CSSU
Jul 31 19:16:35 <stryngs> Hmm
Jul 31 19:16:43 <Pali> otherwise there will be battery drain with packed injected wl1251 module
Jul 31 19:16:47 <stryngs> Can i just straight dpkg -i the .deb?
Jul 31 19:16:54 <Pali> yes, that is enough
Jul 31 19:17:04 <Pali> just need to use fixed wlancond binary
Jul 31 19:17:04 <stryngs> I don't use cssu because of how my file system is laid out
Jul 31 19:17:15 <stryngs> Copy, so I've a new .deb to add to the mix, fun =)
Jul 31 19:17:30 <Pali> here is script for loading packet-injection: http://atrey.karlin.mff.cuni.cz/~pali/packet-injection.sh
Jul 31 19:17:39 <stryngs> Copy that
Jul 31 19:17:45 <stryngs> And the url for the wlancond.deb I should use?
Jul 31 19:17:49 <Pali> w8
Jul 31 19:18:11 <DocScrutinizer05> wlan chip eats LOTS of power when in scanning mode
Jul 31 19:18:34 <DocScrutinizer05> that's the reason why there's a setting "interval to search for APs"
Jul 31 19:18:44 <Pali> http://repository.maemo.org/community/pool/fremantle/free/o/osso-wlan/osso-wlan_3.0.20.1%2b0cssu2_armel.deb
Jul 31 19:19:20 <Pali> DocScrutinizer05: maemo system for scanning doing: ifconfig wlan0 up; scan; ifconfig wlan0 down
Jul 31 19:19:32 <Pali> even up-ed interface eat battery
Jul 31 19:19:50 <DocScrutinizer05> and ideally you should set interval to "never" when you leave home and don't want to waste battery on wlan chip uselessly searching for APs 
Jul 31 19:19:57 <Pali> and when you "switch" drivers there can be problem and system stay in "up" state forever
Jul 31 19:20:01 <Pali> or in down state forever
Jul 31 19:20:02 <stryngs> Hehe
Jul 31 19:20:20 <stryngs> Note for ya'll:  Having it search for APs == seg fault for most packet injection / monitor mode programs on the n900
Jul 31 19:20:27 <Pali> stryngs: package name is osso-wlan, see link up ^^^
Jul 31 19:20:28 <stryngs> As soon as it searches, segfault
Jul 31 19:20:33 <stryngs> Already grabbed it Pali
Jul 31 19:20:46 <stryngs> I'll Be playing with it tonight
Jul 31 19:20:47 <stryngs> I'm excited
Jul 31 19:21:12 <Pali> if there are any problems with packet injection wl1251 module from kp53, please report ir
Jul 31 19:21:14 <Pali> *it
Jul 31 19:21:49 <stryngs> Sure
Jul 31 19:21:56 <stryngs> But the problem is just the way the scanning works is all
Jul 31 19:21:56 <Pali> stryngs: here is also dbg and doc package (in case you need them too): http://repository.maemo.org/community/pool/fremantle/free/o/osso-wlan/
Jul 31 19:22:19 <stryngs> As soon as it sends probe requests looking for known APs it has connected to before, it kills whatever was using monitor/injection
Jul 31 19:22:20 <DocScrutinizer05> btw wlan AP scan also causes dropouts on BT A2DP aka "listening to music"
Jul 31 19:22:46 <Pali> ideally via my packet-injection.sh script set to packet injection modules to load at startup
Jul 31 19:22:49 <Pali> and reboot device
Jul 31 19:23:05 <Pali> and after that do tests (because of that up/down conflicts)
Jul 31 19:23:12 <stryngs> Interesting Pali, I never knew the drivers were stable like that
Jul 31 19:23:16 <Pali> DocScrutinizer05: is there any way for fixing that problem
Jul 31 19:23:22 <stryngs> I'd just always assumed it was a bug for having monitor mode capabilities
Jul 31 19:23:22 <DocScrutinizer05> set wlan ap scan time to 5min and you can adjust your clock to the headset dropouts every 300s
Jul 31 19:23:28 <Pali> a2dp vs scan
Jul 31 19:23:32 <DocScrutinizer05> Pali: I guess no
Jul 31 19:23:36 <stryngs> Right, but just so ya'll know:
Jul 31 19:23:43 <stryngs> "load injection capabilities"
Jul 31 19:23:47 <DocScrutinizer05> Pali: prlly introduced by hardwired coexistence
Jul 31 19:23:49 <stryngs> "iwconfig wlan0 channel 6"
Jul 31 19:23:57 <stryngs> "tcpdump -i wlan0 -lnX -s0"
Jul 31 19:24:03 <stryngs> As SOON as it probes, tcpdump dies
Jul 31 19:24:08 <stryngs> because iface wlan0 goes down
Jul 31 19:24:22 <stryngs> And this IS due to the probing
Jul 31 19:24:25 <stryngs> It's not a worry
Jul 31 19:24:36 <stryngs> Just know that u can't have probing enabled when yer playing monitor mode
Jul 31 19:24:37 <Pali> stryngs: you need to turn of that autoscan in systemsettings
Jul 31 19:24:43 <stryngs> Oh, I do.
Jul 31 19:24:51 <stryngs> I just wasn't sure if ya'll were aware =)
Jul 31 19:24:54 <stryngs> THat's all =)
Jul 31 19:24:57 <Pali> DocScrutinizer05: that problem will be there also in neo900?
Jul 31 19:25:20 <stryngs> Ofc Pali 
Jul 31 19:25:23 <DocScrutinizer05> good question. Might actually occur in Neo900 too
Jul 31 19:25:28 <stryngs> It will occur
Jul 31 19:25:31 <Pali> aaah no :-(
Jul 31 19:25:35 <stryngs> You cannot send probe requests
Jul 31 19:25:41 <stryngs> period.
Jul 31 19:25:56 <stryngs> Just know u turn off autoscan is all
Jul 31 19:25:58 <stryngs> =)
Jul 31 19:26:00 <DocScrutinizer05> but the WLAN module in Neo is more advanced than the one in N900, so maybe they fixed that issue
Jul 31 19:26:04 <stryngs> Hmm
Jul 31 19:26:09 <stryngs> Interesting to see DocScrutinizer05 
Jul 31 19:26:52 <stryngs> I do love the fact that people hate on my n900, but yet bitch when all the sudden they are de-auth'd from the wifi....
Jul 31 19:27:01 <stryngs> "My smartphone can kick your smartphones ass"
Jul 31 19:27:06 <stryngs> That's what I tell em =)
Jul 31 19:28:21 <DocScrutinizer05> Pali: I'm not completely sure if it could get fixed by not having any "anonymous" (hidden SSID) APs configured. Basically I suspect only WLAN TX would cause BT dropouts and TX is not needed when the WLAN doesn't need to ping an anonymous AP and ask "are you FOOBAR?"
Jul 31 19:29:48 <DocScrutinizer05> Pali: also the WLAN/BT integration on Neo900 is way tighter than on N900
Jul 31 19:30:06 <Pali> DocScrutinizer05: on my laptop I have one bt/wifi chip on one half-mini-pcie card
Jul 31 19:30:13 <Pali> and I do not see this problem
Jul 31 19:30:24 <stryngs> So... Pali, on my n900, after looking at it, I do not, nor have I ever installed the osso-wlan_3.0.20.1%2b0cssu2_armel.deb.  You're saying the benefit to this package is that it will help battery life?
Jul 31 19:30:33 <DocScrutinizer05> yep, I think it's actually a bug in N900 wlan/bt firmware
Jul 31 19:30:54 <Pali> stryngs: osso-wlan is needed for battery life of packet injection drivers
Jul 31 19:31:09 <stryngs> Very cool!
Jul 31 19:31:31 <stryngs> That was the thing I hated with the current rig I have.  As soon as I enable monitor mode, even if I disable it later on, the battery gets eaten
Jul 31 19:31:39 <stryngs> Have to turn it off and on again to prevent it
Jul 31 19:31:42 <Pali> DocScrutinizer05: anyway, in n900 there is one chip (from TI) for wifi and one (from broadcom) for BT+FM
Jul 31 19:32:16 <DocScrutinizer05> yes
Jul 31 19:32:18 <Pali> so maybe bug in TI or broadcom firmware...
Jul 31 19:32:24 <DocScrutinizer05> yes
Jul 31 19:32:30 <Pali> or maybe problem just because it is not one chip?
Jul 31 19:32:51 <DocScrutinizer05> on Neo900 both chips will be in same module, same manuf, maybe even same chip
Jul 31 19:33:02 <Pali> that sounds better
Jul 31 19:33:18 <Pali> all WIFI+BT+FM_RX+FM_TX?
Jul 31 19:33:23 <DocScrutinizer05> yep
Jul 31 19:33:31 <DocScrutinizer05> unless we can't source the module
Jul 31 19:33:34 <DocScrutinizer05> :-/
Jul 31 19:34:02 <DocScrutinizer05> recently has 20 weeks lead time
Jul 31 19:34:08 <Pali> will be there same fuckup like on n900... when you enable fm rx it also start bluetooth?
Jul 31 19:34:27 <DocScrutinizer05> yes, sort of
Jul 31 19:34:37 <DocScrutinizer05> they share same interface
Jul 31 19:35:02 <DocScrutinizer05> that however doesn't mean BT us *up*
Jul 31 19:35:05 <DocScrutinizer05> is*
Jul 31 19:35:05 <Pali> but can be any of those 4 parts disabled/enabled separately?
Jul 31 19:35:24 <DocScrutinizer05> they all can get enabled/disabled separately
Jul 31 19:35:26 <Pali> or when FM_RX is up also BT must be up?
Jul 31 19:35:32 <Pali> ok, thats enough
Jul 31 19:35:54 <DocScrutinizer05> they just share same interface and thus BT interface needs power to work
Jul 31 19:36:04 <DocScrutinizer05> that doesn't mean BT TX is enabled
Jul 31 19:36:45 <stryngs> heh
Jul 31 19:36:48 <stryngs> 900+ eur
Jul 31 19:36:54 <stryngs> It'll be an insane price to pay
Jul 31 19:36:56 <stryngs> But.. I will =)
Jul 31 19:38:51 <DocScrutinizer05> (source the module) there are other almost identical modules, but they usually don't (officially) support the FM, either TX or even both
Jul 31 19:40:40 <DocScrutinizer05> would suck if we need a separate chip for FM (like in N900) just because they didn't solder the antenna pins of the chip inside their WLAN module
Jul 31 19:41:34 <DocScrutinizer05> some modules are known to work just fine for FM despite it's not even mentioned as feature in the module datasheet
Jul 31 19:41:50 <DocScrutinizer05> possibly a certification thing too
Jul 31 19:42:49 <DocScrutinizer05> afk o/
Jul 31 19:43:04 <stryngs> Pali: Thanks for the help today
Jul 31 19:43:22 <stryngs> Pali: I run monitor mode quite frequently, so if I see a bug with the way things go, I'll be the first to let u know
Jul 31 19:46:18 <Pali> ok
Jul 31 19:55:47 <DocScrutinizer05> Ticket system re-opens Friday, 2015-07-31, 22:00 CEST      https://events.ccc.de/2015/07/30/tickets-2/   5min
**** ENDING LOGGING AT Sat Aug 01 02:59:58 2015