**** BEGIN LOGGING AT Tue Sep 14 02:59:57 2010
Sep 14 06:42:25 <mickeyl> will be back on 30th, c'ya.
Sep 14 06:43:16 <PaulF> :-O
Sep 14 06:43:38 <PaulF> Holiday trip? :)
Sep 14 09:44:58 <daniele_athome> morning
Sep 14 09:53:15 <daniele_athome> what version of vala does the shr buildhost use?
Sep 14 12:04:57 <badcloud> anyone see dos1 lately?
Sep 14 12:05:19 <soltys> he's at school propably ;)
Sep 14 12:10:13 <badcloud> soltys: good guess
Sep 14 12:13:26 <soltys> ;)
Sep 14 12:20:26 <daniele_athome> gitorious is down :(
Sep 14 12:21:55 <badcloud> is there any way to find out which bootloader image I'm using?
Sep 14 12:22:43 <badcloud> I'm trying to find out which one I'm using from those at this link http://dos.openmoko.pl/overclock/
Sep 14 12:23:25 <lindi-> badcloud: you can cat it
Sep 14 12:23:49 <badcloud> what's the location if I flashed it?
Sep 14 12:24:34 <lindi-> badcloud: /dev/mtdblock1?
Sep 14 12:26:55 <badcloud> lindi-: that gives me lots of giberish
Sep 14 12:30:02 <lindi-> badcloud: that's what binaries look like
Sep 14 12:32:53 <badcloud> yeah, I got that from 'cat /dev/mtdblock1|grep qi' ;P
Sep 14 12:32:58 <badcloud> so what do I do then?
Sep 14 12:34:09 <badcloud> do I need to translate it to ascii somehow (intuition+ignorance=funny and dumb questions)?
Sep 14 12:49:02 <badcloud> lindi-: found it. Qi Bootloader s3c2442  sowa master_c38b062a609f1442 
Sep 14 12:49:26 <badcloud> lindi-: but 'c38b062a609f1442' corresponds with all of the images on the link
Sep 14 12:51:20 <lindi-> badcloud: the link?
Sep 14 12:52:06 <badcloud> http://dos.openmoko.pl/overclock/
Sep 14 12:52:26 <lindi-> well, ask dos? ;)
Sep 14 12:52:38 <lindi-> badcloud: you can just compare the binaries instead of looking at plaintext strings
Sep 14 12:52:42 <badcloud> waiting for him to show :)
Sep 14 12:54:24 <gena2x> badcloud: again, i recommend you to use glamo 2-4-2 instead
Sep 14 12:54:33 <lindi-> badcloud: if you have omhacks you can use it to see the timings
Sep 14 12:54:48 <lindi-> ah it was about overclocking
Sep 14 12:54:48 <gena2x> ah
Sep 14 12:54:51 <gena2x> yes
Sep 14 12:55:06 <badcloud> gena2x: didn't you say there isn't a qi image with that?
Sep 14 12:55:25 <gena2x> you can use overcked image + lindi's omhacks tool
Sep 14 12:55:32 <gena2x> this will be fastest
Sep 14 12:55:46 <lindi-> badcloud: 'om screen glamo-bus-timings 2-4-2'
Sep 14 12:55:51 <lindi-> but it's not in debian unstable yet
Sep 14 12:55:57 <lindi-> (that particular option)
Sep 14 12:56:03 <badcloud> lindi-: aaah
Sep 14 12:56:20 <lindi-> squeeze is kind of frozen now
Sep 14 12:56:51 <badcloud> gena2x: it's just that my u-boot is broken
Sep 14 12:57:05 <badcloud> so I'm using qi
Sep 14 12:57:06 <gena2x> broken?
Sep 14 12:57:12 <badcloud> what yes
Sep 14 12:57:17 <badcloud> *yes
Sep 14 12:57:24 <gena2x> what's wrong with it?
Sep 14 12:57:34 <badcloud> if I flash uboot
Sep 14 12:57:55 <badcloud> I see nand boot text
Sep 14 12:57:59 <badcloud> "poweroff"
Sep 14 12:58:02 <badcloud> nothing but that
Sep 14 12:58:19 <gena2x> you should prepare and flash environment
Sep 14 12:58:30 <badcloud> gena2x: how
Sep 14 12:58:38 <gena2x> use devirginator too
Sep 14 12:58:40 <gena2x> *tool
Sep 14 12:58:52 <gena2x> http://svn.openmoko.org/trunk/src/host/devirginator/
Sep 14 12:59:01 <gena2x> it has envedit.pl
Sep 14 12:59:10 <badcloud> I tried that. got stuck along the way. I'll tell you exactly at which stage in one sec
Sep 14 12:59:10 <gena2x> and sample config environment.in
Sep 14 13:00:15 <badcloud> gena2x: oh wait, don't I need jtag for that?
Sep 14 13:00:43 <gena2x> edit it, ./envedit.pl -f environment.in -s 262144 > env.new
Sep 14 13:01:06 <gena2x> then sudo dfu-util -a u-boot_env -D env.new
Sep 14 13:01:13 <gena2x> and that's all.
Sep 14 13:01:26 <gena2x> no of course
Sep 14 13:01:37 <gena2x> no jtag
Sep 14 13:01:54 <gena2x> this is just one tool to cook uboot env
Sep 14 13:01:56 <badcloud> I'll try now
Sep 14 13:03:57 <badcloud> gena2x: done
Sep 14 13:04:08 <badcloud> so which u-boot image did you recommend
Sep 14 13:04:10 <gena2x> should work
Sep 14 13:04:18 <gena2x> wait a bit...
Sep 14 13:05:11 <badcloud> sure
Sep 14 13:06:43 <gena2x> badcloud: www.bsdmn.com/openmoko/glamo/242/u-boot_440_glamo242.udfu
Sep 14 13:06:48 <gena2x> for overclocked
Sep 14 13:07:23 <gena2x> and if it will not work (kernel crashes, no menu at all), www.bsdmn.com/openmoko/glamo/242/u-boot_glamo242.udfu
Sep 14 13:07:52 <gena2x> 440 has unchanged memory voltage
Sep 14 13:08:24 <gena2x> and cpu too
Sep 14 13:09:53 <badcloud> gena2x: same deal, "poweroff" at the top, horizontal colorful segmented line along the bottom third of screen
Sep 14 13:10:18 <gena2x> ah, try POWER+AUX
Sep 14 13:10:42 <gena2x> while booting default it try to load picture from nand
Sep 14 13:10:55 <gena2x> with power+aux you should be menu
Sep 14 13:12:23 <gena2x> *get
Sep 14 13:12:50 <mrmoku> DocScrutinizer, GNUtoo|laptop: I have SHR running without r&d mode :)
Sep 14 13:12:56 <badcloud> gena2x: any idea what's wrong?
Sep 14 13:13:03 <DocScrutinizer> mrmoku: :-D
Sep 14 13:13:09 <DocScrutinizer> kick wd?
Sep 14 13:13:26 <mrmoku> correct watchdog.conf... 
Sep 14 13:13:35 <mrmoku> actually two confs
Sep 14 13:13:45 <DocScrutinizer> err, that's a SHR specific?
Sep 14 13:13:48 <mrmoku> and starting watchdog and wd_keepalive
Sep 14 13:14:06 <mrmoku> don't think so... as I got it from ele...'s site ;)
Sep 14 13:14:59 <DocScrutinizer> hmm, I gather watchdog and wd_keepalive are /etc/init.d ?
Sep 14 13:15:06 <GNUtoo|laptop> mrmoku, nice!
Sep 14 13:15:26 <mrmoku> DocScrutinizer: yep
Sep 14 13:16:11 <DocScrutinizer> yep, nothing like that in maemo
Sep 14 13:16:15 <badcloud> gena2x: how would I do that, load picture from nand?
Sep 14 13:17:07 <DocScrutinizer> I'd be highly interested in the one interesting line in those scripts - is it "echo foobar > /dev/watchdog_foo"?
Sep 14 13:17:46 <mrmoku> DocScrutinizer: ahh, then I misunderstood your /etc/init.d... watchdog and wd_keepalive are two daemons that are started
Sep 14 13:17:51 <DocScrutinizer> badcloud: see people.om.org/joerg/dontpanic
Sep 14 13:18:14 <DocScrutinizer> mrmoku: no scripts? o.O
Sep 14 13:18:20 <mrmoku> no
Sep 14 13:18:27 <DocScrutinizer> blah
Sep 14 13:18:31 <mrmoku> http://www.matthew.ath.cx/cgi-bin/man/man2html?8+watchdog
Sep 14 13:18:50 <badcloud> DocScrutinizer: bad link
Sep 14 13:19:11 <DocScrutinizer> badcloud: it's an insider hint, no link :-D
Sep 14 13:20:04 <DocScrutinizer> kkk, won't fsck with u. mompl
Sep 14 13:20:27 <DocScrutinizer> http://people.openmoko.org/joerg/bootsplash/
Sep 14 13:20:56 <DocScrutinizer> has very terse howto
Sep 14 13:21:32 <badcloud> ?
Sep 14 13:21:45 <DocScrutinizer> btw, now some guys in maemo are picking up ACI to get rid of maemo PA madness :-D
Sep 14 13:22:43 <DocScrutinizer> so after 2+ years it seems there'll be at least a minimal result from my ALSA digging the mud
Sep 14 13:22:54 <mrmoku> :)
Sep 14 13:22:55 <misc> aci ?
Sep 14 13:23:09 <DocScrutinizer> http://people.openmoko.org/joerg/ALSA/ACI/
Sep 14 13:23:50 <DocScrutinizer> esp acihooklib there
Sep 14 13:25:16 <DocScrutinizer> which allows to found a completely integrated better-maybe audio management on it, than all PA policy enforcer and libcanberra and whatnot
Sep 14 13:25:54 <badcloud> DocScrutinizer: ah, just got it, *wink wink*
Sep 14 13:27:17 <mrmoku> GNUtoo|laptop: hmm... there are no /dev/mmcblk* nodes ?
Sep 14 13:27:22 <gena2x> badcloud: you should just place it to special nand partition
Sep 14 13:27:38 <GNUtoo|laptop> mrmoku, there are
Sep 14 13:27:52 <GNUtoo|laptop> mrmoku, /dev/mmcblk1p1 for instance
Sep 14 13:27:57 <GNUtoo|laptop> or mmcblk0p1
Sep 14 13:27:59 <GNUtoo|laptop> but beware
Sep 14 13:28:05 <GNUtoo|laptop> we should use bootloader stuff
Sep 14 13:28:19 <GNUtoo|laptop> because /dev/mmcblk1 and /dev/mmcblk0 are often interverted
Sep 14 13:28:21 <gena2x> badcloud: i saw exact instruction on wiki
Sep 14 13:28:37 <GNUtoo|laptop> mrmoku, I'll push my kernel config later on
Sep 14 13:29:01 <DocScrutinizer> idea being the user apps using ALSA snd_open() and snd_close() don't do this with "ALSA:default" but come with their own .alsarc.d/* alsaconfig files to include to ALSA .alsarc and defining a unique ALSA audio device for the app. Then with acihooklib and ALSA hooks plugin you define arbitrary commands that get executed whenever such a unique individual audio dev is snd_open()'ed or close()'ed
Sep 14 13:29:53 <mrmoku> GNUtoo|laptop: I don't have them... cat /proc/partitions lists them though
Sep 14 13:30:01 <GNUtoo|laptop> I have
Sep 14 13:30:14 <GNUtoo|laptop> mrmoku, but I've also that in my kernel:
Sep 14 13:30:19 <GNUtoo|laptop> *omap mmc driver
Sep 14 13:30:25 <GNUtoo|laptop> *block devices for mmc cards
Sep 14 13:30:30 <GNUtoo|laptop> *ext2/3
Sep 14 13:30:37 <GNUtoo|laptop> and similar stuff necessary for booting
Sep 14 13:31:31 <mrmoku> hmm
Sep 14 13:32:41 <mrmoku> GNUtoo|laptop: you are using multiboot?
Sep 14 13:33:06 <GNUtoo|laptop> I tried everything
Sep 14 13:33:09 <mrmoku> :)
Sep 14 13:33:18 <GNUtoo|laptop> currently I've a flashed kernel
Sep 14 13:33:23 <GNUtoo|laptop> I'll retry uboot
Sep 14 13:33:29 <GNUtoo|laptop> but later
Sep 14 13:33:45 <mrmoku> to *not* share the kernel with maemo... that would be possible with multiboot?
Sep 14 13:33:54 <GNUtoo|laptop> yes indeed
Sep 14 13:34:49 <GNUtoo|laptop> also with uboot but multiboot is more user friendly
Sep 14 13:41:02 <badcloud> flashed the splashscreen
Sep 14 13:41:18 <badcloud> still getting nor boot menu text
Sep 14 13:41:42 <badcloud> nor is what I meant instead of 'NAND ' (beforehand)
Sep 14 13:47:08 <lindi-> badcloud: how do you boot?
Sep 14 13:47:27 <badcloud> lindi-: long power press
Sep 14 13:48:12 <lindi-> badcloud: maybe your AUX is stuck?
Sep 14 13:48:33 <badcloud> lindi-: I don't get nor menu when qi is flashed
Sep 14 13:48:55 <lindi-> badcloud: how do you know it is in NOR?
Sep 14 13:48:57 <badcloud> lindi-: btw, when uboot is flashed, it's not that I get nor menu, only the firsl line of text
Sep 14 13:49:38 <badcloud> if uboot is flashed and I press power for ~3 sec
Sep 14 13:49:39 <gena2x> badcloud: to see menu, hold power for 1 sec and press and hold AUX
Sep 14 13:50:09 <badcloud> gena2x: one sec, reflashing uboot to try this out
Sep 14 13:50:14 <gena2x> i mean power for 1 sec, then power+aux
Sep 14 13:51:23 <badcloud> gena2x: same deal, the text 'poweroff' is at the top left corner of screen
Sep 14 13:51:37 <badcloud> now without the colorful horiz line at the bottom
Sep 14 13:51:50 <badcloud> I can wait a while to see what happens
Sep 14 13:52:11 <gena2x> i think you just didn't flash boot env properly
Sep 14 13:52:59 <badcloud> I can download devirginator again
Sep 14 13:53:20 <gena2x> you have no need in whole thing
Sep 14 13:53:36 <gena2x> just download envedit and environment.in
Sep 14 13:53:41 <badcloud> ok
Sep 14 13:53:43 <gena2x> and use my instructions
Sep 14 13:54:12 <gena2x> so far this worked for everyone
Sep 14 13:55:11 <badcloud> Undefined subroutine &main::crc32 called at ./envedit.pl line 79
Sep 14 13:55:46 <gena2x> ops
Sep 14 13:56:07 <gena2x> ok, anyway, i g2g
Sep 14 13:56:19 <badcloud> ok
Sep 14 13:56:20 <gena2x> it should work
Sep 14 13:56:34 <badcloud> do I need to do it as root or reg user?
Sep 14 13:56:46 <badcloud> ^ was as root
Sep 14 13:57:19 <badcloud> dos1: just the man I wanted to see
Sep 14 13:57:44 <badcloud> do you have a copy of that priv msg conversation we had about me testing your qi overclk images?
Sep 14 13:58:22 <dos1> badcloud: hi
Sep 14 13:59:09 <dos1> badcloud: hmm... did you have "badcloud" nick back then, or with some suffix?
Sep 14 13:59:30 <badcloud> could be '_' as a suffix
Sep 14 13:59:31 <dos1> "badcloud" log is empty for me in konversation :x
Sep 14 13:59:31 <badcloud> not sure
Sep 14 13:59:40 <badcloud> dag
Sep 14 13:59:51 <badcloud> I don't remember which of the images worked for me
Sep 14 14:11:12 <dos1> badcloud: could you change your nick to badcloud_ for a while? i can't find how to open custom log here ;x
Sep 14 14:15:26 <mrmoku> GNUtoo|laptop: did you find out what is causing dbus-daemon to run havoc?
Sep 14 14:15:39 <GNUtoo|laptop> mrmoku, later, I'm working for now
Sep 14 14:15:47 <GNUtoo|laptop> s/working/studying
Sep 14 14:15:47 <mrmoku> GNUtoo|laptop: ok :)
Sep 14 14:18:14 <GNUtoo|laptop> mrmoku, maybe fsogsmd
Sep 14 14:18:34 <GNUtoo|laptop> mrmoku, try dummy modem
Sep 14 14:20:35 <mrmoku> GNUtoo|laptop: even after killing phonefsod, phoneuid and fsogsmd it behaves bad
Sep 14 14:21:56 <GNUtoo|laptop> that's because of cron
Sep 14 14:22:07 <GNUtoo|laptop> try putting a dummy modem
Sep 14 14:22:43 <mrmoku> hmm... ok
Sep 14 14:26:16 <mrmoku> cat /proc/interrupts
Sep 14 14:26:18 <mrmoku> oops
Sep 14 14:28:46 <badcloud> dos1: ok
Sep 14 15:05:20 <mrmoku> dos1: locally building fixed watchdog now :)
Sep 14 15:08:27 <dos1> mrmoku: nice :)
Sep 14 15:12:40 <mrmoku> dos1: looking into xserver-common now
Sep 14 15:28:50 <mrmoku> dos1: any idea how we get a WiFi resource for n900 into fsodeviced?
Sep 14 16:01:54 <mrmoku> dos1: watchdog and xserver-common pushed
Sep 14 17:30:46 <mrmoku> GNUtoo: do you have a pointer for me where to find multiboot?
Sep 14 17:31:35 <GNUtoo> mrmoku, apt-get it
Sep 14 17:31:43 <GNUtoo> mrmoku, it's in the extra feeds
Sep 14 17:31:53 <GNUtoo> my computer uses too much ram and freeze
Sep 14 17:31:56 <mrmoku> ahh, ok, thanks
Sep 14 17:32:01 <GNUtoo> so I'm trying to fix that now
Sep 14 17:32:08 <GNUtoo> so I can build again
Sep 14 18:11:36 <mrmoku> GNUtoo: heh, forgot to add an entry for maemo :/
Sep 14 18:11:39 <mrmoku> can only boot shr now :P
Sep 14 18:34:40 <GNUtoo> mrmoku, lol
Sep 14 18:34:48 <GNUtoo> mrmoku, maybe it's the way to go?
Sep 14 18:34:56 <GNUtoo> aka eat your own dog fod
Sep 14 18:34:58 <GNUtoo> *food
Sep 14 18:39:57 <mrmoku> GNUtoo: hehe, wanted to get still some inspirations from the maemo ui though :)
Sep 14 18:40:12 <GNUtoo> ok nice
Sep 14 18:42:07 <mrmoku> ahh... 0 is default to maemo in multiboot menu
Sep 14 18:47:57 <GNUtoo|laptop> mrmoku, any new commits?
Sep 14 18:48:04 <GNUtoo|laptop> should I try to make a new image?
Sep 14 18:48:10 <GNUtoo|laptop> dos11, hi
Sep 14 18:48:26 <GNUtoo|laptop> dos11, hi
Sep 14 18:49:08 <mrmoku> GNUtoo|laptop: I pushed xserver-common and watchdog
Sep 14 18:49:13 <GNUtoo|laptop> ok
Sep 14 18:49:19 <GNUtoo|laptop> should I push udev?
Sep 14 18:49:20 <mrmoku> should obsolete the use of r&d
Sep 14 18:49:24 <GNUtoo|laptop> ok nice
Sep 14 18:49:36 <mrmoku> what did you fix in udev?
Sep 14 18:49:40 <GNUtoo|laptop> nothing yet
Sep 14 18:49:50 <GNUtoo|laptop> I want to add it for certain machines only,in the image
Sep 14 18:49:58 <GNUtoo|laptop> but you could do it too
Sep 14 18:49:59 <mrmoku> ahh... yep
Sep 14 18:50:10 <mrmoku> I wanted to find out how to handle wifi
Sep 14 18:50:17 <GNUtoo|laptop> ah wifi
Sep 14 18:50:22 <GNUtoo|laptop> indeed we have a kernel issue
Sep 14 18:50:24 <mrmoku> it works fine, but fsodeviced does not discover it as resource
Sep 14 18:50:28 <GNUtoo|laptop> ifconfig wlan0 up
Sep 14 18:50:36 <GNUtoo|laptop> works fine
Sep 14 18:50:38 <GNUtoo|laptop> if:
Sep 14 18:50:42 <GNUtoo|laptop> *you have the firmware
Sep 14 18:50:45 <GNUtoo|laptop> *you use udev
Sep 14 18:50:57 <GNUtoo|laptop> *you have modified udev rules
Sep 14 18:50:59 <GNUtoo|laptop> but:
Sep 14 18:51:06 <GNUtoo|laptop> ifconfig wlan0 down doesn't
Sep 14 18:51:12 <GNUtoo|laptop> maybe that's because I'm using PSM?
Sep 14 18:51:18 <mrmoku> psm?
Sep 14 18:51:22 <GNUtoo|laptop> power saving mode
Sep 14 18:51:26 <GNUtoo|laptop> iwconfig wlan0 power on
Sep 14 18:51:31 <mrmoku> ahh, ok
Sep 14 18:51:32 <GNUtoo|laptop> huge power savings
Sep 14 18:51:42 <GNUtoo|laptop> basically the router buffer the packets for you
Sep 14 18:51:52 <GNUtoo|laptop> and then send them all at once when the phone request them
Sep 14 18:51:54 <GNUtoo|laptop> and other stuff
Sep 14 18:52:08 * mrmoku installs wireless-tools
Sep 14 18:53:53 <mrmoku> GNUtoo|laptop: how do you see if ifconfig down works? 
Sep 14 18:54:03 <mrmoku> if I do ifconfig down wlan0 and wmaster0 disappear
Sep 14 18:54:04 <GNUtoo|laptop> if it segfault
Sep 14 18:54:09 <GNUtoo|laptop> then look at dmesg
Sep 14 18:54:10 <mrmoku> still shown with ifconfig -a
Sep 14 18:54:20 <GNUtoo|laptop> does it segfaults
Sep 14 18:54:21 <GNUtoo|laptop> ?
Sep 14 18:54:46 <mrmoku> [  535.265747] wl1251: down
Sep 14 18:54:48 <mrmoku> works
Sep 14 18:54:50 <mrmoku> does not segfault
Sep 14 18:55:09 <mrmoku> I have the following on ifconfig up though
Sep 14 18:55:11 <mrmoku> [  105.859588] wl1251: ERROR Power save entry failed, giving up
Sep 14 18:55:21 <GNUtoo|laptop> strange
Sep 14 18:55:24 <GNUtoo|laptop> I'll try
Sep 14 18:55:41 <mrmoku> hmm... not on ifconfig up
Sep 14 18:55:52 <mrmoku> probably maemo trying to connect to my AP
Sep 14 18:56:13 <mrmoku> btw. I have no modified udev rules
Sep 14 18:56:19 <mrmoku> but I have udev and the firmware installed
Sep 14 18:56:45 <GNUtoo|laptop> mrmoku, http://pastebin.com/E0EnDzu5
Sep 14 18:57:00 <GNUtoo|laptop> mrmoku, look here for modified dev rules:
Sep 14 18:57:18 <GNUtoo|laptop> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:df:*", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
Sep 14 18:57:20 <GNUtoo|laptop> in:
Sep 14 18:57:24 <GNUtoo|laptop> /etc/udev/rules.d/70-persistent-net.rules
Sep 14 18:57:32 <GNUtoo|laptop> note the 00:1f:df:*
Sep 14 18:57:37 <GNUtoo|laptop> I'll explain
Sep 14 18:57:42 <GNUtoo|laptop> basically it's a wl1251_spi
Sep 14 18:58:04 <mrmoku> GNUtoo|laptop: ok, that udev rule is only for persistent naming of the interface
Sep 14 18:58:05 <GNUtoo|laptop> the wl1251 don't have the memory(flash,eeprom etc...) to store the mac address
Sep 14 18:58:10 <GNUtoo|laptop> indeed
Sep 14 18:58:19 <GNUtoo|laptop> else the interface do:
Sep 14 18:58:29 <GNUtoo|laptop> wlan0->wlan1->wlan2->wlan3...
Sep 14 18:58:48 <mrmoku> heh, ok
Sep 14 19:08:49 <mrmoku> GNUtoo|laptop: even when associated ifconfig down does not segfault for me
Sep 14 19:09:19 <GNUtoo|laptop> strange
Sep 14 19:09:28 <GNUtoo|laptop> maybe different kernel config
Sep 14 19:09:29 <GNUtoo|laptop> here's mine
Sep 14 19:09:38 <mrmoku> I'm using maemo default kernel
Sep 14 19:10:07 <GNUtoo|laptop> http://pastebin.com/5nZYnm0T
Sep 14 19:10:10 <GNUtoo|laptop> ah ok
Sep 14 19:10:11 <GNUtoo|laptop> not me
Sep 14 19:10:21 <dos11> GNUtoo|laptop: (mac address) i figured it out as i have to click "reg" button on my router every time i want to connect to wifi with SHR/N900 :D
Sep 14 19:10:36 <GNUtoo|laptop> ok 
Sep 14 19:10:37 <GNUtoo|laptop> lol
Sep 14 19:11:01 <GNUtoo|laptop> I've a GNU/Linux x86 DIY router
Sep 14 19:11:14 <GNUtoo|laptop> ath9k
Sep 14 19:11:18 <GNUtoo|laptop> hostapd
Sep 14 19:11:26 <GNUtoo|laptop> stock distro kernel
Sep 14 19:11:28 <GNUtoo|laptop> etc...
Sep 14 19:11:38 <GNUtoo|laptop> but all the config were made by me
Sep 14 19:11:48 <mrmoku> what kernel source are you using?
Sep 14 19:11:51 <GNUtoo|laptop> like hostapd.conf, named.conf etc...
Sep 14 19:11:53 <GNUtoo|laptop> on what?
Sep 14 19:11:57 <mrmoku> n900
Sep 14 19:11:58 <GNUtoo|laptop> the ones in oe
Sep 14 19:12:15 <GNUtoo|laptop> kernel_2.6.28-20101501+0m5.diff.gz
Sep 14 19:12:20 <mrmoku> did somebody already integrate the patches from meego?
Sep 14 19:12:21 <GNUtoo|laptop> I don't know if I pushed it tough
Sep 14 19:12:26 <GNUtoo|laptop> no
Sep 14 19:12:31 <mrmoku> we should do that probably
Sep 14 19:12:34 <GNUtoo|laptop> ok
Sep 14 19:12:54 <mrmoku> http://meego.gitorious.org/meego-os-base/kernel-source/trees/master/patches
Sep 14 19:13:08 <mrmoku> there is a config for n900 too in that repo
Sep 14 19:13:29 <GNUtoo|laptop> ok
Sep 14 19:14:18 <mrmoku> and maybe there is rfkill in that kernel too
Sep 14 19:14:26 <GNUtoo|laptop> can old meego scan while associated btw?
Sep 14 19:14:33 <mrmoku> old meego?
Sep 14 19:14:36 <mrmoku> you mean maemo?
Sep 14 19:14:37 <GNUtoo|laptop> s/meego/maemo
Sep 14 19:14:38 <GNUtoo|laptop> yes
Sep 14 19:15:29 <mrmoku> yup, I can do iwlist scan while associated
Sep 14 19:16:15 <GNUtoo|laptop> ok
Sep 14 19:16:21 <GNUtoo|laptop> what year is the kenrel from?
Sep 14 19:16:30 <GNUtoo|laptop> if it's 2009 I'm very interested
Sep 14 19:16:38 <mrmoku> the maemo one?
Sep 14 19:16:43 <GNUtoo|laptop> yes
Sep 14 19:16:50 <mrmoku> Nokia-N900-51-1:/etc/multiboot.d# cat /proc/version 
Sep 14 19:16:50 <mrmoku> Linux version 2.6.28-omap1 (bifh6@maemo-bifh-19) (gcc version 4.2.1) #1 PREEMPT Thu Dec 17 09:40:52 EET 2009
Sep 14 19:17:06 <GNUtoo|laptop> because scan while associated has been proposed and pushed very recently
Sep 14 19:17:10 <GNUtoo|laptop> in compat-wireless
Sep 14 19:17:13 <GNUtoo|laptop> and linux-next
Sep 14 19:17:27 <mrmoku> hmm... interesting
Sep 14 19:17:32 <GNUtoo|laptop> indeed
Sep 14 19:17:35 <GNUtoo|laptop> for the dream
Sep 14 19:17:38 <GNUtoo|laptop> but dream is sdio
Sep 14 19:17:55 <mrmoku> maybe they patched it...
Sep 14 19:18:33 <GNUtoo|laptop> indeed if it makes PSM work on dream....
Sep 14 19:19:02 <GNUtoo|laptop> I should ask dos11 for advises on GUI for dream
Sep 14 22:44:15 <DocScrutinizer> is our ALSA dmix plugin optimized for Arm?
**** ENDING LOGGING AT Wed Sep 15 02:59:57 2010