00:27.11 | *** join/#neo900 freemangordon_ (~freemango@46.249.74.23) |
00:45.45 | *** join/#neo900 Herbstbert_ (~Herbstber@drms-4d0d9357.pool.mediaWays.net) |
00:52.34 | *** join/#neo900 Herbstbert_ (~Herbstber@drms-4d0d9357.pool.mediaWays.net) |
02:11.23 | *** join/#neo900 brentoo2 (~brent@99-18-21-45.lightspeed.rkwdmi.sbcglobal.net) |
03:43.18 | *** join/#neo900 brentoo (~brent@99-18-21-45.lightspeed.rkwdmi.sbcglobal.net) |
04:11.22 | *** join/#neo900 liteIRC_ (~ravelo@85-127-247-95.dynamic.xdsl-line.inode.at) |
07:10.29 | *** join/#neo900 luka (~luka@62.113.223.155) |
10:05.18 | *** join/#neo900 liteIRC_ (~ravelo@178-165-133-066.dyn.orange.at) |
10:06.42 | *** join/#neo900 joecool (~joecool@no-sources/joecool) |
10:54.10 | DocScrutinizer05 | we started evaluating our options regarding WLAN/BT module/chip. see http://projects.goldelico.com/p/neo900/issues/546/ |
10:55.34 | DocScrutinizer05 | please DONT post any questions or unevaluated suggestions resp requests to the tracker! there's http://talk.maemo.org/showthread.php?t=91142 for that, or you contact us here on IRC |
10:59.27 | *** join/#neo900 infobot (~infobot@rikers.org) |
10:59.27 | *** topic/#neo900 is http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ | 2013-11-04 - the day our fundraiser reached its goal, 25k EUR | 2013-12-02 - 200 devices reached! | 12-14 50035EUR, 232 units | Now heading for 1000 devices to build! |
10:59.27 | *** mode/#neo900 [+v infobot] by ChanServ |
11:25.24 | *** join/#neo900 xes (~xes@unaffiliated/xes) |
12:21.50 | *** join/#neo900 robotanarchy (~robotanar@f051049103.adsl.alicedsl.de) |
12:58.04 | *** join/#neo900 liteIRC_ (~ravelo@85-127-247-95.dynamic.xdsl-line.inode.at) |
13:19.38 | *** join/#neo900 dos11 (~dos@unaffiliated/dos1) |
13:33.10 | *** join/#neo900 sequantz (~sequantz@agbq53.neoplus.adsl.tpnet.pl) |
13:42.27 | *** join/#neo900 Guest18026 (~luka@unaffiliated/luka) |
13:48.20 | *** join/#neo900 thrakcattack (~pi@194-118-149-55.adsl.highway.telekom.at) |
15:03.27 | *** join/#neo900 liteIRC_ (~ravelo@091-141-004-020.dyn.orange.at) |
15:04.06 | *** join/#neo900 sequantz__ (~sequantz@agce250.neoplus.adsl.tpnet.pl) |
15:05.56 | *** join/#neo900 liteIRC__ (~ravelo@091-141-004-020.dyn.orange.at) |
15:09.31 | *** join/#neo900 liteIRC_ (~ravelo@77.119.0.160) |
15:21.55 | *** join/#neo900 nully (elisa@fsf/staff/nully) |
15:44.02 | *** join/#neo900 kolp (~quassel@212.255.123.161) |
15:44.21 | *** join/#neo900 liteIRC_ (~ravelo@213-240-74-83.adsl.highway.telekom.at) |
15:45.37 | *** join/#neo900 liteIRC__ (~ravelo@213-240-74-83.adsl.highway.telekom.at) |
16:01.58 | *** join/#neo900 liteIRC_ (~ravelo@213-240-74-83.adsl.highway.telekom.at) |
16:06.58 | *** join/#neo900 liteIRC_ (~ravelo@213-240-74-83.adsl.highway.telekom.at) |
16:50.37 | *** join/#neo900 ravelo (~ravelo@213-240-74-83.adsl.highway.telekom.at) |
16:54.43 | *** join/#neo900 sequantz (~sequantz@agce250.neoplus.adsl.tpnet.pl) |
17:07.36 | *** join/#neo900 liteIRC_ (~ravelo@091-141-005-217.dyn.orange.at) |
17:07.46 | *** join/#neo900 kratz00_work (~stpa2497@194.136.18.134) |
17:08.14 | *** join/#neo900 Hakki (~hakki@ip212-226-155-81.adsl.kpnqwest.fi) |
17:26.03 | *** join/#neo900 liteIRC_ (~ravelo@091-141-005-217.dyn.orange.at) |
17:39.42 | *** join/#neo900 brentoo (~brent@99-18-21-45.lightspeed.rkwdmi.sbcglobal.net) |
17:40.41 | *** join/#neo900 liteIRC_ (~ravelo@85-127-247-95.dynamic.xdsl-line.inode.at) |
17:47.27 | *** join/#neo900 NIN101 (~NIN@n900.quitesimple.org) |
22:08.03 | DocScrutinizer05 | hi dos1 |
22:08.28 | DocScrutinizer05 | seems we're still on an average at least of ~1 device per day |
22:08.31 | DocScrutinizer05 | :-D |
22:08.35 | dos1 | DocScrutinizer05: hello |
22:09.24 | dos1 | hmm, so 1000 in two years |
22:09.34 | DocScrutinizer05 | yeah ;-P |
22:09.35 | dos1 | a bit slow :P |
22:09.52 | DocScrutinizer05 | any comments on TiWi5 ? |
22:10.27 | dos1 | but 1 device per day without any bigger media coverage recently isn't that bad |
22:10.35 | DocScrutinizer05 | according to the specs Nikolaus posted it looks awesome |
22:10.53 | dos1 | yup |
22:11.15 | DocScrutinizer05 | alas has "blob" |
22:11.22 | DocScrutinizer05 | aka firmware binary |
22:11.27 | DocScrutinizer05 | ohwell |
22:11.39 | DocScrutinizer05 | (at least afaik) |
22:13.15 | DocScrutinizer05 | we can't get a flashable hackable hard&soft-MAC power conserving embedded WiFi chipset that also pleases FSF anyway, I guess |
22:13.53 | DocScrutinizer05 | I doubt such magic thing exists |
22:14.25 | DocScrutinizer05 | just like the magic FOSS WWAN modem doesn't exist, only a tiny bit less unlikely |
22:15.56 | DocScrutinizer05 | and in the end - 100% identical to GTA04 concept ;-) And nope, we won't build that MC to load the firmware to WLAN on Neo900 either ;-D |
22:20.37 | dos1 | datasheet just mentions "firmware download" in "the duration of t2 depends on:" |
22:22.32 | *** join/#neo900 Herbstbert (~Herbstber@drms-4d0d9357.pool.mediaWays.net) |
22:22.40 | dos1 | hehe, there's FM module, but it's unsupported and enabling pin is recommended to be grounded :D |
22:26.47 | dos1 | http://processors.wiki.ti.com/index.php/WL127x |
22:32.13 | *** join/#neo900 freemangordon_ (~freemango@46.249.74.23) |
22:38.02 | dos1 | DocScrutinizer05: does N9 use TiWi5, or some other wl1273-based module? |
22:38.48 | dos1 | aaah |
22:38.50 | dos1 | The FM radio is tested by TI at the WL1271 level, but not tested at the Module level by LS Research at the present time. Therefore LS Research assumes no liability for its operation. If this is a requirement for an application, please feel free to contact LS Research to discuss. Information on using the FM radio (again at a customers own risk) can be obtained from TI. For example see TI OMAP Wiki. |
22:42.24 | DocScrutinizer05 | dos1: wl1273 chipset |
22:43.26 | DocScrutinizer05 | dang, that radio detail is awesome |
22:43.40 | DocScrutinizer05 | link please! :-) |
22:44.07 | dos1 | http://www.lsr.com/ProductsWiki/tabid/163/loc/TopicHistory/ShowHistory/298/Default.aspx?topic=TiWi-R2%2C+TiWi-BLE%2C+TiWi5 |
22:44.28 | dos1 | first question in FAQ |
22:47.45 | DocScrutinizer05 | also see N9-schamtics "BOB" (page 9) |
22:54.09 | DocScrutinizer05 | great, thanks! |
22:54.30 | DocScrutinizer05 | seems I should add that to the ticket |
23:01.19 | dos1 | hehe, I'm always curious for abusing "not recommended" stuff :D |
23:03.11 | dos1 | though I guess there's no FM TX support on driver side, as it was written by Nokia |
23:04.08 | DocScrutinizer05 | I don't think the module *has* FMTX |
23:05.18 | dos1 | I think I saw it somewhere |
23:05.28 | DocScrutinizer05 | the only FMTX I know of is in N900 and that is done by a discrete chip and using a separate antenna(!) |
23:06.42 | dos1 | FM IP - RX /TX |
23:07.00 | dos1 | with two separate pins for FM Rx Antenna and FM Tx Antenna |
23:07.42 | dos1 | FM IP Active modes: |
23:07.44 | dos1 | FM IP OFF/Reset: When Bluetooth is used and FM is not required (BT_EN=H). |
23:07.45 | dos1 | FM TX: When FM is transmitting. FM (AFE) PM is entirely on. |
23:07.47 | dos1 | FM RX: When FM is receiving. FM (AFE) PM is entirely on. |
23:08.18 | dos1 | http://pdf.datasheetarchive.com/indexerfiles/Datasheet-082/DASF0044888.pdf |
23:08.33 | DocScrutinizer05 | http://processors.wiki.ti.com/index.php/WL127x_Hardware_Design_Guide#External_Interfaces |
23:08.44 | DocScrutinizer05 | DUH! |
23:22.30 | DocScrutinizer05 | dos1: check out FAQ 16) ;-D |
23:23.20 | dos1 | wlan test interface? |
23:24.45 | dos1 | WL_RS232_RX/TX |
23:24.53 | dos1 | hmm, sounds pretty hackable :D |
23:25.21 | DocScrutinizer05 | yeah, doesn't it? |
23:25.41 | DocScrutinizer05 | :-/ @ |
23:25.43 | DocScrutinizer05 | The Linux driver supports A2DP, HFP, HSP, OPP and FTP profiles. |
23:25.44 | DocScrutinizer05 | The Win CE driver supports SDP, SSP, OPP, FTP, DUN, PAN et AD2P. |
23:26.04 | DocScrutinizer05 | no DUN and no PAN? |
23:26.18 | DocScrutinizer05 | WTF?! |
23:26.41 | DocScrutinizer05 | they prolly missed out on sth there |
23:27.30 | dos1 | "However, the N9 doesn't support BT PAN. I've been trying (http://talk.maemo.org/showthread.php?t=82199) tho get PAN going, but didn't succeed so far. :(" |
23:29.27 | DocScrutinizer05 | DANG! |
23:29.46 | DocScrutinizer05 | so we should check for wl1251 of N900 |
23:30.00 | DocScrutinizer05 | since I think THIS chip CAN do |
23:30.22 | DocScrutinizer05 | I have a hard time to believe 1251 can do stuff 1273 can't |
23:31.00 | DocScrutinizer05 | dos1: welcome in the EE team ;-) |
23:31.27 | dos1 | \o/ |
23:31.28 | *** join/#neo900 josch_ (~josch@fulda116.server4you.de) |
23:31.28 | *** join/#neo900 josch_ (~josch@unaffiliated/josch) |
23:31.28 | dos1 | :D |
23:31.55 | DocScrutinizer05 | heads out for brinner |
23:32.06 | DocScrutinizer05 | shall I bring some for you too? |
23:33.09 | dos1 | nah thanks, I should go to sleep soon |
23:34.46 | dos1 | at least I'll try, as I rarely succeed and then I'm in zombie mode whole day |
23:36.03 | dos1 | it's hard to be rather night-shifted while having day studies and day job :x |
23:42.44 | DocScrutinizer05 | :nod: |
23:42.51 | DocScrutinizer05 | felt like this the whole day |
23:43.43 | dos1 | DocScrutinizer05: looks like bt DUN works on N9 |
23:43.53 | DocScrutinizer05 | mhm |
23:43.57 | DocScrutinizer05 | better should |
23:44.36 | dos1 | however I haven't found definitive proof |
23:44.59 | DocScrutinizer05 | I'm pretty sure that's a question of drivers |
23:45.07 | DocScrutinizer05 | and OS daemons |
23:45.14 | dos1 | yep |
23:45.37 | dos1 | more drivers, as OS daemons are rather easier to overcome |
23:45.54 | dos1 | Win CE driver supports both DUN and PAN |
23:46.33 | DocScrutinizer05 | nah, I guess on unix that's just a matter of route/bridge/whatever, and DUN just a thing like PNATD on a SER on BT |
23:47.13 | DocScrutinizer05 | IOW prolly every BT can do PAN and DUN, when the OS implements the needed bits on higher levels |
23:47.42 | DocScrutinizer05 | in the end I guess for PAN the BT is like MAC layer |
23:47.47 | DocScrutinizer05 | aka PHY |
23:48.44 | DocScrutinizer05 | and DUN is probably a simple serial to a modem speaking AT |
23:49.01 | DocScrutinizer05 | see DUN implementation on N900 |
23:49.07 | dos1 | ah, misunderstood you then :) |
23:50.08 | DocScrutinizer05 | it's probably not listed in the list of linux supported protocols siply because the wl12xx driver isn't responsible for doing it |
23:50.22 | DocScrutinizer05 | simply* |
23:51.07 | DocScrutinizer05 | though that's a lot of wild guessing on my side now |
23:51.17 | dos1 | hmm |
23:51.18 | dos1 | http://darkstarshout.blogspot.com/2012/08/nokia-n9-bluetooth-pan-usb-dummy.html |
23:51.29 | DocScrutinizer05 | anyway 1251 and 1273 should probably even share same kernel driver |
23:52.37 | *** join/#neo900 xes (~xes@unaffiliated/xes) |
23:54.33 | DocScrutinizer05 | yeah >>Fortunately, the N9 has a normal Linux userspace under the hood (one reason I'd take this over Android any day), which includes bluez 4.x and as such I was able to use that to make it do bluetooth PAN.<< |
23:55.25 | dos1 | yup |
23:55.45 | DocScrutinizer05 | http://darkstarshout.blogspot.de/2012/08/nokia-n9-bluetooth-pan-usb-dummy.html#blue_pan |
23:56.21 | dos1 | so tiwi5 looks pretty awesome |
23:58.23 | dos1 | I wonder if now there would be anyone willing to work on something like http://projects.goldelico.com/p/gta04-main/issues/310/ |
23:59.50 | DocScrutinizer05 | [2014-01-06 23:15:56] <DocScrutinizer05> and in the end - 100% identical to GTA04 concept ;-) And nope, we won't build that MC to load the firmware to WLAN on Neo900 either ;-D |