IRC log for #htc-linux on 20091005

00:00.11kvasterkri5: ?
00:00.13kvasterfirst boot will be SLOW
00:00.23kvasterit will create data images
00:00.32mdrobnakis annoyed at how Android does keymaps
00:00.44kvasteranyway android 1.6 is much more faster for me then 1.5
00:02.18kri5kvaster: yes i've seen it, but running on android is damn slow
00:02.30kri5by the way i hope 1.6 will be faster
00:02.41kri5and there is still the home button problem :/
00:02.49kvaster???
00:02.49mdrobnakkri5: Do you have Data?
00:03.04kvasterno
00:03.05kvasterno data
00:03.08kvasterat least for me
00:03.15kvasteri was not able to setup apn e.t.c.
00:04.16mdrobnakOk, well, if it's attempting data calls, that slows things down too
00:04.34mdrobnakthe RIL needs work still. Once i get the keymap fixed for RAPH, that's what I will start working on again, but I need help...
00:05.06kri5mdrobnak: what do you mean by data?
00:05.22mdrobnakkri5: Like do you see "G,E,3G" near the signal strength?
00:06.23kri5nop :/
00:07.43mdrobnakok, are you passing mem=76M on the command line?
00:07.52mdrobnakbecause that will slow it down too.
00:10.36kri5no i'm not
00:11.17kri5i've seen some ppp stuff left on the startup.txt, i just get them off
00:11.21kri5tring again
00:12.45mdrobnakHow much ram is it booting with?
00:13.06mdrobnak89M?
00:13.06kri5tried to boot again, and it boots with locked screen, and no way to unlock it :/
00:13.23kvasterkri5: remap home button to MENU in your kernel
00:13.53kri5kvaster: how do i do this?
00:14.06kvasterpatch msm_blackstone_pad.c
00:14.13kri5arf :/
00:14.27kri5i just took a zImage :/
00:14.29kvasteror I can upload my zImage
00:14.34kri5i didn't compiled it myself
00:14.57kvasterone sec - will upoad my kernel to xda
00:15.00kri5kvaster: please do :), but do you have the latest patchset for kind of hacky sound?
00:15.06kri5kvaster: ok, thx
00:15.09kvaster?
00:15.13kvasteryep
00:15.17kri5ok great
00:15.19kvasterall latest patches
00:15.21kri5:D
00:15.30kvasterbut this was not sound patches - this was battery patcj
00:15.32kvasterpatch
00:15.44kvasterwhich enabled us to use raphael android image
00:15.52kri5i've some problem on my main machine, so i can't build my own kernel :)
00:16.28kri5kvaster: but there was a patch in a pastebin from mrblacomm this afternoon, which was sound related, isn't it?
00:17.07kvasternope
00:17.07kvasterit was battery related
00:17.13kvastersound was working long ago
00:17.13kri5kvaster: ok, my bad :p
00:17.17kvasterbut not in android
00:17.22kri5hum
00:17.52kri5i see :)
00:18.38*** join/#htc-linux toast (n=quassel@173-137-30-129.pools.spcsdns.net)
00:19.06kvasterdone. see my post on xda
00:19.44kri5kvaster: thanks, going to test it right now
00:20.01kri5mdrobnak: i think i got nothing related to mem in my cmdline :/
00:21.11mdrobnakkri5: Then you need to look at dmesg some how. It probably defaults to 89. In which case, yes, it's going to be slow.
00:21.29kri5should i set it to some value?
00:21.40kri5and what is the cl option?
00:22.48kvastermdrobnak: which value is correct ?
00:23.20mdrobnakThat depends on the device
00:23.27kri5for blac100
00:23.34mdrobnakand if you're testing Android, keep it at 89M.
00:28.59*** join/#htc-linux kvaster (n=kvaster@live.bn.by)
00:37.49mdrobnakis re-building system.img. Joy
00:40.36kri5mdrobnak: have fun ;)
00:41.11mdrobnakHey if this gets me anywhere closer to having a working keymap, I'll be very happy
00:41.35mdrobnakIf I knew the correct identifier, I probably would be able to get away with not updating the img.
00:42.52kvastermdrobnak: you're rebuilding android image with patches applied to android from connect-utb ?
00:43.28mdrobnakI took the last Raphael based one, cp'd the files from the image to a dir, edited what I needed, and recreated the cramfs.
00:46.13*** join/#htc-linux enatefox (n=user@c-69-254-31-113.hsd1.fl.comcast.net)
00:46.14mdrobnakawesome
00:46.22mdrobnakI think I completely screwed it up
00:46.22mdrobnaklol
00:47.39mdrobnakand then it crashed.
00:48.49kri5:D
00:49.57*** join/#htc-linux kvaster (n=kvaster@live.bn.by)
00:51.29enatefoxLet's suppose, hypothetically, that I had a Kaiser and needed help with a certain s5k3c1fx camera would I be in the right room?
00:54.48mdrobnakenatefox: In linux?
00:54.54enatefoxbut of course
00:55.17mdrobnakTechnially, yes, right room. I think the gurus are asleep though hehe
00:55.37enatefoxI got info on using Haret to debug the output, I got nothing. This is my treasure map: http://forum.xda-developers.com/showthread.php?t=560257
00:55.54enatefoxjust kind of hoping there were 1+ others for this
00:57.52enatefoxif not I can always feign interest in the relevant subject and offer shill advice.
00:58.06mdrobnaklol.
01:00.48mdrobnakI'm worn out for the day. I got a "standard" keymap for the RAPH110 done for the most part, and tried to do the same thing for Android. It's a pain in the... for Android to do it.
01:00.51*** join/#htc-linux x29a_ (n=x29a@unaffiliated/x29a)
01:01.13enatefoxas a side note, since I can't think of a whole lot to talk about re: Linux and HTC, but I found that we are vulnerable to fork bombs just like our desktops
01:01.24enatefoxso, we've got that
01:01.38ali1234O_o
01:02.28ali1234enatefox: how much do you know about i2c?
01:02.57enatefoxi know it's a bus
01:03.21enatefox(dont let them see you thinking/googling the answer...)
01:03.40mdrobnaklol
01:03.52ali1234do you have a shell on kaiser with debugging tools?
01:04.07mdrobnakenatefox: Compiling code, or  just using perl to make your phone explode? lol
01:04.11enatefoxalright, I've used Linux for years as a user but am willing/able to learn the "real" stuff. I'm no noob, just haven't done this before
01:04.29enatefoxa debug shell... I have bash 4 and ADB
01:04.35mdrobnakwb ali1234 - how's it going?
01:04.41ali1234ADB sucks
01:04.44enatefoxtrue
01:04.48mdrobnaknoooo
01:04.50enatefoxkeypads suck worse
01:04.51mdrobnakadb rules!
01:04.52ali1234you need the real stuff
01:04.53mdrobnak:D
01:05.11ali1234bash, /dev/mem, hexdump, and i2c-tools
01:05.50ali1234and lots of haret
01:06.09enatefoxi like how pressing up/down to cycle ADB history will execute random commands that it jumbles into dangerous root-level lines
01:06.25enatefoxyea, I've got the gist of getting the info but no one to look it over.
01:06.50ali1234so, according that post, you need 3 things, "rpc call for the clocks, i2c for the camera control and adsp for the vfe queues"
01:06.57*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
01:07.04ali1234hmm, a dzo :)
01:07.12enatefoxI'm not looking for a hand holding session just something more than I can find on teh webz
01:07.17enatefoxthen a wild dzo appears
01:07.35mdrobnakali1234: We don't even have /dev/mem, remember?
01:07.42mdrobnakOMAP should thought
01:07.44mdrobnak*though
01:07.49ali1234mdrobnak: well you should do............
01:08.19enatefoxhmm. i have /dev/mem and it's denied even for root
01:08.38ali1234you have to mmap it, but that's neither here nor there
01:08.42*** join/#htc-linux stickboy (n=anonymou@128.153.209.94)
01:08.56mdrobnakali1234: Given up on the memory stuff for a while. 107MB is going to have to suffice for the time being..
01:11.12ali1234enatefox: so, anyway... i2c being a bus and all is abstracted through a driver, so assuming that driver has been implemented on kaiser (it probably has) then that part should be relatively easy - just a matter of looking at the datasheet for the sensor
01:13.12ali1234the other two bits are harder. best advice i can offer is read the existing driver over and over until you understand how it works backwards, and then look for that similar behaviour in haret dumps
01:13.28enatefoxali, apologies up front that I do suck at kernel dev and all but I know what you're saying. You seem to not have a Kaiser so I can only imagine your interest but I know that dzo used the datasheet for Kaiser to make it work on a Vogue
01:14.01enatefoxI wouldn't even know where to begin, just trying to revive a dead topic and "you people" know your stuff
01:14.04ali1234yes, i read that. but you have to understand that the datasheet will only tell you so much, mainly the i2c stuff
01:14.12enatefoxright
01:14.41ali1234the other parts, well, the best doc is going to be the existing code
01:14.44enatefoxi mean, if I have the driver for a Vogue which is very close to my phone, and dzo used my phone's datasheet, that I could figure out what he did to mod it?
01:15.01enatefoxinb4 100101011 1010110101
01:15.56mdrobnakgood luck enatefox ...
01:16.00mdrobnakI'm off to see Zombieland!
01:16.04enatefoxfair enough
01:16.08mdrobnaksee yas
01:17.42ali1234dzo: got a link to that s5k3c1fx datasheet handy?
01:19.28enatefoxdamn... had a link myself.
01:20.41enatefoxthis is all she (he in this case) wrote: "...used the s5k3c1fx data sheet to do the s5k4b1fx driver...they seem quite similar. Best thing to do is just trace i2c accesses when turning on the camera and copy that.
01:21.15enatefoxand sauce: http://www.riddle.ru/dl/ccd/samsung/ds_s5k3c1fx_rev012.pdf
01:21.35enatefoxs5k4b1fx is Vogue, s5k3c1fx is Kaiser
01:23.24ali1234ok. you won't need to trace any i2c, that is for sure. you have all that in the datasheet
01:23.59enatefoxproceed... i should mention there is a bounty going on now for a working camera on these phones.. have you met my friend Mr. Washington?
01:25.10ali1234have you tried just running the existing driver on your kaiser?
01:25.47enatefoxWell, I don't know when the V-Tec fail kicks in but the app doesn't crash-- just a black screen when the camera is "initialized"
01:26.14enatefoxat this point I don't know where it's failing. But the driver is for a Vogue and while similar I know they're slightly different and it doesn't work "out of the box"
01:26.25ali1234yeah
01:26.47ali1234see the thing you have to realise about these chips is everything is sectioned off on the second core in a really annoying way
01:27.15ali1234so while the i2c stuff is easy to fix, you still have to work out how to talk to the annoying shared memory interface
01:27.36enatefoxyea, that sounds like a peach
01:28.01enatefoxseems like a higher level transport could work but forget that if I can't write low level calls..
01:28.02enatefoxI dunno, I don't want to clog the room with my personal army or anything but I've got nothing to go on as far as what to research/test and don't know a smarter dev that's working on this now
01:28.37ali1234problem is everyone bought new phones
01:28.47ali1234i don't even use MSM at all :)
01:29.58enatefoxyou and your corporate incentives.. I got my Tilt for $99 thanks to a typo. today, with my job, I couldn't buy that phone again. Got no data/text/MMS, I keep it real 2 years ago here
01:30.24ali1234i'm still using a wizard from 2006
01:30.29enatefoxnice
01:30.43ali1234which kernel has the vogue driver in it?
01:30.53enatefoxwe're running 2.6.25
01:31.01ali1234from linuxtogo?
01:31.18enatefox27 got all estranged wife on us and cut things up badly or so my bad analogy goes
01:31.20enatefoxyea
01:31.42enatefoxcompcache .5...
01:32.09ali1234hmm not in my branch
01:32.55enatefoxsee, I love talking to people. I thought I'd get lucky and someone would say "don't worry guy, since it works on a similar phone, change 0xFAIL to 0xWORK and wash your hands after" but I see this is going to be "a thing"
01:33.09ali1234found it
01:36.13ali1234ok, so i looked at kernel/drivers/i2c/chips/s5k4b1fx.c and compared it on the datasheet, and looks very similar
01:37.10enatefoxgood?
01:39.23ali1234yeah. the two files on the post are probably the only two files you wont need to change
01:40.09enatefoxwait, which 2 files?
01:40.13enatefoxthe .c file?
01:40.31ali1234drivers/i2c/chips/s5k4b1fx.c and drivers/sbus/char/vfc_i2c.c
01:40.39ali1234you might need to change the clocks
01:40.43enatefoxsorry.. just saw it
01:41.08ali1234you see these lines like: writel(0xfe8c6a49,MSM_CLK_CTL_BASE+0x40);
01:42.14enatefoxyea
01:42.25ali1234what you should do is find the value of MSM_CLK_CTL_BASE, and then use haret to look for writes in that region when you turn on the camera
01:42.37*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
01:42.39enatefoxthat doesn't sound too bad
01:42.39ali1234then that's the clock init you need. so youpatch that into the file
01:43.03enatefoxok.. so to summize for the noobs that are listening, and not for my benefit...
01:43.04ali1234if you are lucky you will see it doing the exact same write, then you know it works the same way
01:43.17enatefoxI need to find writes to MSM_CLK_CTL_BASE
01:43.36enatefoxthen somehow find the clock speed of the writes
01:43.45ali1234just look what value is written
01:43.49enatefoxthen adjust a variable that holds the clock speed
01:43.55ali1234in this case 0xfe8c6a49
01:44.06enatefoxand that would be the clock speed?
01:44.16enatefoxthere's a 4.) PROFIT!! step in there somewhere
01:44.23ali1234sort of. it's a bit field that controls the clock multipliers i guess
01:44.30enatefoxgood enough
01:44.33ali1234just think of it as a magic number
01:44.38enatefoxright
01:44.54ali1234you might need to write in a different place too
01:45.14ali1234hell, for all i know, MSM_CLK_CTL_BASE might have a completely different value on kaiser vs vogue
01:45.24enatefoxI'm still going to need help but that certainly explains the process a bit.
01:46.41enatefoxthanks, I don't want to keep tying up the room from more important things, but that told me more than I could find-- even more than a MSN Live search
01:48.52ali1234one more thing
01:49.04ali1234do you have /dev/i2c-0 or /dev/i2c/0 or similar?
01:49.21ali1234if so, you can use i2c-tools to probe the i2c bus
01:49.40ali1234if the chip is enabled you should see the default values as listed on the datasheet
01:49.47ali1234then you know it is part working at least
01:50.49enatefoxno.. /dev/input is the only "i" in /dev
01:53.01ali1234hmm.... then your first step should probably be getting that set up.
01:53.19enatefoxit's like an Easter egg hunt of my patience and skill level
01:53.28ali1234this place is always quiet at this time
01:54.01enatefoxI'll propose we make this so I can "emerge aworkingcamera" for the 2.7 kernel
01:54.13enatefoxI know Linus is holding out on us
01:54.29ali1234looks like someone has done this before though: http://dx.infernix.net/kaiser/
01:55.06ali1234although those images are probably out of date
01:56.02enatefoxI'm flexible and have the list of commits since things got rolling. I think I can manage that if that's all it takes
01:56.07enatefoxgood find
01:56.28ali1234looks like you just need to enable the i2c dev interface on kernel config and compile i2c-tools
01:57.17enatefoxok, and in theory I could take the i2c_tools from that link, compile it into the kernel or add it as a module and then that would bring me to..
01:57.28ali1234i2c-tools is userspace
01:57.29enatefoxgetting the right timer for the writes to MSM_CLK_CTL_BASE
01:57.38enatefoxoh
01:57.56enatefoxum, you're saying the dev interface is kernel side but not the toolset?
01:58.04ali1234right
01:58.15ali1234you get a /dev/ device and talk to it from userspace...
01:58.26enatefoxok, that makes sesne
01:58.50ali1234so you need to bring that up. and then check if you can see the chip or not
01:58.58ali1234if you can, then the clocks are probably right already
01:59.24enatefoxlet's say, then that I bring that up and can't see the chip. That's indicative that only the clock is wrong?
01:59.43enatefoxTrying to map out where things can go wrong in my hastily thrown together attempts
01:59.58ali1234well, the three things....
02:00.02ali1234any can be wrong
02:00.38ali1234i can tell you about i2c only
02:00.52ali1234someone who actually knows kaiser hardware can tell you about the other two (at least where to look)
02:01.05ali1234but you'll have to hang around for them
02:01.14ali1234i guess they're all sleeping
02:01.31enatefoxyou've taught me moar than I knew before
02:01.34enatefoxyou know, in my job searching I see kernel development jobs starting at $95K. I think I know why
02:02.23enatefoxthis is not going to get me even close to a working camera but you told me the process which is more valuable for me at this point. Thanks a lot for your time
02:04.45ali1234seems like there's more than one type of kaiser too :(
02:04.53ali1234that will only complicate things
02:05.05enatefoxyea, the actual Kaiser has 2 cameras I have an ATT Tilt with one camera
02:05.06*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
02:06.11ali1234well, getting it to work will be a matter of painstaking detective work
02:06.26enatefoxoh yes. painstaking indeed
02:06.34ali1234it probably will boil down to changing a couple of values somewhere, the problem is knowing which ones...
02:07.06enatefoxunfortunately I missed the wifi wave to see how that was done but it was all kernel side with some userland services set at boot. I imagine the same for the camera
02:07.29ali1234camera should be a lot easier than wifi
02:07.43ali1234not that that really helps
02:07.44enatefoxbesides, who cares if my kid makes her first step I don't need to remember that..
02:08.07ali1234the kaiser camera isn't exactly great quality anyway :/
02:08.27enatefoxhey, you can't fault a 3.0 megapixel beast
02:08.43enatefoxor can you...
02:09.11ali1234hmm not too bad
02:09.40enatefoxluckily I don't care about bluetooth because that's been quite the problem apparently.
02:10.16enatefoxare these phones more difficult to port? Seems like we're a little behind the other HTC's, not including the G1/2/Hero/GodTier phones
02:10.35ali1234MSM is a really nasty architecture in my opinion
02:10.50ali1234the phone has two cpus: linux runs on one, all the hardware is attached to the other
02:10.57ali1234and they talk with an undocumented protocol
02:11.23enatefoxwat.. you mean my phone or HTC's in general? this sounds like the Wii all over again
02:11.33ali1234the other phones are similar but the second core is only used for the radio bits and is much easier to reverse
02:11.59ali1234MSM phones means all the 7x01 phones
02:12.23ali1234stuff like the wizard uses the OMAP chips, they are much easier to program
02:12.29enatefox>undocumented protocol. have to love it
02:12.49ali1234like eg. the bluetooth is just connected to a PC compatible UART
02:12.57ali1234it doesn't get any easier than that
02:14.08enatefoxhmm. well, forgetting my problems, what is this channel really for (spare my dignity)? Is it just general porting or is there a specific thing being addressed?
02:14.23ali1234it's for general porting of linux
02:14.45ali1234people like to run android on the end result
02:14.59ali1234but android itself doesn't need any porting, it only needs a linux kernel
02:15.21ali1234so this place is all about figuring out how the hardware works
02:15.45ali1234this time last year it was all kaiser stuff
02:15.45enatefoxI would love to run a solid Linux distro (Ubuntu/Debian) then run Android. I used to be able to get it working in a chroot but lately I get bus errors.
02:15.48*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
02:15.50ali1234now it's all about the new phones
02:16.13enatefoxthose damn kids and their  MyBooks and FaceSpaces. Can't keep up
02:18.16enatefoxI got the wifey an  LG Incite which is, among other things, not HTC and has a Linux equivelant out there somewhere. Here I am failing at getting the camera to work with such a large support group. I guess that phone will never happen
02:20.41ali1234LG incite is MSM7201A
02:21.02ali1234like the new phones everyone has
02:21.09enatefoxwith nary a mention of Linux development on it
02:21.23ali1234the kernels from here would probably run on it
02:21.28enatefoxo rly
02:21.47ali1234just need to patch the LCD drivers and stuff
02:21.59enatefox</caveat>
02:22.03ali1234sure, always
02:22.17enatefoxbut that's encouraging
02:22.41enatefoxcost me $30 for that phone
02:22.43ali1234these phones are based on system-on-chip designs, which means everything is in one chip
02:22.51ali1234which means they're all basically the same inside
02:23.09ali1234only the external stuff like LCD and buttons are different
02:23.36enatefoxnice.. I did see LCD4Linux. Maybe I could grab some code from that
02:23.44ali1234someone who had brought one of these phones up before could probably get that one running linux in a couple of days if they had one
02:24.54enatefoxWell, thanks for the help. I'm going to see how far that can take me. Appreciate the time/help. I might actually get somewhere now...
02:35.47*** join/#htc-linux root2 (n=root@rgnb-5d87d2d1.pool.mediaWays.net)
02:38.11*** join/#htc-linux pleemans (n=toi@d54C2A96D.access.telenet.be)
02:38.40*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
03:00.03*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
03:21.07*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
03:44.34*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
04:08.06*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
04:19.18*** join/#htc-linux droid0011 (n=g1@p4FDCF8A1.dip.t-dialin.net)
04:29.38*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
04:33.53mdrobnakTo the log readers: Keyboard maps in Android are more of a pain then standard Linux. Not so sure on speed for that one. Will have standard map fixed up by tomorrow night. Also, would like to start doing more debugging on the RIL again -- anyone know how to print out the entire string received from the modem in the unsolicited responses? I feel the code might be crashing there, and would like to put debugging in there...b
04:33.53mdrobnakut not sure how to print the entire string, before it is parsed in the AT parser...Thanks. I'm off to sleep now..
04:49.31*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
04:53.09*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
05:14.49*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
05:37.31*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
05:41.07*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
05:52.14*** join/#htc-linux xixx (n=xixx@cpmsq.epam.com)
06:00.27*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
06:07.46*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
06:20.09*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
06:20.25*** join/#htc-linux kiozen (n=oeichler@p549215A5.dip0.t-ipconnect.de)
06:21.54*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
06:30.39*** join/#htc-linux eway (n=ellis@genkt-048-026.t-mobile.co.uk)
06:43.37*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
07:06.08*** join/#htc-linux FR^2 (n=frzwo@2001:41d0:1:ed2f:0:0:0:cafe)
07:07.39*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
07:18.09*** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
07:28.13*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
07:33.04*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
07:40.56*** join/#htc-linux leobaillard (n=leobaill@63.48.73-86.rev.gaoland.net)
07:41.31leobaillardhi !
07:42.43tmzthello
07:50.40*** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it)
07:51.57*** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215)
07:57.28leobaillardlet's get this f****** wifi to work...
08:05.09tmztdoes it not work for you?
08:05.11tmztwhat device?
08:05.29tmztdoesn't work for me either, but I think I did somethign wrong and don't have the calibration data
08:06.43leobaillardwell, it works in some very conditions and it's kind of random
08:07.01leobaillardbut I'm trying to make a script containing a procedure that works most of the time
08:07.24leobaillardbut we get those s*** CRC errors and don't know where the hell they come from
08:12.42*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
08:15.47leobaillardpfff /o\
08:24.09*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
08:29.30tmztcr2: http://thread.gmane.org/gmane.linux.ports.arm.kernel/
08:29.47tmztnot our chip, but 2k and finally explains what the contents of oob structs are
08:29.55tmztecclayout I mean
08:30.08leobaillardthe only good news that I see here is that I can get the wifi up without turning it on in winmo
08:30.15tmztso maybe we can get compatible with wm :)
08:30.24tmztleobaillard: sure, that shouldn't matter
08:31.49leobaillardyeah, but phh said at the early developments of it that it was necessary
08:33.48leobaillardwhat are you working on tmzt ?
08:35.57tmztlooking into user gsm stacks
08:36.21tmztunlike raph100 (I think) I don't have full sound working in calls
08:36.38tmztbut I'd like some plans for when I do to get my linux phone working
08:39.46leobaillardokay
08:40.33leobaillarddo you know where I can find a kernel version already used in a working htc linux device like dream, hero, whatever ?
08:42.42tmztleobaillard: sure, android.git.kernel.org
08:44.21leobaillardthx
09:05.52leobaillardI may have found the right procedure \o/ ! testing...
09:06.07tmztcool
09:06.10tmztplease document
09:06.21leobaillardit's fast and throws merely no debug message
09:06.40leobaillardBUT, I have to try it again and again to see if it wasn't just luck...
09:06.59leobaillardwhich could, unfortunately, very well be the case... :/
09:07.53*** join/#htc-linux nozze1 (n=nozze@u193-11-162-41.studentnatet.se)
09:11.51*** join/#htc-linux Squarc (n=Squarc@145.81.0.104)
09:21.07*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
09:21.15leobaillardit seems to work well for the wifi acivation :D let's script it...
09:30.31leobaillardit works :D let's go in class, and then I'll finalize my script and document it ! :D
09:34.52*** join/#htc-linux darkstone (n=LOL@78-86-59-180.zone2.bethere.co.uk)
09:36.23*** join/#htc-linux nozze2 (n=nozze@u193-11-162-41.studentnatet.se)
09:44.48*** join/#htc-linux Captnoord (n=Captnoor@145.74.216.71)
10:00.52*** join/#htc-linux thedicemaster2 (n=thedicem@24.132.89.51)
10:28.39*** join/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
10:29.23*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
10:30.00rayman18hi all
10:30.57rayman18one queestion, what mean the last comit on the git " hack in snd.c" ?¿
10:31.41tmztalsa support?
10:32.15Captnoordits a hack to check if the implementation is correct......
10:33.13rayman18ok
10:33.20rayman18<PROTECTED>
10:33.45*** join/#htc-linux stefand (n=stefand@194.7.153.125)
10:34.03Captnoordand like tmzt is saying its for the alsa support
10:35.18rayman18ok, its is clear now
10:35.21rayman18thanks
10:35.22tmztoh, wrong snd.c
10:35.24rayman18<PROTECTED>
10:36.25tmzthow did msm sdcc work with wrong dma channels?
10:36.36tmztis this needed for wl12xx?
10:43.15Captnoordtmzt: its maybe because if you always use the wrong dma channels... nothings wrong and everything should work....
10:43.16Captnoord:P
10:44.11Captnoordso if there is no wifi.... the sdcc should work on that channel if its set ofcourse to work on that channel even if its the wrong one
10:44.34tmztright, but if wifi works won't it interfere without that patch?
10:45.01Captnoordyup....
10:45.10tmztok
10:45.11Captnoordit will interfere
10:45.13Captnoordbut....
10:45.15tmztso I need the patch
10:45.20CaptnoordI think so
10:45.51Captnoordit could work... but it would result in loads of errors on both the wifi side and the sdcc side
10:45.59Captnoordmaybe the crc erros are coming from that
10:46.13tmztpossible, can you paste a little?
10:46.28Captnoordnope.. not atm.... working...
10:46.31Captnoordno stuff here
10:56.39*** join/#htc-linux leaigor (n=laigor@188.134.16.241)
10:57.05*** join/#htc-linux thedicemaster (n=thedicem@j89051.upc-j.chello.nl)
10:58.40*** join/#htc-linux x_coRe_x (n=x_coRe_x@95-37-155-123.dynamic.mts-nn.ru)
11:00.38*** join/#htc-linux leobaillard (n=leobaill@leobaillard.org)
11:05.02*** part/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
11:08.28*** join/#htc-linux x_coRe_x (n=x_coRe_x@95-37-155-123.dynamic.mts-nn.ru)
11:18.06*** join/#htc-linux Squarc (n=Squarc@145.81.0.104)
11:23.16*** join/#htc-linux PocketIRC111 (n=pocketir@32.174.47.166)
11:24.45*** join/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
11:28.29*** part/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
11:38.15*** join/#htc-linux MethoS- (n=clemens@134.102.106.250)
11:55.38*** join/#htc-linux cybersyx (n=cybersyx@151.54.241.151)
11:56.36*** join/#htc-linux BT (n=irchon@cpe-68-173-135-7.nyc.res.rr.com)
12:15.46*** join/#htc-linux Squarc1 (n=Squarc@145.81.0.104)
12:26.22*** join/#htc-linux Captnoord (n=Captnoor@145.74.216.71)
12:28.35*** part/#htc-linux leobaillard (n=leobaill@leobaillard.org)
12:53.26*** join/#htc-linux [1]Captnoord (n=Captnoor@145.74.216.71)
12:58.37tmztwell, if anyone can help get this adapted to msm
12:58.38tmzthttp://chronolytics.com/mid/fbdev_xaa_pp_hwcurs.tgz
13:02.10*** join/#htc-linux xCOREx (n=x_coRe_x@95-37-187-247.dynamic.mts-nn.ru)
13:04.14*** join/#htc-linux CORE (n=x_coRe_x@95-37-176-177.dynamic.mts-nn.ru)
13:10.56*** join/#htc-linux CORE (n=x_coRe_x@95-37-215-54.dynamic.mts-nn.ru)
13:16.52*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
13:17.07*** join/#htc-linux CORE (n=x_coRe_x@95-37-225-47.dynamic.mts-nn.ru)
13:30.22*** join/#htc-linux Captnoord (n=Captnoor@145.74.182.0)
13:30.30*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
13:36.45*** join/#htc-linux xCOREx (n=x_coRe_x@95-37-253-200.dynamic.mts-nn.ru)
14:00.59*** join/#htc-linux PocketIRC111 (n=pocketir@32.174.13.69)
14:09.08*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
14:12.32*** join/#htc-linux gekas (i=4d69cbdc@gateway/web/freenode/x-xchykcdyctuwpmty)
14:36.22*** join/#htc-linux townkat (n=town@86.127.6.111)
14:41.01*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
14:58.17*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
14:58.38*** join/#htc-linux dzo (n=dzo@121.98.128.127)
15:21.19*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
15:29.39*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
15:31.56*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
15:50.43*** join/#htc-linux kiozen (n=kiozen@93.135.67.59)
15:52.11*** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes)
15:56.55*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
16:04.57*** join/#htc-linux xixx (n=xixx@217.21.56.2)
16:06.55*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
16:14.38*** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes)
16:21.20*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
16:21.48*** join/#htc-linux bartman (n=bart@tau.jukie.net)
16:24.39*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
16:25.54*** join/#htc-linux stickboy (n=anonymou@128.153.209.94)
16:45.25*** join/#htc-linux cybersyx_ (n=cybersyx@151.54.243.58)
16:48.45*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
16:49.42*** join/#htc-linux kvaster (n=kvaster@212.98.181.84)
17:04.05phhapt: can you warn me when leobaillard comes back please ? :p
17:05.27*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:07.13Gnutooleviathan, with a friend we tried to debug the oops
17:07.39Gnutooleviathan, it was an error message that made the oops...we now just have to find which one
17:08.21phhab heisenbug ?
17:08.23phhanù*
17:08.24phhan*
17:10.38dcordesphh, heisenbug?
17:11.06phha bug caused by a measure (here a debugging message)
17:11.35phhin reference to heisenberg's principle
17:11.38*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
17:13.49*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:14.51Gnutoook
17:14.54Gnutoolol
17:15.12Gnutoos/message/
17:15.22Gnutoothings like EINVAL etc...
17:16.23Gnutoolol for heisenbug
17:32.14*** join/#htc-linux FR^2 (n=frquadra@91.121.172.47)
17:34.17*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:44.43*** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34)
17:44.55rafyvittohey guys i got a question
17:45.23swc|666sorry, this channel is only girls, not guys
17:45.28swc|666;)
17:46.01rafyvittohas anyone gotten there hands on a sprint hero rom? this rom should be base on 1.6 donut, meaning it has native support for vga screen, hence no scaling would have to be implemented on the raph/diamond kernel
17:47.29rafyvittoi mean since the sprint hero is a cdma phone, and 1.6 donut brought cdma support =]
17:49.14phhrafyvitto: someone already did some 1.6 builds
17:49.58phhrafyvitto: no pm.
17:50.18phhit was a generic build, so it shouldn't be too specific
17:50.49rafyvittoits squash, il have to converted back to img
17:51.00phh?!?
17:51.15phhrootfs is squashfs ?
17:52.11rafyvittois that generic image you reffer to squashfs?
17:58.02phhmaybe you can try kaiser's initramfs
18:01.16*** join/#htc-linux stickboy (n=anonymou@128.153.176.145)
18:12.03*** join/#htc-linux gekas (i=4d69cbdc@gateway/web/freenode/x-oonfyesihhaedooz)
18:18.42*** join/#htc-linux leobaillard (n=leobaill@63.48.73-86.rev.gaoland.net)
18:24.04*** join/#htc-linux pleemans (n=toi@d54C2A96D.access.telenet.be)
18:24.49rafyvittolet see if it works
18:24.56rafyvittoits booting
18:25.11rafyvittoits succesfully created swap files
18:25.53phhleobaillard: !!
18:26.17phhleobaillard: i read you got it ?
18:27.05*** join/#htc-linux stickboy (n=anonymou@128.153.176.145)
18:28.44*** join/#htc-linux leaigor (n=laigor@188.134.16.241)
18:35.04*** join/#htc-linux cr2 (n=cr2@109.84.202.109)
18:35.47leobaillardphh: I'm eating, telling you after that, but yes, some progress... :)
18:35.55phhok :)
18:36.30cr2dcordes: ping
18:38.30cr2phh: your diff from yesterday. includes many "not our" patches
18:38.32rafyvittoand nothing happend black screen for more than 10min ><
18:38.43phhcr2: i know :/
18:38.55phhcr2: android thing ...
18:39.53cr2phh: maybe it's easier to grep for CONFIG_HTC*
18:40.09cr2phh: but not all our changes are ifdef'd
18:40.10phhcr2: maybe dcordes know how to get a big diff after the kernel merges
18:40.36cr2i think it's a good idea to try to ifdef our changes.
18:41.05cr2and hide the proc_comm_wince, clock control and gpio alt behind proc_comm
18:41.34dcordescr2, ello
18:42.09cr2hi dcordes
18:42.23cr2dcordes: there was a blac100 patch yesterday
18:42.25*** join/#htc-linux gekas (i=4d69cbdc@gateway/web/freenode/x-lrjdffcnxtstqpwd)
18:42.51cr2phh: this one ->
18:42.55cr2diff -ur linux-2.6.27/arch/arm/plat-omap/usb.c kernel/arch/arm/plat-omap/usb.c
18:42.56cr2--- linux-2.6.27/arch/arm/plat-omap/usb.c2008-10-10 00:13:53.000000000 +0200
18:42.57cr2+++ kernel/arch/arm/plat-omap/usb.c2009-09-16 19:20:14.280057252 +0200
18:43.15cr2has even nothing to do with msm
18:43.47dcordessome timestamp ?
18:45.47kvastercr2: do you need latest patch for blac ?
18:46.13cr2kvaster: pastebin it
18:46.26cr2kvaster: not .ca
18:46.46cr2if it does not break other devices, we should commit it
18:48.02*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
18:59.09cybersyx_hi cr2
19:01.09kvastercr2: http://pastebin.com/m52f7411
19:01.17kvasterit's blacm patch + small addition
19:01.41cybersyx_cr2, don't ask you anything don't worry :)
19:02.22*** join/#htc-linux stickboy_ (n=anonymou@128.153.18.192)
19:03.13*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:03.56phhkvaster: your board-htcblackstone.h seems weird :p
19:04.17kvastermmm
19:04.33kvaster:(
19:04.40phhi mean the RAPH100_things
19:07.58cr2+        .smem_offset = 0xfc110, /* cr2: 0xfc00c, 0xfc110 */
19:08.02cr2i don't understand this one
19:08.47*** join/#htc-linux mblancom (n=mblancom@230.Red-217-126-178.staticIP.rima-tde.net)
19:08.48cr2+               msm_battery_pdata.smem_offset = 0xfc110; /* cr2: 0xfc00c*/
19:08.50cr2here too
19:09.12mblancomhi all!
19:09.36cr2mddi_client_epson.c needs more code, but it's a good beginning
19:09.39cr2hi mblancom
19:09.44*** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it)
19:09.49mblancomhi !
19:09.57townkathi mblancom
19:10.01*** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it)
19:10.04cr2mblancom: what is the purpose of this patch
19:10.11cr2+        .smem_offset = 0xfc110, /* cr2: 0xfc00c, 0xfc110 */
19:11.09mblancomwell, i remember asking about the specific changes needed to be able to start android wihout fall in the power off trap.
19:12.06cr2http://htc-linux.org/wiki/index.php?title=RaphaelMemoryMap
19:12.10Gnutoohi leviathan the oops will be fixed soon
19:12.10leviathanGnutoo: wonderfull
19:12.11Gnutooleviathan, I'm debuging it but I bet the code is a at a point I know:
19:12.26mblancomand this address is from dwaradzyn, the comment says that after sending to you the battery.dll you said somethin about this address
19:12.34cr2says that 0xfc00c has completely different purpose
19:12.45leviathanI showed the working OpenMoko to my comilitones this morning, some nearly freaked out, because we got it running ^_^
19:13.10cr2leviathan: hmm. why is it so surprising ?
19:13.41mblancomcr2: perhaps i missunderstood something
19:13.49cr2mblancom: blac100 is very similar to raph100. only the epson mddi is different. and some gpios
19:14.08leviathanGnutoo: because they didnt believe that it could work so soon =)
19:14.26Gnutooleviathan, I don't know if it will work but oops will be debuged
19:14.37Gnutooyou never know what's next
19:14.50mblancomcr2: ok, lets erase the comment then.
19:15.08cr2yes, your patch is 100% raph100
19:15.09Gnutoobasically there is this code:
19:15.13Gnutoothat is suspect:
19:15.14cr2compatible
19:15.37cr2mblancom: btw, what about the headset/speaker ?
19:16.01Gnutooif (reply->xid != req->xid) {kfree(reply);continue;}if (reply->reply_stat != 0) {rc = -EPERM;break;}
19:16.02cr2mblancom: i've seen in the source, that it's necessary to apply the gpio power to eenable it
19:16.34cr2i think we have traced it on a real blac100 too
19:16.50Gnutooanyway I know more or less where it is located...recompiling a cleaner kernel with debug for addr2line
19:16.59mblancomcr2: well, I did not try to make a special or different approach. I only want to enable what was donne some time ago and it does not worked until now...
19:17.44cr2mblancom: i've added the gpio to wiki, and you can recheck it with 'watch gpios' in haret
19:18.05mblancomcr2: I would like to know how to deal with sound in the speaker. To power it.... I have to learn how to do it...
19:18.20cr2mblancom: btw, what about BT? the setup is the same as on raph100 i think
19:19.32cr294  0x5e   26  I irq CAP_SENz (NAVI)    ext SPK related
19:19.47mblancomcr2: I was following your advances with BT, Wifi, GPS, etc, just waiting to know if they work in android...
19:19.51cr2the speaker amplifier power gpio
19:20.05cr2~ping dcordes
19:20.06aptpong dcordes
19:20.52phhmblancom: bluetooth works on android
19:20.57phhthe other one will be tough
19:21.15mblancomphh: nice to ear that
19:21.16*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
19:21.19cr2mblancom: sound needs some more research in the ADIE and AudioPara area
19:21.46phhmblancom: i just need to find someone who is used to make androd builds
19:22.00*** join/#htc-linux cr2 (n=cr2@109.84.202.109)
19:22.03mblancomcr2: I remember dwaradzyn posting his AudioParam.c ...
19:22.05dcordesleviathan, I hope nobody hyperventilated
19:22.43cr2dcordes: can we clone the current blackstone board file for rhod/topa ?
19:22.47leviathandcordes: They found the work very cool. So we got respect from students in switzerland
19:22.56leviathanits already something
19:23.06leviathanthey find it cool, that someone does it
19:23.13leviathan:D
19:24.18mblancomgo to dinner, bbl
19:24.34cr2leviathan: when i show the angstrom booting on my phones, everybodysays i'm crazy :)
19:24.41dcordescr2, yes
19:24.55cr2leviathan: on all my phones :)
19:24.55dcordesleviathan, I don't know if there are many unix geeks among my fellow students
19:25.00phhcr2: but you are.
19:25.10cr2phh: LOL
19:25.12phh(and we love that :)
19:25.40cr2phh: eh ? i'm crazy ?
19:25.45dcordesbut showing angstrom boot on a nice smartphone makes everybody think you are totally super crazy geek that's true :)
19:26.05gekaskinda
19:26.05dcordesfound the same phenomenon
19:26.14phhwell angstrom is unusable for me because of no keyboard :(
19:26.21cr2dcordes: yeah, on the most expensive smartphones ;)
19:26.49dcordeswell whatever has scrolling white on black system messages
19:26.59leviathanthey is only perfect, if you can show, that everything is working fine or at least working minimal
19:27.09cr2dcordes: don't forget the nice penguin
19:27.14phh:)))
19:28.02dcordescr2, I usually have the logo turned off in order to have more fit on the screen
19:28.06*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:28.08cr2most people who know me have already learned that windows sucks, and linux should run everywhere.
19:28.38dcordescr2, what's is the key of your success?
19:28.52dcordess/what's/what/
19:28.59cr2so in the end, they are not surprised that linux is running on my cellphone.
19:29.17phhleobaillard: ?
19:29.36*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
19:29.42cr2just amazed that it's so easily possible for a qualified person to do it
19:30.37phhcr2: well for raph you're lucky that current android uses same SoC. If you had an unknown soc, it would be a lot of other troubles.
19:30.38dcordesI mean I didn't convince too many people about linux superiority
19:31.00cr2phh: that's why i bought raph, and not kaiser
19:31.06phh:)
19:31.28dcordescr2, look at the pxa ports
19:31.34dcordess/cr2/phh/
19:31.37dcordes^^
19:32.39leviathanI'm building an shr-image right now and will install alsa,vlc,mplayer and midori
19:32.47leviathanthen I'll try alsa again
19:37.23dcordesleviathan, alsa will be nice
19:38.00dcordesleviathan, did you boot a qtopia rootfs?
19:39.04cr2leviathan: yeah, i'd like to have a qtopia roots too. even without the phone support
19:39.23leviathanhmm
19:40.02leviathanWould there support in development for it? then I would make it run
19:40.51*** join/#htc-linux cr2 (n=cr2@109.84.202.109)
19:41.19*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:42.28cr2leviathan: yu can aask BabelO aboiut it :)
19:42.55leviathanhttp://qtopia.net/modules/devices/
19:43.03leviathanok, would be nice, to have it like this
19:43.08leviathanvery smart gui-design
19:43.14leviathanthats why I love Qt
19:43.36cr2leviathan: i'd like to run this program http://qlandkarte.org/
19:44.09cr2it was already done on several devices earlier.
19:44.28cr2they just didn't either had 100% linux support or no gps
19:44.39leviathanis this qt-landkarte able to read open streetmap
19:44.41cr2we have a very good change to change that now
19:44.57leviathandont believe it, one german word and I begin to write german again -_-
19:45.00cr2leviathan: the raster background ? yes
19:45.10cr2hehe
19:45.17BabelOhi
19:45.21BabelOwhat happen ? :)
19:45.25leviathanhiho
19:45.43cr2leviathan: if you want vector maps, use roadmap. it also has qt4 support
19:45.44leviathanWe talked about to port qtopia-phone-x11 onto the htcdream
19:45.45leviathan=)
19:45.52cr2BabelO: we want to build qtopia
19:46.13leviathanI'm building shr atm
19:46.23leviathandidnt die yet
19:47.09leviathanafterwards I can also try to build qtopia-phone
19:47.12Gnutoommm does the usb gadget uses the rpc?
19:47.33leviathannope, not that I knew it
19:47.45leviathanit only uses ipv6
19:47.58Gnutoostrange because when I remove some rpc part I've no usb
19:47.59leviathanits the only function I registered in dmesg and console
19:48.08Gnutoook
19:48.29GnutooI'll look if I use function
19:48.35BabelOGnutoo: you remove nfs maybe ?
19:48.45Gnutoono rpc not for nfs
19:48.49Gnutoobut for the msm thing
19:48.54leviathanperhaps they tinkered something with syscalls and rpc... who knows... >_<
19:49.28cr2leviathan: it needs some more c++ code. like "ril"
19:49.28*** join/#htc-linux cr2 (n=cr2@109.84.202.109)
19:49.29cr2dcordes: i suggest to copy the blacstone to topaz. then we can support rhod100 with it too
19:49.36leviathansmokes a cigarette$
19:49.49cr2and then apply the patch by mblancom
19:50.10Gnutoo# CONFIG_USB_FUNCTION is not set
19:50.29Gnutoocr2, ril is in C
19:50.41cr2Gnutoo: qtopia is c++
19:50.45Gnutooyes
19:50.46Gnutooit is
19:50.51Gnutoobut android's ril is C
19:51.04Gnutoothere is another ril from qtopia?
19:51.10cr2ok, that why i said "ril"
19:51.16dcordescr2, ok I'll have dinner then we can put it
19:51.23Gnutooah ok
19:51.25cr2the modem interface laye
19:51.26Gnutoosorry then
19:51.37*** join/#htc-linux stickboy (n=anonymou@128.153.176.141)
19:51.37Gnutoothey use their own...
19:52.05cr2but it was already done for the moko phone
19:52.53dilingerparts of ril are in c++
19:53.32cr2we just need to exten calypso support to msm AT
19:53.53cr2most of it is standard AT anyway
19:54.16cr2and the weird simtoolkit stuff can wait.
19:57.23leviathanre
19:57.25gekashttp://forum.xda-developers.com/showthread.php?t=567870 omg...
19:59.41mblancomhi again...
20:03.03Gnutoomaybe I need to recompile the kernel again
20:03.13Gnutoo(recompile means change important options)
20:04.52cr2phh: have you looked at hte SDIO spec ?
20:04.58leviathanGnutoo: Try my options =)
20:05.05Gnutoono i mean for debugging
20:05.11Gnutoolike remove -o3
20:05.25leviathanGnutoo: my options allow very good tracing in dmesg
20:05.27leviathan:)
20:05.27Gnutooremove the preemptive
20:05.57leviathanbut that allows better performance, like on a workstation
20:06.00cr2leviathan: the biggest problem i have with dream and 7201A is wtf is /dev/mem not working ?
20:06.01leviathanokee, it also needs aku
20:06.14leviathancr2: hmm
20:06.17leviathanyaah
20:06.17*** join/#htc-linux PocketIRC111 (n=pocketir@32.174.162.6)
20:06.30leviathancould be because its memory access driver
20:06.54leviathanand perhaps the addresses arent correct for these devices and you access into the digital nirvana
20:07.14cr2no, you get a nerror messae
20:07.28cr2= some code traps this access
20:07.51cr2on accessing nirvana you will get a segfault in the kernel = oops
20:09.54leviathanhmm, true
20:11.17cr2hehe
20:14.24*** join/#htc-linux patp (n=patp@87.194.56.160)
20:14.31patphiya
20:14.42*** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes)
20:15.00patpformatting sd card, what's the best allocation unit size?
20:15.11dcordesawesome 100+ users
20:15.32cr2lol
20:15.48cr2dcordes: add topa/rhod, and there will be more :)
20:16.15dcordesgood propaganda. one reason why I wanted to see msm in OE
20:16.28cr2patp: SD blocksize is 512, SDHC is 2048 afair
20:16.47Gnutooleviathan, what debugging options did you add?
20:16.59*** join/#htc-linux richard333 (n=richard3@adsl-072-149-006-119.sip.mia.bellsouth.net)
20:17.01dcordeslol I have no toolchain :-(
20:17.16richard333hey guys i have a question
20:17.33richard333how do i emulate the pressing of the trackball down with my kaiser
20:18.23richard333or should i ask @ android?
20:18.25dcordesrichard333, doesn't the kaiser have an "enter" key in the middle of the front keypad? you could use that
20:19.22leviathanGnutoo: hmm, I'll past it into pastebin
20:19.25richard333@dcordes yeah i agree, i just want to know if its currently mapped to an existing key and if its not how do i redo mappings, some starting leads would be nice, is it a zimage change?
20:19.26leviathanthen you can look
20:19.29Gnutoook
20:20.48patpcr2: thx
20:20.51leviathanhttp://pastebin.com/m6d29b6cf
20:21.23*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
20:21.40dcordesrichard333, idk how to remap keys in android userspace. for zImage (kernal) you have to look here: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
20:22.34dcordesrichard333, the relevant bits are located in this file arch/arm/mach-msm/board-kaiser-keypad.c
20:22.42Gnutooleviathan, how do you enable -o0 ?
20:22.49Gnutoos/o/O
20:23.25dcordesrichard333, see the coment in line 11: "* PAD Center = KEY_OK"
20:24.00Gnutooleviathan, you seem to use CONFIG_CC_OPTIMIZE_FOR_SIZE=y
20:24.05dcordesit's the good old marbalon driver
20:24.36richard333@dcordes i see yeah thats very relevant, so PAD_CENTER which is the one i'd like to use is set to KEY_OK right now i'd like to change it to trackball down, what would be the equivalent command for that?
20:25.26patpI'm really hacked off with this... the exact same sd card with the exact same files on it, today is not recognised.
20:25.35dcordesrichard333, did you navigate to the file?
20:26.03richard333not yet
20:26.29richard333ok im there
20:26.49dcordesrichard333, I can't recall where the dream trackball driver is
20:28.20leviathanGnutoo: I have one very enoying problem with my htcdream
20:28.30Gnutooleviathan, yes?
20:28.34leviathanhow can I set the keymap in the kernel?
20:28.50leviathanI cant type "-" on my hw-keyboard
20:29.03Gnutooleviathan, I didn't look yet but there is a driver that has all keymaps in the boards files
20:29.05leviathanthey keymap is crap
20:29.08Gnutooit has qwerty
20:29.19leviathanokee
20:29.23leviathana driver you say?
20:29.26leviathanwhere?
20:29.29phhcr2: according to leobaillard's tests, you were right about nand driver, it seems it's bad enough to get the sd controler missed for some time.
20:29.41Gnutoo/* arch/arm/mach-msm/board-trout-keypad.c
20:29.58Gnutooleviathan, but can't it be done in userspace?
20:30.18dcordescr2, ok only copy the boardfile for now?
20:30.49richard333@gnutoo that is the dream keypad drivers?
20:31.14Gnutoorichard333, yes
20:31.28Gnutookeyboard =? keypad?
20:31.37leviathanit is done in the userspace
20:31.44leviathan<PROTECTED>
20:31.44leviathan<PROTECTED>
20:31.44leviathan<PROTECTED>
20:31.44leviathan<PROTECTED>
20:31.44leviathan<PROTECTED>
20:31.45leviathan<PROTECTED>
20:31.48leviathan<PROTECTED>
20:31.55cr2dcordes: clone the *blackstone* files
20:32.00leviathanI just need the keyfile
20:32.00Gnutoook
20:32.50Gnutooleviathan, look in the intializations files
20:33.59leviathanfuck'n crap, the hacked some binary stuff for layout
20:34.09leviathanI'll have to make my own layout -_-
20:34.11Gnutoo???
20:34.13Gnutooah ok
20:34.21leviathanhttp://bzed.de/
20:34.22Gnutoowhat do you mean by some binary stuff?
20:34.27leviathanhttp://bzed.de/posts/2009/08/german_keyboard_layout_for_cyanogenmod/
20:34.34leviathanlook there
20:35.14richard333so basically there isn't an utility winmo style where i can remap my keys?
20:36.00Gnutooleviathan, setkey 0x0 0x38 0x0
20:36.08Gnutoomaybe it can set the keys
20:36.13richard333i'd have to edit the board-kaiser-keypad.c to emulate the trackabll down button which i would have to get the code from the dream file
20:36.15leviathanokee
20:36.16cr2the sdcard is much slower than nand. at least in wince
20:36.39cr2leviathan: LC_LANG ?
20:42.28leviathancr2: hmm
20:42.46leviathananyway. first I build an shr image
20:42.55leviathanthen Ill look further
20:43.32dcordesTopaz is a silicate mineral of aluminium and fluorine with the chemical formula Al2SiO4(F,OH)2.
20:44.15cr2lol
20:44.17leviathanGnutoo: did you upload the alsa drivers into git now?
20:44.21Gnutoonot yet
20:44.26Gnutooyou have the patch
20:44.32Gnutooand I'm still debugging them
20:44.40cr2something new:
20:44.40GnutooI know more or less where the problem is
20:44.42cr200000001 00000006 00000001
20:44.48Gnutoobut I need better debugging options
20:44.53Gnutoofor having a better trace
20:44.59leviathanok
20:45.02leviathantry mine
20:45.02Gnutoo-o0 is compiling
20:45.03leviathan=)
20:45.07leviathanok
20:45.15Gnutoo#oe guys told me that it was in the Makefile
20:45.18Gnutoothe top one
20:45.23*** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
20:45.24cr2#define RPCROUTER_CTRL_CMD_REMOVE_CLIENT        6
20:45.26cr2aha
20:45.51phhhu ? rpcrouter says to the client to drop connection ?
20:47.22richard333so can anyone guide me as to finding the htc dream key mappings file
20:51.26leviathanhttp://www.handy-faq.de/forum/htc_dream_google_g1_forum/87817-google_g1_qwertz_tastatur_wiederherstellen.html
20:51.31leviathanyoull have to register
20:51.52leviathanfor openmoko I'll have to write my own
20:51.56leviathanits so fuck'n exotic keymapping
20:52.01cr2phh: see such message for the first time
20:52.12leviathanI'll have to associate them my self
20:52.21Captnoordcr2 that stuff is in the rpc dll's on wince
20:52.27Captnoordbut you already knew that
20:52.42cr2phh: tried to connect the BT headset
20:52.46cr2Captnoord: yes
20:52.57phhcr2: didn't work i guess ?
20:52.59dcordescr2, pushd
20:53.11phhit should work for A2DP actually
20:53.23phhsince android do it in software
20:54.01cr2phh: in wince
20:54.05cr200000001 00000006 00000001 fffffffe 00000000 00000014 00000000 fffffffe 00000006 00000001 8cf0f3fe 02293f18 0228e3f8
20:54.07cr200000001 00000006 00000001 fffffffe 00000000 00000014 00000000 fffffffe 00000006 00000001 00000001 02293f18 0228e3f8
20:54.38phhyou think i understand raw rpc replies ? :p
20:54.42cr2the arm11 rpcrouter tells the arm9 router about client close
20:55.15cr2need to lookup the syntax
20:55.39cr2cmd +
20:55.47cr2<PROTECTED>
20:55.48cr2<PROTECTED>
20:55.50cr2<PROTECTED>
20:55.50*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
20:55.51cr2<PROTECTED>
20:55.53cr2<PROTECTED>
20:56.33cr200000006 00000001 8cf0f3fe
20:57.30cr2=closed ARM11 cid=8cf0f3fe
20:57.49cr2this one is more cryptic
20:57.51cr200000006 00000001 00000001
20:58.04cr2what is cid=1 on wince ??
20:59.43dcordeslassen sie mich durch, ich spreche msm rpc
21:00.26phh:)
21:01.22phhcr2: rpcrouter or god i think :p
21:02.48*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
21:04.30cr2phh: rpcrouter is cid=-2
21:04.36cr20xfffffffe
21:05.28Captnoordwasn't 1 something like global
21:05.46Captnoordor self
21:06.53*** join/#htc-linux stickboy (n=anonymou@128.153.181.25)
21:08.38*** join/#htc-linux cybersyx_ (n=cybersyx@host145-83-static.34-79-b.business.telecomitalia.it)
21:09.39*** join/#htc-linux [1]Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
21:10.19cr2Captnoord: i don't understand why wince periodicaly changes the ept of the CB servers.
21:10.40cr2the same code is available on linux too. but the cid seems to be allocated only once.
21:11.15[1]Captnoordept?
21:11.29[1]Captnoordmaybe to allow multiple buffers
21:11.37[1]Captnoordasync system
21:11.56[1]Captnoordor
21:12.04[1]Captnoordhmmm
21:12.05[1]Captnoorddono
21:12.14[1]Captnoordhaven't been reading the asm lately
21:12.21[1]Captnoordbeen studing a lot
21:13.11*** join/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
21:14.30cr2but i don't get the GPS messages to the CB if i do the same
21:14.40cr2strange
21:14.50cr2something is still not right in the RPC setup
21:16.13[1]Captnoordcr2 like I sayd about the wifi and the sdcc stuff ... if we do something wrong and we do that consistantly..... everywhere.... there isn't a sight of a bug because everything works.... untill you want to implement something that requires something that you fuckedup then the entire setting will be different and the bug will be shown
21:17.28*** part/#htc-linux mblancom (n=mblancom@230.Red-217-126-178.staticIP.rima-tde.net)
21:17.29chemical_at_workprogress²
21:18.16*** join/#htc-linux [2]Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
21:18.53*** join/#htc-linux cr2 (n=cr2@109.84.202.109)
21:19.13cr2ok, so i've catched the moment where the CB muxed ept is disabled, and all CB servers are reregistered again
21:19.49cr2maybe we should do it on the adsp_cid :)
21:20.22cr2hmm. but it's not the adsp cid here.
21:29.33Gnutoook  here what I found
21:29.38Gnutooleviathan, ping
21:29.50leviathanGnutoo: yeah?
21:29.55leviathansry, was smoking
21:29.57leviathan=)
21:30.18Gnutooin msm_rpc_call_reply ept is null when moving the second bar in alsamixer
21:30.30Gnutooso that's what cause the kernel oops
21:30.38leviathanoh, ok
21:30.39Gnutooept is the endpoint
21:30.57Gnutoothe thing is that I looked at the bottom of the backtrace only
21:31.03leviathanok
21:31.04Gnutooinstead of looking at the top of it who has:
21:31.28Gnutoo[   97.697021] pc : [<c0038640>]    lr : [<c003876c>]    psr: 20000013
21:31.32Gnutoonote the pc...
21:31.37Gnutooso I went to the pc line
21:31.42Gnutooand I got the offending code
21:31.50Gnutoothat was before all my printk
21:32.05Gnutooputting a check and returning -1 make it not segfault
21:32.11Gnutoobut the bar doesn't seem to work
21:32.25Gnutooso we must have a valid endpoint
21:33.02leviathanwhich file, which line?
21:33.06Gnutoook
21:33.12Gnutoothe line you'll find it
21:33.14leviathanwants to take a look
21:33.16Gnutoofor the file it's:
21:33.34Gnutooarch/arm/mach-msm/smd_rpcrouter.c
21:34.27Gnutoogrep for if (ept->dst_pid == 0xffffffff)
21:34.31leviathanok
21:34.36Gnutooso if ept is null that fails
21:34.42*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
21:35.02Gnutooso we must:
21:35.05Gnutoo*check for ept
21:35.14Gnutoo*find why ept is null
21:35.32Gnutooif we do so we should get a better volume
21:35.41Gnutooand then we implement routing
21:35.42leviathanokee
21:35.45Gnutoolike in the openmoko
21:36.05Gnutoowith all theses switchs
21:36.22GnutooI'll go bye
21:36.24leviathanhmm, we could make a hack with changing the value to highest value possible as default
21:36.39leviathanok
21:36.42Gnutooyes you could but I prefer making it work
21:36.53Gnutooso:
21:36.59Gnutoo*you put the higest volume
21:37.11Gnutoo*I'll try to finish debugging when I'll have time
21:37.19leviathanok
21:37.24Gnutoobecause I could have returned -1 at higger level
21:37.35Gnutooand put a high value for volume
21:37.40Gnutoobut I didn't like it
21:37.43Gnutooso I debugged
21:37.48leviathanpls upload the current alsa driver, so that I can develop on it
21:37.56Gnutooyou've got the patch
21:38.06leviathanyeah, I mean into gitorious
21:38.07Gnutooall what you need is to check for null
21:38.13Gnutoook I'll do it once it's ready
21:38.21leviathanok
21:38.26Gnutoocan I go now:?
21:38.37leviathanyeah
21:38.40leviathangn8
21:38.54leviathanill go to sleep now anyway
21:38.55Gnutoothanks bye
21:38.57leviathanbye
21:44.37leobaillardbye all, night night !
21:45.04*** join/#htc-linux stickboy (n=anonymou@128.153.209.94)
21:48.36*** join/#htc-linux rafyvitto (i=rafyvitt@24.54.253.34)
22:00.56*** join/#htc-linux thedicemaster2 (n=thedicem@j89051.upc-j.chello.nl)
22:04.01dcordesyawns
22:07.48*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
22:20.52*** join/#htc-linux thedicemaster (n=thedicem@j89051.upc-j.chello.nl)
22:24.01*** part/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es)
22:24.33*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
22:26.00dcordesnn
22:44.25*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
23:06.17*** join/#htc-linux Bry8Star (n=Bry8Star@99.146.37.237)
23:20.04*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
23:24.35*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
23:53.11*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
23:58.30*** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.