Guest7605 has quit [Killed (sodium.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
<freemangordon1>
Wizzup: yeah, no chanlog there
freemangordon1 has quit [Quit: Leaving.]
freemangordon has joined #maemo-leste
belcher_ is now known as belcher
inky_ has quit [Ping timeout: 268 seconds]
inky_ has joined #maemo-leste
uvos__ has joined #maemo-leste
inky_ has quit [Ping timeout: 255 seconds]
inky_ has joined #maemo-leste
inky_ has quit [Ping timeout: 255 seconds]
diejuse has joined #maemo-leste
<stano_>
droid4: messages wlcore: Association completed.
<stano_>
omap-mcbsp 40124000.mcbsp: CLKS: could not clk-get() prcm_fck
<stano_>
oh it eventually connected, nvm
Pali has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
<stano_>
greets - (droid4) is the battery-charging indicator always showing charging for anyone else?
<Wizzup>
looks like the wl1251 did get some fixes since our kernel, but none seem to relate
<stano_>
now it stopped always showing charging 0_o
<stano_>
maybe because i'm in a long compile
<Wizzup>
Pali: ping
<Pali>
Wizzup: pong
<Wizzup>
looking at the scan problem in wl1251, where on nl80211 the wpa_supplicant scan requests get EINVAL, PaulFertser from #linux-wireless suggested to add wl->hw->wiphy->max_scan_ie_len to wl1251
<Wizzup>
I am looking at wlcore and it does set that, but it has a constant like htis: #define WL1271_CMD_TEMPL_MAX_SIZE 512
<Wizzup>
any idea where I could find the max command template length for wl1251?
<Pali>
I have no idea what this template length is
<Wizzup>
(looking at wlcore for an other driver that seems very similar)
<Wizzup>
me neither :)
<Pali>
anyway, in past when I debugged wl1251 kernel driver I was looking into TI SDK driver for wl1251, so maybe it would be again
<Wizzup>
ok
<Pali>
wl1251 is marked as "TI WiLink 4.0"
<Pali>
somewhere on internet was TI driver for this WiLink 4
<Pali>
I will try to find it
<Wizzup>
btw, this change makes wl80211 scanning work properly:
<Pali>
seems that their firmware RPC API shares some structures with old TI ACX100/110 wifi chips
<sicelo>
nice info @Pali
<Pali>
Wizzup, freemangordon: maybe you can write some reply to n900 u-boot email?
<Wizzup>
Pali: I am not sure what to reply, I don't think I can do it now or any time soon, but maybe we can find some timeline where we can agree it is doable by one of us
<Wizzup>
parazyd: pushed to hildon-base and building for maemo/beowulf-devel
<parazyd>
Awesome
uvos__ is now known as uvos
<uvos>
nice work Wizzup @ wl1251
<Wizzup>
uvos: it was mostly someone else guiding me, but yeah
<uvos>
to me sitting on the sidelines mabye setting wl->hw->wiphy->max_scan_ie_len to some random value thats ignored later looks a bit wierd
<uvos>
maybe i would be better wlcore manged this case better somehow
<Wizzup>
s/wlcore/wl1251
<Wizzup>
/
<uvos>
but idk
<uvos>
ok
<Wizzup>
as I understand it, the EINVAL doesn't even come from wl1251, it comes from layer before it
<uvos>
wlcore
<uvos>
no?
<Wizzup>
I don't think so, it's not loaded on n900
<Wizzup>
I think wl1251 is standalone, whereas on d4 the wlcore and others are loaded
<Wizzup>
iiuc
<uvos>
wl1251 isent a wlcore dirver
<uvos>
ok
<Wizzup>
wlcore *does* set this value
<uvos>
til
<uvos>
ok
<uvos>
Wizzup: so everything should work now? and we are using the command interface of wpa now, not dbus?
<uvos>
if so ill go around testing the current code on the divices i have
<Wizzup>
I need to build fixed kernel and push out some stuff to -devel
<Wizzup>
so maybe wait just a bit
<uvos>
ok when you do ill try xt875/wl1271, n900 wl1251 and d4's wl1285c
<uvos>
particulary i assume no one has tried the new code on wl1271 at all...
<Wizzup>
what 'new code'?
<uvos>
all changes since the start of you working on hidden aps
<Wizzup>
I tested on the d4, not the bionic
<uvos>
right
<Wizzup>
uvos: if you want to test, now on -devel you can test wifi for the devices that are not the n900
<Wizzup>
well, wait, no
<Wizzup>
uvos: yeah, wait, I need to revert back to libwpa_client once this n900 kernel builds
diejuse has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
<freemangordon>
Wizzup: yes, I changed the policy, but IIRC we agreed that 'user' will be netdev member
<Wizzup>
freemangordon: ok, that didn't happen yet, but I did it now
<Wizzup>
freemangordon: on n900 hidden ap stuff works fine now :)
<freemangordon>
great!
<freemangordon>
wext?
<Wizzup>
nl80211
<freemangordon>
or you fixed the driver
<freemangordon>
nice
<sicelo>
yay
<stano_>
does this fix losing wifi and all access points disappearing on droid4?
<stano_>
is there a script to restart wifi driver without rebooting?
inky has quit [Ping timeout: 265 seconds]
<Wizzup>
uvos: I think early next week I'd like to toy a bit with one of the tablets, or the droid 3, see how far I can come, anything you can recommend?
<Wizzup>
I know tony was working on display driver for one of them
inky has joined #maemo-leste
<uvos>
Wizzup: the d3 might be easier as the only real problem it should have judging by a breif look at its bord source and teardown images is bootstraping the thing, as it shares the pannel and everything else with the bionic
<uvos>
Wizzup: the tablets (all of them) have a dsi->lvds bridge chip that isent working for unkown reasons, tony was/is working on that.
<uvos>
right so for d3 i would to look around on xda for the safestrap files and install that, then modify a bionic dts so the memory map ends lower, force cmdline to something and then use mkbootimg to build a boot.img for it and try and boot that
<uvos>
if that fails you have to diff the board src for android 2.3 between targa and solana
<uvos>
since solana never got 4.0 or 4.1
<uvos>
if it works you can build kexec.ko for the soloana kernel and then clown boot should be a possibility
<uvos>
looks like Hashcode (main mapphone los dev) had solana booting the newest motorola kernel see mapphone_solana_phablet_defconfig in the los kernel and the memory map is just 512 MB starting at 0x80000000