00:00.11 | kvaster | kri5: ? |
00:00.13 | kvaster | first boot will be SLOW |
00:00.23 | kvaster | it will create data images |
00:00.32 | mdrobnak | is annoyed at how Android does keymaps |
00:00.44 | kvaster | anyway android 1.6 is much more faster for me then 1.5 |
00:02.18 | kri5 | kvaster: yes i've seen it, but running on android is damn slow |
00:02.30 | kri5 | by the way i hope 1.6 will be faster |
00:02.41 | kri5 | and there is still the home button problem :/ |
00:02.49 | kvaster | ??? |
00:02.49 | mdrobnak | kri5: Do you have Data? |
00:03.04 | kvaster | no |
00:03.05 | kvaster | no data |
00:03.08 | kvaster | at least for me |
00:03.15 | kvaster | i was not able to setup apn e.t.c. |
00:04.16 | mdrobnak | Ok, well, if it's attempting data calls, that slows things down too |
00:04.34 | mdrobnak | the 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.06 | kri5 | mdrobnak: what do you mean by data? |
00:05.22 | mdrobnak | kri5: Like do you see "G,E,3G" near the signal strength? |
00:06.23 | kri5 | nop :/ |
00:07.43 | mdrobnak | ok, are you passing mem=76M on the command line? |
00:07.52 | mdrobnak | because that will slow it down too. |
00:10.36 | kri5 | no i'm not |
00:11.17 | kri5 | i've seen some ppp stuff left on the startup.txt, i just get them off |
00:11.21 | kri5 | tring again |
00:12.45 | mdrobnak | How much ram is it booting with? |
00:13.06 | mdrobnak | 89M? |
00:13.06 | kri5 | tried to boot again, and it boots with locked screen, and no way to unlock it :/ |
00:13.23 | kvaster | kri5: remap home button to MENU in your kernel |
00:13.53 | kri5 | kvaster: how do i do this? |
00:14.06 | kvaster | patch msm_blackstone_pad.c |
00:14.13 | kri5 | arf :/ |
00:14.27 | kri5 | i just took a zImage :/ |
00:14.29 | kvaster | or I can upload my zImage |
00:14.34 | kri5 | i didn't compiled it myself |
00:14.57 | kvaster | one sec - will upoad my kernel to xda |
00:15.00 | kri5 | kvaster: please do :), but do you have the latest patchset for kind of hacky sound? |
00:15.06 | kri5 | kvaster: ok, thx |
00:15.09 | kvaster | ? |
00:15.13 | kvaster | yep |
00:15.17 | kri5 | ok great |
00:15.19 | kvaster | all latest patches |
00:15.21 | kri5 | :D |
00:15.30 | kvaster | but this was not sound patches - this was battery patcj |
00:15.32 | kvaster | patch |
00:15.44 | kvaster | which enabled us to use raphael android image |
00:15.52 | kri5 | i've some problem on my main machine, so i can't build my own kernel :) |
00:16.28 | kri5 | kvaster: but there was a patch in a pastebin from mrblacomm this afternoon, which was sound related, isn't it? |
00:17.07 | kvaster | nope |
00:17.07 | kvaster | it was battery related |
00:17.13 | kvaster | sound was working long ago |
00:17.13 | kri5 | kvaster: ok, my bad :p |
00:17.17 | kvaster | but not in android |
00:17.22 | kri5 | hum |
00:17.52 | kri5 | i see :) |
00:18.38 | *** join/#htc-linux toast (n=quassel@173-137-30-129.pools.spcsdns.net) |
00:19.06 | kvaster | done. see my post on xda |
00:19.44 | kri5 | kvaster: thanks, going to test it right now |
00:20.01 | kri5 | mdrobnak: i think i got nothing related to mem in my cmdline :/ |
00:21.11 | mdrobnak | kri5: 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.29 | kri5 | should i set it to some value? |
00:21.40 | kri5 | and what is the cl option? |
00:22.48 | kvaster | mdrobnak: which value is correct ? |
00:23.20 | mdrobnak | That depends on the device |
00:23.27 | kri5 | for blac100 |
00:23.34 | mdrobnak | and if you're testing Android, keep it at 89M. |
00:28.59 | *** join/#htc-linux kvaster (n=kvaster@live.bn.by) |
00:37.49 | mdrobnak | is re-building system.img. Joy |
00:40.36 | kri5 | mdrobnak: have fun ;) |
00:41.11 | mdrobnak | Hey if this gets me anywhere closer to having a working keymap, I'll be very happy |
00:41.35 | mdrobnak | If I knew the correct identifier, I probably would be able to get away with not updating the img. |
00:42.52 | kvaster | mdrobnak: you're rebuilding android image with patches applied to android from connect-utb ? |
00:43.28 | mdrobnak | I 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.14 | mdrobnak | awesome |
00:46.22 | mdrobnak | I think I completely screwed it up |
00:46.22 | mdrobnak | lol |
00:47.39 | mdrobnak | and then it crashed. |
00:48.49 | kri5 | :D |
00:49.57 | *** join/#htc-linux kvaster (n=kvaster@live.bn.by) |
00:51.29 | enatefox | Let'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.48 | mdrobnak | enatefox: In linux? |
00:54.54 | enatefox | but of course |
00:55.17 | mdrobnak | Technially, yes, right room. I think the gurus are asleep though hehe |
00:55.37 | enatefox | I 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.54 | enatefox | just kind of hoping there were 1+ others for this |
00:57.52 | enatefox | if not I can always feign interest in the relevant subject and offer shill advice. |
00:58.06 | mdrobnak | lol. |
01:00.48 | mdrobnak | I'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.13 | enatefox | as 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.24 | enatefox | so, we've got that |
01:01.38 | ali1234 | O_o |
01:02.28 | ali1234 | enatefox: how much do you know about i2c? |
01:02.57 | enatefox | i know it's a bus |
01:03.21 | enatefox | (dont let them see you thinking/googling the answer...) |
01:03.40 | mdrobnak | lol |
01:03.52 | ali1234 | do you have a shell on kaiser with debugging tools? |
01:04.07 | mdrobnak | enatefox: Compiling code, or just using perl to make your phone explode? lol |
01:04.11 | enatefox | alright, 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.29 | enatefox | a debug shell... I have bash 4 and ADB |
01:04.35 | mdrobnak | wb ali1234 - how's it going? |
01:04.41 | ali1234 | ADB sucks |
01:04.44 | enatefox | true |
01:04.48 | mdrobnak | noooo |
01:04.50 | enatefox | keypads suck worse |
01:04.51 | mdrobnak | adb rules! |
01:04.52 | ali1234 | you need the real stuff |
01:04.53 | mdrobnak | :D |
01:05.11 | ali1234 | bash, /dev/mem, hexdump, and i2c-tools |
01:05.50 | ali1234 | and lots of haret |
01:06.09 | enatefox | i like how pressing up/down to cycle ADB history will execute random commands that it jumbles into dangerous root-level lines |
01:06.25 | enatefox | yea, I've got the gist of getting the info but no one to look it over. |
01:06.50 | ali1234 | so, 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.04 | ali1234 | hmm, a dzo :) |
01:07.12 | enatefox | I'm not looking for a hand holding session just something more than I can find on teh webz |
01:07.17 | enatefox | then a wild dzo appears |
01:07.35 | mdrobnak | ali1234: We don't even have /dev/mem, remember? |
01:07.42 | mdrobnak | OMAP should thought |
01:07.44 | mdrobnak | *though |
01:07.49 | ali1234 | mdrobnak: well you should do............ |
01:08.19 | enatefox | hmm. i have /dev/mem and it's denied even for root |
01:08.38 | ali1234 | you 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.56 | mdrobnak | ali1234: Given up on the memory stuff for a while. 107MB is going to have to suffice for the time being.. |
01:11.12 | ali1234 | enatefox: 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.12 | ali1234 | the 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.28 | enatefox | ali, 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.01 | enatefox | I wouldn't even know where to begin, just trying to revive a dead topic and "you people" know your stuff |
01:14.04 | ali1234 | yes, i read that. but you have to understand that the datasheet will only tell you so much, mainly the i2c stuff |
01:14.12 | enatefox | right |
01:14.41 | ali1234 | the other parts, well, the best doc is going to be the existing code |
01:14.44 | enatefox | i 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.01 | enatefox | inb4 100101011 1010110101 |
01:15.56 | mdrobnak | good luck enatefox ... |
01:16.00 | mdrobnak | I'm off to see Zombieland! |
01:16.04 | enatefox | fair enough |
01:16.08 | mdrobnak | see yas |
01:17.42 | ali1234 | dzo: got a link to that s5k3c1fx datasheet handy? |
01:19.28 | enatefox | damn... had a link myself. |
01:20.41 | enatefox | this 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.15 | enatefox | and sauce: http://www.riddle.ru/dl/ccd/samsung/ds_s5k3c1fx_rev012.pdf |
01:21.35 | enatefox | s5k4b1fx is Vogue, s5k3c1fx is Kaiser |
01:23.24 | ali1234 | ok. you won't need to trace any i2c, that is for sure. you have all that in the datasheet |
01:23.59 | enatefox | proceed... 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.10 | ali1234 | have you tried just running the existing driver on your kaiser? |
01:25.47 | enatefox | Well, 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.14 | enatefox | at 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.25 | ali1234 | yeah |
01:26.47 | ali1234 | see 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.15 | ali1234 | so 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.36 | enatefox | yea, that sounds like a peach |
01:28.01 | enatefox | seems like a higher level transport could work but forget that if I can't write low level calls.. |
01:28.02 | enatefox | I 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.37 | ali1234 | problem is everyone bought new phones |
01:28.47 | ali1234 | i don't even use MSM at all :) |
01:29.58 | enatefox | you 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.24 | ali1234 | i'm still using a wizard from 2006 |
01:30.29 | enatefox | nice |
01:30.43 | ali1234 | which kernel has the vogue driver in it? |
01:30.53 | enatefox | we're running 2.6.25 |
01:31.01 | ali1234 | from linuxtogo? |
01:31.18 | enatefox | 27 got all estranged wife on us and cut things up badly or so my bad analogy goes |
01:31.20 | enatefox | yea |
01:31.42 | enatefox | compcache .5... |
01:32.09 | ali1234 | hmm not in my branch |
01:32.55 | enatefox | see, 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.09 | ali1234 | found it |
01:36.13 | ali1234 | ok, so i looked at kernel/drivers/i2c/chips/s5k4b1fx.c and compared it on the datasheet, and looks very similar |
01:37.10 | enatefox | good? |
01:39.23 | ali1234 | yeah. the two files on the post are probably the only two files you wont need to change |
01:40.09 | enatefox | wait, which 2 files? |
01:40.13 | enatefox | the .c file? |
01:40.31 | ali1234 | drivers/i2c/chips/s5k4b1fx.c and drivers/sbus/char/vfc_i2c.c |
01:40.39 | ali1234 | you might need to change the clocks |
01:40.43 | enatefox | sorry.. just saw it |
01:41.08 | ali1234 | you see these lines like: writel(0xfe8c6a49,MSM_CLK_CTL_BASE+0x40); |
01:42.14 | enatefox | yea |
01:42.25 | ali1234 | what 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.39 | enatefox | that doesn't sound too bad |
01:42.39 | ali1234 | then that's the clock init you need. so youpatch that into the file |
01:43.03 | enatefox | ok.. so to summize for the noobs that are listening, and not for my benefit... |
01:43.04 | ali1234 | if you are lucky you will see it doing the exact same write, then you know it works the same way |
01:43.17 | enatefox | I need to find writes to MSM_CLK_CTL_BASE |
01:43.36 | enatefox | then somehow find the clock speed of the writes |
01:43.45 | ali1234 | just look what value is written |
01:43.49 | enatefox | then adjust a variable that holds the clock speed |
01:43.55 | ali1234 | in this case 0xfe8c6a49 |
01:44.06 | enatefox | and that would be the clock speed? |
01:44.16 | enatefox | there's a 4.) PROFIT!! step in there somewhere |
01:44.23 | ali1234 | sort of. it's a bit field that controls the clock multipliers i guess |
01:44.30 | enatefox | good enough |
01:44.33 | ali1234 | just think of it as a magic number |
01:44.38 | enatefox | right |
01:44.54 | ali1234 | you might need to write in a different place too |
01:45.14 | ali1234 | hell, for all i know, MSM_CLK_CTL_BASE might have a completely different value on kaiser vs vogue |
01:45.24 | enatefox | I'm still going to need help but that certainly explains the process a bit. |
01:46.41 | enatefox | thanks, 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.52 | ali1234 | one more thing |
01:49.04 | ali1234 | do you have /dev/i2c-0 or /dev/i2c/0 or similar? |
01:49.21 | ali1234 | if so, you can use i2c-tools to probe the i2c bus |
01:49.40 | ali1234 | if the chip is enabled you should see the default values as listed on the datasheet |
01:49.47 | ali1234 | then you know it is part working at least |
01:50.49 | enatefox | no.. /dev/input is the only "i" in /dev |
01:53.01 | ali1234 | hmm.... then your first step should probably be getting that set up. |
01:53.19 | enatefox | it's like an Easter egg hunt of my patience and skill level |
01:53.28 | ali1234 | this place is always quiet at this time |
01:54.01 | enatefox | I'll propose we make this so I can "emerge aworkingcamera" for the 2.7 kernel |
01:54.13 | enatefox | I know Linus is holding out on us |
01:54.29 | ali1234 | looks like someone has done this before though: http://dx.infernix.net/kaiser/ |
01:55.06 | ali1234 | although those images are probably out of date |
01:56.02 | enatefox | I'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.07 | enatefox | good find |
01:56.28 | ali1234 | looks like you just need to enable the i2c dev interface on kernel config and compile i2c-tools |
01:57.17 | enatefox | ok, 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.28 | ali1234 | i2c-tools is userspace |
01:57.29 | enatefox | getting the right timer for the writes to MSM_CLK_CTL_BASE |
01:57.38 | enatefox | oh |
01:57.56 | enatefox | um, you're saying the dev interface is kernel side but not the toolset? |
01:58.04 | ali1234 | right |
01:58.15 | ali1234 | you get a /dev/ device and talk to it from userspace... |
01:58.26 | enatefox | ok, that makes sesne |
01:58.50 | ali1234 | so you need to bring that up. and then check if you can see the chip or not |
01:58.58 | ali1234 | if you can, then the clocks are probably right already |
01:59.24 | enatefox | let'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.43 | enatefox | Trying to map out where things can go wrong in my hastily thrown together attempts |
01:59.58 | ali1234 | well, the three things.... |
02:00.02 | ali1234 | any can be wrong |
02:00.38 | ali1234 | i can tell you about i2c only |
02:00.52 | ali1234 | someone who actually knows kaiser hardware can tell you about the other two (at least where to look) |
02:01.05 | ali1234 | but you'll have to hang around for them |
02:01.14 | ali1234 | i guess they're all sleeping |
02:01.31 | enatefox | you've taught me moar than I knew before |
02:01.34 | enatefox | you know, in my job searching I see kernel development jobs starting at $95K. I think I know why |
02:02.23 | enatefox | this 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.45 | ali1234 | seems like there's more than one type of kaiser too :( |
02:04.53 | ali1234 | that will only complicate things |
02:05.05 | enatefox | yea, 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.11 | ali1234 | well, getting it to work will be a matter of painstaking detective work |
02:06.26 | enatefox | oh yes. painstaking indeed |
02:06.34 | ali1234 | it probably will boil down to changing a couple of values somewhere, the problem is knowing which ones... |
02:07.06 | enatefox | unfortunately 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.29 | ali1234 | camera should be a lot easier than wifi |
02:07.43 | ali1234 | not that that really helps |
02:07.44 | enatefox | besides, who cares if my kid makes her first step I don't need to remember that.. |
02:08.07 | ali1234 | the kaiser camera isn't exactly great quality anyway :/ |
02:08.27 | enatefox | hey, you can't fault a 3.0 megapixel beast |
02:08.43 | enatefox | or can you... |
02:09.11 | ali1234 | hmm not too bad |
02:09.40 | enatefox | luckily I don't care about bluetooth because that's been quite the problem apparently. |
02:10.16 | enatefox | are 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.35 | ali1234 | MSM is a really nasty architecture in my opinion |
02:10.50 | ali1234 | the phone has two cpus: linux runs on one, all the hardware is attached to the other |
02:10.57 | ali1234 | and they talk with an undocumented protocol |
02:11.23 | enatefox | wat.. you mean my phone or HTC's in general? this sounds like the Wii all over again |
02:11.33 | ali1234 | the other phones are similar but the second core is only used for the radio bits and is much easier to reverse |
02:11.59 | ali1234 | MSM phones means all the 7x01 phones |
02:12.23 | ali1234 | stuff like the wizard uses the OMAP chips, they are much easier to program |
02:12.29 | enatefox | >undocumented protocol. have to love it |
02:12.49 | ali1234 | like eg. the bluetooth is just connected to a PC compatible UART |
02:12.57 | ali1234 | it doesn't get any easier than that |
02:14.08 | enatefox | hmm. 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.23 | ali1234 | it's for general porting of linux |
02:14.45 | ali1234 | people like to run android on the end result |
02:14.59 | ali1234 | but android itself doesn't need any porting, it only needs a linux kernel |
02:15.21 | ali1234 | so this place is all about figuring out how the hardware works |
02:15.45 | ali1234 | this time last year it was all kaiser stuff |
02:15.45 | enatefox | I 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.50 | ali1234 | now it's all about the new phones |
02:16.13 | enatefox | those damn kids and their MyBooks and FaceSpaces. Can't keep up |
02:18.16 | enatefox | I 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.41 | ali1234 | LG incite is MSM7201A |
02:21.02 | ali1234 | like the new phones everyone has |
02:21.09 | enatefox | with nary a mention of Linux development on it |
02:21.23 | ali1234 | the kernels from here would probably run on it |
02:21.28 | enatefox | o rly |
02:21.47 | ali1234 | just need to patch the LCD drivers and stuff |
02:21.59 | enatefox | </caveat> |
02:22.03 | ali1234 | sure, always |
02:22.17 | enatefox | but that's encouraging |
02:22.41 | enatefox | cost me $30 for that phone |
02:22.43 | ali1234 | these phones are based on system-on-chip designs, which means everything is in one chip |
02:22.51 | ali1234 | which means they're all basically the same inside |
02:23.09 | ali1234 | only the external stuff like LCD and buttons are different |
02:23.36 | enatefox | nice.. I did see LCD4Linux. Maybe I could grab some code from that |
02:23.44 | ali1234 | someone 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.54 | enatefox | Well, 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.53 | mdrobnak | To 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.53 | mdrobnak | ut 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.31 | leobaillard | hi ! |
07:42.43 | tmzt | hello |
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.28 | leobaillard | let's get this f****** wifi to work... |
08:05.09 | tmzt | does it not work for you? |
08:05.11 | tmzt | what device? |
08:05.29 | tmzt | doesn't work for me either, but I think I did somethign wrong and don't have the calibration data |
08:06.43 | leobaillard | well, it works in some very conditions and it's kind of random |
08:07.01 | leobaillard | but I'm trying to make a script containing a procedure that works most of the time |
08:07.24 | leobaillard | but 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.47 | leobaillard | pfff /o\ |
08:24.09 | *** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz) |
08:29.30 | tmzt | cr2: http://thread.gmane.org/gmane.linux.ports.arm.kernel/ |
08:29.47 | tmzt | not our chip, but 2k and finally explains what the contents of oob structs are |
08:29.55 | tmzt | ecclayout I mean |
08:30.08 | leobaillard | the only good news that I see here is that I can get the wifi up without turning it on in winmo |
08:30.15 | tmzt | so maybe we can get compatible with wm :) |
08:30.24 | tmzt | leobaillard: sure, that shouldn't matter |
08:31.49 | leobaillard | yeah, but phh said at the early developments of it that it was necessary |
08:33.48 | leobaillard | what are you working on tmzt ? |
08:35.57 | tmzt | looking into user gsm stacks |
08:36.21 | tmzt | unlike raph100 (I think) I don't have full sound working in calls |
08:36.38 | tmzt | but I'd like some plans for when I do to get my linux phone working |
08:39.46 | leobaillard | okay |
08:40.33 | leobaillard | do you know where I can find a kernel version already used in a working htc linux device like dream, hero, whatever ? |
08:42.42 | tmzt | leobaillard: sure, android.git.kernel.org |
08:44.21 | leobaillard | thx |
09:05.52 | leobaillard | I may have found the right procedure \o/ ! testing... |
09:06.07 | tmzt | cool |
09:06.10 | tmzt | please document |
09:06.21 | leobaillard | it's fast and throws merely no debug message |
09:06.40 | leobaillard | BUT, I have to try it again and again to see if it wasn't just luck... |
09:06.59 | leobaillard | which 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.15 | leobaillard | it seems to work well for the wifi acivation :D let's script it... |
09:30.31 | leobaillard | it 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.00 | rayman18 | hi all |
10:30.57 | rayman18 | one queestion, what mean the last comit on the git " hack in snd.c" ?¿ |
10:31.41 | tmzt | alsa support? |
10:32.15 | Captnoord | its a hack to check if the implementation is correct...... |
10:33.13 | rayman18 | ok |
10:33.20 | rayman18 | <PROTECTED> |
10:33.45 | *** join/#htc-linux stefand (n=stefand@194.7.153.125) |
10:34.03 | Captnoord | and like tmzt is saying its for the alsa support |
10:35.18 | rayman18 | ok, its is clear now |
10:35.21 | rayman18 | thanks |
10:35.22 | tmzt | oh, wrong snd.c |
10:35.24 | rayman18 | <PROTECTED> |
10:36.25 | tmzt | how did msm sdcc work with wrong dma channels? |
10:36.36 | tmzt | is this needed for wl12xx? |
10:43.15 | Captnoord | tmzt: its maybe because if you always use the wrong dma channels... nothings wrong and everything should work.... |
10:43.16 | Captnoord | :P |
10:44.11 | Captnoord | so 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.34 | tmzt | right, but if wifi works won't it interfere without that patch? |
10:45.01 | Captnoord | yup.... |
10:45.10 | tmzt | ok |
10:45.11 | Captnoord | it will interfere |
10:45.13 | Captnoord | but.... |
10:45.15 | tmzt | so I need the patch |
10:45.20 | Captnoord | I think so |
10:45.51 | Captnoord | it could work... but it would result in loads of errors on both the wifi side and the sdcc side |
10:45.59 | Captnoord | maybe the crc erros are coming from that |
10:46.13 | tmzt | possible, can you paste a little? |
10:46.28 | Captnoord | nope.. not atm.... working... |
10:46.31 | Captnoord | no 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.37 | tmzt | well, if anyone can help get this adapted to msm |
12:58.38 | tmzt | http://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.05 | phh | apt: 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.13 | Gnutoo | leviathan, with a friend we tried to debug the oops |
17:07.39 | Gnutoo | leviathan, it was an error message that made the oops...we now just have to find which one |
17:08.21 | phh | ab heisenbug ? |
17:08.23 | phh | anù* |
17:08.24 | phh | an* |
17:10.38 | dcordes | phh, heisenbug? |
17:11.06 | phh | a bug caused by a measure (here a debugging message) |
17:11.35 | phh | in 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.51 | Gnutoo | ok |
17:14.54 | Gnutoo | lol |
17:15.12 | Gnutoo | s/message/ |
17:15.22 | Gnutoo | things like EINVAL etc... |
17:16.23 | Gnutoo | lol 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.55 | rafyvitto | hey guys i got a question |
17:45.23 | swc|666 | sorry, this channel is only girls, not guys |
17:45.28 | swc|666 | ;) |
17:46.01 | rafyvitto | has 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.29 | rafyvitto | i mean since the sprint hero is a cdma phone, and 1.6 donut brought cdma support =] |
17:49.14 | phh | rafyvitto: someone already did some 1.6 builds |
17:49.58 | phh | rafyvitto: no pm. |
17:50.18 | phh | it was a generic build, so it shouldn't be too specific |
17:50.49 | rafyvitto | its squash, il have to converted back to img |
17:51.00 | phh | ?!? |
17:51.15 | phh | rootfs is squashfs ? |
17:52.11 | rafyvitto | is that generic image you reffer to squashfs? |
17:58.02 | phh | maybe 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.49 | rafyvitto | let see if it works |
18:24.56 | rafyvitto | its booting |
18:25.11 | rafyvitto | its succesfully created swap files |
18:25.53 | phh | leobaillard: !! |
18:26.17 | phh | leobaillard: 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.47 | leobaillard | phh: I'm eating, telling you after that, but yes, some progress... :) |
18:35.55 | phh | ok :) |
18:36.30 | cr2 | dcordes: ping |
18:38.30 | cr2 | phh: your diff from yesterday. includes many "not our" patches |
18:38.32 | rafyvitto | and nothing happend black screen for more than 10min >< |
18:38.43 | phh | cr2: i know :/ |
18:38.55 | phh | cr2: android thing ... |
18:39.53 | cr2 | phh: maybe it's easier to grep for CONFIG_HTC* |
18:40.09 | cr2 | phh: but not all our changes are ifdef'd |
18:40.10 | phh | cr2: maybe dcordes know how to get a big diff after the kernel merges |
18:40.36 | cr2 | i think it's a good idea to try to ifdef our changes. |
18:41.05 | cr2 | and hide the proc_comm_wince, clock control and gpio alt behind proc_comm |
18:41.34 | dcordes | cr2, ello |
18:42.09 | cr2 | hi dcordes |
18:42.23 | cr2 | dcordes: there was a blac100 patch yesterday |
18:42.25 | *** join/#htc-linux gekas (i=4d69cbdc@gateway/web/freenode/x-lrjdffcnxtstqpwd) |
18:42.51 | cr2 | phh: this one -> |
18:42.55 | cr2 | diff -ur linux-2.6.27/arch/arm/plat-omap/usb.c kernel/arch/arm/plat-omap/usb.c |
18:42.56 | cr2 | --- linux-2.6.27/arch/arm/plat-omap/usb.c2008-10-10 00:13:53.000000000 +0200 |
18:42.57 | cr2 | +++ kernel/arch/arm/plat-omap/usb.c2009-09-16 19:20:14.280057252 +0200 |
18:43.15 | cr2 | has even nothing to do with msm |
18:43.47 | dcordes | some timestamp ? |
18:45.47 | kvaster | cr2: do you need latest patch for blac ? |
18:46.13 | cr2 | kvaster: pastebin it |
18:46.26 | cr2 | kvaster: not .ca |
18:46.46 | cr2 | if 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.09 | cybersyx_ | hi cr2 |
19:01.09 | kvaster | cr2: http://pastebin.com/m52f7411 |
19:01.17 | kvaster | it's blacm patch + small addition |
19:01.41 | cybersyx_ | 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.56 | phh | kvaster: your board-htcblackstone.h seems weird :p |
19:04.17 | kvaster | mmm |
19:04.33 | kvaster | :( |
19:04.40 | phh | i mean the RAPH100_things |
19:07.58 | cr2 | + .smem_offset = 0xfc110, /* cr2: 0xfc00c, 0xfc110 */ |
19:08.02 | cr2 | i 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.48 | cr2 | + msm_battery_pdata.smem_offset = 0xfc110; /* cr2: 0xfc00c*/ |
19:08.50 | cr2 | here too |
19:09.12 | mblancom | hi all! |
19:09.36 | cr2 | mddi_client_epson.c needs more code, but it's a good beginning |
19:09.39 | cr2 | hi mblancom |
19:09.44 | *** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it) |
19:09.49 | mblancom | hi ! |
19:09.57 | townkat | hi mblancom |
19:10.01 | *** join/#htc-linux Gnutoo (n=gnutoo@host137-159-dynamic.54-79-r.retail.telecomitalia.it) |
19:10.04 | cr2 | mblancom: what is the purpose of this patch |
19:10.11 | cr2 | + .smem_offset = 0xfc110, /* cr2: 0xfc00c, 0xfc110 */ |
19:11.09 | mblancom | well, i remember asking about the specific changes needed to be able to start android wihout fall in the power off trap. |
19:12.06 | cr2 | http://htc-linux.org/wiki/index.php?title=RaphaelMemoryMap |
19:12.10 | Gnutoo | hi leviathan the oops will be fixed soon |
19:12.10 | leviathan | Gnutoo: wonderfull |
19:12.11 | Gnutoo | leviathan, I'm debuging it but I bet the code is a at a point I know: |
19:12.26 | mblancom | and this address is from dwaradzyn, the comment says that after sending to you the battery.dll you said somethin about this address |
19:12.34 | cr2 | says that 0xfc00c has completely different purpose |
19:12.45 | leviathan | I showed the working OpenMoko to my comilitones this morning, some nearly freaked out, because we got it running ^_^ |
19:13.10 | cr2 | leviathan: hmm. why is it so surprising ? |
19:13.41 | mblancom | cr2: perhaps i missunderstood something |
19:13.49 | cr2 | mblancom: blac100 is very similar to raph100. only the epson mddi is different. and some gpios |
19:14.08 | leviathan | Gnutoo: because they didnt believe that it could work so soon =) |
19:14.26 | Gnutoo | leviathan, I don't know if it will work but oops will be debuged |
19:14.37 | Gnutoo | you never know what's next |
19:14.50 | mblancom | cr2: ok, lets erase the comment then. |
19:15.08 | cr2 | yes, your patch is 100% raph100 |
19:15.09 | Gnutoo | basically there is this code: |
19:15.13 | Gnutoo | that is suspect: |
19:15.14 | cr2 | compatible |
19:15.37 | cr2 | mblancom: btw, what about the headset/speaker ? |
19:16.01 | Gnutoo | if (reply->xid != req->xid) {kfree(reply);continue;}if (reply->reply_stat != 0) {rc = -EPERM;break;} |
19:16.02 | cr2 | mblancom: i've seen in the source, that it's necessary to apply the gpio power to eenable it |
19:16.34 | cr2 | i think we have traced it on a real blac100 too |
19:16.50 | Gnutoo | anyway I know more or less where it is located...recompiling a cleaner kernel with debug for addr2line |
19:16.59 | mblancom | cr2: 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.44 | cr2 | mblancom: i've added the gpio to wiki, and you can recheck it with 'watch gpios' in haret |
19:18.05 | mblancom | cr2: 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.20 | cr2 | mblancom: btw, what about BT? the setup is the same as on raph100 i think |
19:19.32 | cr2 | 94 0x5e 26 I irq CAP_SENz (NAVI) ext SPK related |
19:19.47 | mblancom | cr2: I was following your advances with BT, Wifi, GPS, etc, just waiting to know if they work in android... |
19:19.51 | cr2 | the speaker amplifier power gpio |
19:20.05 | cr2 | ~ping dcordes |
19:20.06 | apt | pong dcordes |
19:20.52 | phh | mblancom: bluetooth works on android |
19:20.57 | phh | the other one will be tough |
19:21.15 | mblancom | phh: nice to ear that |
19:21.16 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
19:21.19 | cr2 | mblancom: sound needs some more research in the ADIE and AudioPara area |
19:21.46 | phh | mblancom: 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.03 | mblancom | cr2: I remember dwaradzyn posting his AudioParam.c ... |
19:22.05 | dcordes | leviathan, I hope nobody hyperventilated |
19:22.43 | cr2 | dcordes: can we clone the current blackstone board file for rhod/topa ? |
19:22.47 | leviathan | dcordes: They found the work very cool. So we got respect from students in switzerland |
19:22.56 | leviathan | its already something |
19:23.06 | leviathan | they find it cool, that someone does it |
19:23.13 | leviathan | :D |
19:24.18 | mblancom | go to dinner, bbl |
19:24.34 | cr2 | leviathan: when i show the angstrom booting on my phones, everybodysays i'm crazy :) |
19:24.41 | dcordes | cr2, yes |
19:24.55 | cr2 | leviathan: on all my phones :) |
19:24.55 | dcordes | leviathan, I don't know if there are many unix geeks among my fellow students |
19:25.00 | phh | cr2: but you are. |
19:25.10 | cr2 | phh: LOL |
19:25.12 | phh | (and we love that :) |
19:25.40 | cr2 | phh: eh ? i'm crazy ? |
19:25.45 | dcordes | but showing angstrom boot on a nice smartphone makes everybody think you are totally super crazy geek that's true :) |
19:26.05 | gekas | kinda |
19:26.05 | dcordes | found the same phenomenon |
19:26.14 | phh | well angstrom is unusable for me because of no keyboard :( |
19:26.21 | cr2 | dcordes: yeah, on the most expensive smartphones ;) |
19:26.49 | dcordes | well whatever has scrolling white on black system messages |
19:26.59 | leviathan | they is only perfect, if you can show, that everything is working fine or at least working minimal |
19:27.09 | cr2 | dcordes: don't forget the nice penguin |
19:27.14 | phh | :))) |
19:28.02 | dcordes | cr2, 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.08 | cr2 | most people who know me have already learned that windows sucks, and linux should run everywhere. |
19:28.38 | dcordes | cr2, what's is the key of your success? |
19:28.52 | dcordes | s/what's/what/ |
19:28.59 | cr2 | so in the end, they are not surprised that linux is running on my cellphone. |
19:29.17 | phh | leobaillard: ? |
19:29.36 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
19:29.42 | cr2 | just amazed that it's so easily possible for a qualified person to do it |
19:30.37 | phh | cr2: 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.38 | dcordes | I mean I didn't convince too many people about linux superiority |
19:31.00 | cr2 | phh: that's why i bought raph, and not kaiser |
19:31.06 | phh | :) |
19:31.28 | dcordes | cr2, look at the pxa ports |
19:31.34 | dcordes | s/cr2/phh/ |
19:31.37 | dcordes | ^^ |
19:32.39 | leviathan | I'm building an shr-image right now and will install alsa,vlc,mplayer and midori |
19:32.47 | leviathan | then I'll try alsa again |
19:37.23 | dcordes | leviathan, alsa will be nice |
19:38.00 | dcordes | leviathan, did you boot a qtopia rootfs? |
19:39.04 | cr2 | leviathan: yeah, i'd like to have a qtopia roots too. even without the phone support |
19:39.23 | leviathan | hmm |
19:40.02 | leviathan | Would 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.28 | cr2 | leviathan: yu can aask BabelO aboiut it :) |
19:42.55 | leviathan | http://qtopia.net/modules/devices/ |
19:43.03 | leviathan | ok, would be nice, to have it like this |
19:43.08 | leviathan | very smart gui-design |
19:43.14 | leviathan | thats why I love Qt |
19:43.36 | cr2 | leviathan: i'd like to run this program http://qlandkarte.org/ |
19:44.09 | cr2 | it was already done on several devices earlier. |
19:44.28 | cr2 | they just didn't either had 100% linux support or no gps |
19:44.39 | leviathan | is this qt-landkarte able to read open streetmap |
19:44.41 | cr2 | we have a very good change to change that now |
19:44.57 | leviathan | dont believe it, one german word and I begin to write german again -_- |
19:45.00 | cr2 | leviathan: the raster background ? yes |
19:45.10 | cr2 | hehe |
19:45.17 | BabelO | hi |
19:45.21 | BabelO | what happen ? :) |
19:45.25 | leviathan | hiho |
19:45.43 | cr2 | leviathan: if you want vector maps, use roadmap. it also has qt4 support |
19:45.44 | leviathan | We talked about to port qtopia-phone-x11 onto the htcdream |
19:45.45 | leviathan | =) |
19:45.52 | cr2 | BabelO: we want to build qtopia |
19:46.13 | leviathan | I'm building shr atm |
19:46.23 | leviathan | didnt die yet |
19:47.09 | leviathan | afterwards I can also try to build qtopia-phone |
19:47.12 | Gnutoo | mmm does the usb gadget uses the rpc? |
19:47.33 | leviathan | nope, not that I knew it |
19:47.45 | leviathan | it only uses ipv6 |
19:47.58 | Gnutoo | strange because when I remove some rpc part I've no usb |
19:47.59 | leviathan | its the only function I registered in dmesg and console |
19:48.08 | Gnutoo | ok |
19:48.29 | Gnutoo | I'll look if I use function |
19:48.35 | BabelO | Gnutoo: you remove nfs maybe ? |
19:48.45 | Gnutoo | no rpc not for nfs |
19:48.49 | Gnutoo | but for the msm thing |
19:48.54 | leviathan | perhaps they tinkered something with syscalls and rpc... who knows... >_< |
19:49.28 | cr2 | leviathan: it needs some more c++ code. like "ril" |
19:49.28 | *** join/#htc-linux cr2 (n=cr2@109.84.202.109) |
19:49.29 | cr2 | dcordes: i suggest to copy the blacstone to topaz. then we can support rhod100 with it too |
19:49.36 | leviathan | smokes a cigarette$ |
19:49.49 | cr2 | and then apply the patch by mblancom |
19:50.10 | Gnutoo | # CONFIG_USB_FUNCTION is not set |
19:50.29 | Gnutoo | cr2, ril is in C |
19:50.41 | cr2 | Gnutoo: qtopia is c++ |
19:50.45 | Gnutoo | yes |
19:50.46 | Gnutoo | it is |
19:50.51 | Gnutoo | but android's ril is C |
19:51.04 | Gnutoo | there is another ril from qtopia? |
19:51.10 | cr2 | ok, that why i said "ril" |
19:51.16 | dcordes | cr2, ok I'll have dinner then we can put it |
19:51.23 | Gnutoo | ah ok |
19:51.25 | cr2 | the modem interface laye |
19:51.26 | Gnutoo | sorry then |
19:51.37 | *** join/#htc-linux stickboy (n=anonymou@128.153.176.141) |
19:51.37 | Gnutoo | they use their own... |
19:52.05 | cr2 | but it was already done for the moko phone |
19:52.53 | dilinger | parts of ril are in c++ |
19:53.32 | cr2 | we just need to exten calypso support to msm AT |
19:53.53 | cr2 | most of it is standard AT anyway |
19:54.16 | cr2 | and the weird simtoolkit stuff can wait. |
19:57.23 | leviathan | re |
19:57.25 | gekas | http://forum.xda-developers.com/showthread.php?t=567870 omg... |
19:59.41 | mblancom | hi again... |
20:03.03 | Gnutoo | maybe I need to recompile the kernel again |
20:03.13 | Gnutoo | (recompile means change important options) |
20:04.52 | cr2 | phh: have you looked at hte SDIO spec ? |
20:04.58 | leviathan | Gnutoo: Try my options =) |
20:05.05 | Gnutoo | no i mean for debugging |
20:05.11 | Gnutoo | like remove -o3 |
20:05.25 | leviathan | Gnutoo: my options allow very good tracing in dmesg |
20:05.27 | leviathan | :) |
20:05.27 | Gnutoo | remove the preemptive |
20:05.57 | leviathan | but that allows better performance, like on a workstation |
20:06.00 | cr2 | leviathan: the biggest problem i have with dream and 7201A is wtf is /dev/mem not working ? |
20:06.01 | leviathan | okee, it also needs aku |
20:06.14 | leviathan | cr2: hmm |
20:06.17 | leviathan | yaah |
20:06.17 | *** join/#htc-linux PocketIRC111 (n=pocketir@32.174.162.6) |
20:06.30 | leviathan | could be because its memory access driver |
20:06.54 | leviathan | and perhaps the addresses arent correct for these devices and you access into the digital nirvana |
20:07.14 | cr2 | no, you get a nerror messae |
20:07.28 | cr2 | = some code traps this access |
20:07.51 | cr2 | on accessing nirvana you will get a segfault in the kernel = oops |
20:09.54 | leviathan | hmm, true |
20:11.17 | cr2 | hehe |
20:14.24 | *** join/#htc-linux patp (n=patp@87.194.56.160) |
20:14.31 | patp | hiya |
20:14.42 | *** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes) |
20:15.00 | patp | formatting sd card, what's the best allocation unit size? |
20:15.11 | dcordes | awesome 100+ users |
20:15.32 | cr2 | lol |
20:15.48 | cr2 | dcordes: add topa/rhod, and there will be more :) |
20:16.15 | dcordes | good propaganda. one reason why I wanted to see msm in OE |
20:16.28 | cr2 | patp: SD blocksize is 512, SDHC is 2048 afair |
20:16.47 | Gnutoo | leviathan, 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.01 | dcordes | lol I have no toolchain :-( |
20:17.16 | richard333 | hey guys i have a question |
20:17.33 | richard333 | how do i emulate the pressing of the trackball down with my kaiser |
20:18.23 | richard333 | or should i ask @ android? |
20:18.25 | dcordes | richard333, doesn't the kaiser have an "enter" key in the middle of the front keypad? you could use that |
20:19.22 | leviathan | Gnutoo: hmm, I'll past it into pastebin |
20:19.25 | richard333 | @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.26 | leviathan | then you can look |
20:19.29 | Gnutoo | ok |
20:20.48 | patp | cr2: thx |
20:20.51 | leviathan | http://pastebin.com/m6d29b6cf |
20:21.23 | *** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
20:21.40 | dcordes | richard333, 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.34 | dcordes | richard333, the relevant bits are located in this file arch/arm/mach-msm/board-kaiser-keypad.c |
20:22.42 | Gnutoo | leviathan, how do you enable -o0 ? |
20:22.49 | Gnutoo | s/o/O |
20:23.25 | dcordes | richard333, see the coment in line 11: "* PAD Center = KEY_OK" |
20:24.00 | Gnutoo | leviathan, you seem to use CONFIG_CC_OPTIMIZE_FOR_SIZE=y |
20:24.05 | dcordes | it's the good old marbalon driver |
20:24.36 | richard333 | @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.26 | patp | I'm really hacked off with this... the exact same sd card with the exact same files on it, today is not recognised. |
20:25.35 | dcordes | richard333, did you navigate to the file? |
20:26.03 | richard333 | not yet |
20:26.29 | richard333 | ok im there |
20:26.49 | dcordes | richard333, I can't recall where the dream trackball driver is |
20:28.20 | leviathan | Gnutoo: I have one very enoying problem with my htcdream |
20:28.30 | Gnutoo | leviathan, yes? |
20:28.34 | leviathan | how can I set the keymap in the kernel? |
20:28.50 | leviathan | I cant type "-" on my hw-keyboard |
20:29.03 | Gnutoo | leviathan, I didn't look yet but there is a driver that has all keymaps in the boards files |
20:29.05 | leviathan | they keymap is crap |
20:29.08 | Gnutoo | it has qwerty |
20:29.19 | leviathan | okee |
20:29.23 | leviathan | a driver you say? |
20:29.26 | leviathan | where? |
20:29.29 | phh | cr2: 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.41 | Gnutoo | /* arch/arm/mach-msm/board-trout-keypad.c |
20:29.58 | Gnutoo | leviathan, but can't it be done in userspace? |
20:30.18 | dcordes | cr2, ok only copy the boardfile for now? |
20:30.49 | richard333 | @gnutoo that is the dream keypad drivers? |
20:31.14 | Gnutoo | richard333, yes |
20:31.28 | Gnutoo | keyboard =? keypad? |
20:31.37 | leviathan | it is done in the userspace |
20:31.44 | leviathan | <PROTECTED> |
20:31.44 | leviathan | <PROTECTED> |
20:31.44 | leviathan | <PROTECTED> |
20:31.44 | leviathan | <PROTECTED> |
20:31.44 | leviathan | <PROTECTED> |
20:31.45 | leviathan | <PROTECTED> |
20:31.48 | leviathan | <PROTECTED> |
20:31.55 | cr2 | dcordes: clone the *blackstone* files |
20:32.00 | leviathan | I just need the keyfile |
20:32.00 | Gnutoo | ok |
20:32.50 | Gnutoo | leviathan, look in the intializations files |
20:33.59 | leviathan | fuck'n crap, the hacked some binary stuff for layout |
20:34.09 | leviathan | I'll have to make my own layout -_- |
20:34.11 | Gnutoo | ??? |
20:34.13 | Gnutoo | ah ok |
20:34.21 | leviathan | http://bzed.de/ |
20:34.22 | Gnutoo | what do you mean by some binary stuff? |
20:34.27 | leviathan | http://bzed.de/posts/2009/08/german_keyboard_layout_for_cyanogenmod/ |
20:34.34 | leviathan | look there |
20:35.14 | richard333 | so basically there isn't an utility winmo style where i can remap my keys? |
20:36.00 | Gnutoo | leviathan, setkey 0x0 0x38 0x0 |
20:36.08 | Gnutoo | maybe it can set the keys |
20:36.13 | richard333 | i'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.15 | leviathan | okee |
20:36.16 | cr2 | the sdcard is much slower than nand. at least in wince |
20:36.39 | cr2 | leviathan: LC_LANG ? |
20:42.28 | leviathan | cr2: hmm |
20:42.46 | leviathan | anyway. first I build an shr image |
20:42.55 | leviathan | then Ill look further |
20:43.32 | dcordes | Topaz is a silicate mineral of aluminium and fluorine with the chemical formula Al2SiO4(F,OH)2. |
20:44.15 | cr2 | lol |
20:44.17 | leviathan | Gnutoo: did you upload the alsa drivers into git now? |
20:44.21 | Gnutoo | not yet |
20:44.26 | Gnutoo | you have the patch |
20:44.32 | Gnutoo | and I'm still debugging them |
20:44.40 | cr2 | something new: |
20:44.40 | Gnutoo | I know more or less where the problem is |
20:44.42 | cr2 | 00000001 00000006 00000001 |
20:44.48 | Gnutoo | but I need better debugging options |
20:44.53 | Gnutoo | for having a better trace |
20:44.59 | leviathan | ok |
20:45.02 | leviathan | try mine |
20:45.02 | Gnutoo | -o0 is compiling |
20:45.03 | leviathan | =) |
20:45.07 | leviathan | ok |
20:45.15 | Gnutoo | #oe guys told me that it was in the Makefile |
20:45.18 | Gnutoo | the top one |
20:45.23 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
20:45.24 | cr2 | #define RPCROUTER_CTRL_CMD_REMOVE_CLIENT 6 |
20:45.26 | cr2 | aha |
20:45.51 | phh | hu ? rpcrouter says to the client to drop connection ? |
20:47.22 | richard333 | so can anyone guide me as to finding the htc dream key mappings file |
20:51.26 | leviathan | http://www.handy-faq.de/forum/htc_dream_google_g1_forum/87817-google_g1_qwertz_tastatur_wiederherstellen.html |
20:51.31 | leviathan | youll have to register |
20:51.52 | leviathan | for openmoko I'll have to write my own |
20:51.56 | leviathan | its so fuck'n exotic keymapping |
20:52.01 | cr2 | phh: see such message for the first time |
20:52.12 | leviathan | I'll have to associate them my self |
20:52.21 | Captnoord | cr2 that stuff is in the rpc dll's on wince |
20:52.27 | Captnoord | but you already knew that |
20:52.42 | cr2 | phh: tried to connect the BT headset |
20:52.46 | cr2 | Captnoord: yes |
20:52.57 | phh | cr2: didn't work i guess ? |
20:52.59 | dcordes | cr2, pushd |
20:53.11 | phh | it should work for A2DP actually |
20:53.23 | phh | since android do it in software |
20:54.01 | cr2 | phh: in wince |
20:54.05 | cr2 | 00000001 00000006 00000001 fffffffe 00000000 00000014 00000000 fffffffe 00000006 00000001 8cf0f3fe 02293f18 0228e3f8 |
20:54.07 | cr2 | 00000001 00000006 00000001 fffffffe 00000000 00000014 00000000 fffffffe 00000006 00000001 00000001 02293f18 0228e3f8 |
20:54.38 | phh | you think i understand raw rpc replies ? :p |
20:54.42 | cr2 | the arm11 rpcrouter tells the arm9 router about client close |
20:55.15 | cr2 | need to lookup the syntax |
20:55.39 | cr2 | cmd + |
20:55.47 | cr2 | <PROTECTED> |
20:55.48 | cr2 | <PROTECTED> |
20:55.50 | cr2 | <PROTECTED> |
20:55.50 | *** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo) |
20:55.51 | cr2 | <PROTECTED> |
20:55.53 | cr2 | <PROTECTED> |
20:56.33 | cr2 | 00000006 00000001 8cf0f3fe |
20:57.30 | cr2 | =closed ARM11 cid=8cf0f3fe |
20:57.49 | cr2 | this one is more cryptic |
20:57.51 | cr2 | 00000006 00000001 00000001 |
20:58.04 | cr2 | what is cid=1 on wince ?? |
20:59.43 | dcordes | lassen sie mich durch, ich spreche msm rpc |
21:00.26 | phh | :) |
21:01.22 | phh | cr2: rpcrouter or god i think :p |
21:02.48 | *** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo) |
21:04.30 | cr2 | phh: rpcrouter is cid=-2 |
21:04.36 | cr2 | 0xfffffffe |
21:05.28 | Captnoord | wasn't 1 something like global |
21:05.46 | Captnoord | or 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.19 | cr2 | Captnoord: i don't understand why wince periodicaly changes the ept of the CB servers. |
21:10.40 | cr2 | the same code is available on linux too. but the cid seems to be allocated only once. |
21:11.15 | [1]Captnoord | ept? |
21:11.29 | [1]Captnoord | maybe to allow multiple buffers |
21:11.37 | [1]Captnoord | async system |
21:11.56 | [1]Captnoord | or |
21:12.04 | [1]Captnoord | hmmm |
21:12.05 | [1]Captnoord | dono |
21:12.14 | [1]Captnoord | haven't been reading the asm lately |
21:12.21 | [1]Captnoord | been studing a lot |
21:13.11 | *** join/#htc-linux rayman18 (n=opera@residL-102-227.uc3m.es) |
21:14.30 | cr2 | but i don't get the GPS messages to the CB if i do the same |
21:14.40 | cr2 | strange |
21:14.50 | cr2 | something is still not right in the RPC setup |
21:16.13 | [1]Captnoord | cr2 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.29 | chemical_at_work | progress² |
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.13 | cr2 | ok, so i've catched the moment where the CB muxed ept is disabled, and all CB servers are reregistered again |
21:19.49 | cr2 | maybe we should do it on the adsp_cid :) |
21:20.22 | cr2 | hmm. but it's not the adsp cid here. |
21:29.33 | Gnutoo | ok here what I found |
21:29.38 | Gnutoo | leviathan, ping |
21:29.50 | leviathan | Gnutoo: yeah? |
21:29.55 | leviathan | sry, was smoking |
21:29.57 | leviathan | =) |
21:30.18 | Gnutoo | in msm_rpc_call_reply ept is null when moving the second bar in alsamixer |
21:30.30 | Gnutoo | so that's what cause the kernel oops |
21:30.38 | leviathan | oh, ok |
21:30.39 | Gnutoo | ept is the endpoint |
21:30.57 | Gnutoo | the thing is that I looked at the bottom of the backtrace only |
21:31.03 | leviathan | ok |
21:31.04 | Gnutoo | instead of looking at the top of it who has: |
21:31.28 | Gnutoo | [ 97.697021] pc : [<c0038640>] lr : [<c003876c>] psr: 20000013 |
21:31.32 | Gnutoo | note the pc... |
21:31.37 | Gnutoo | so I went to the pc line |
21:31.42 | Gnutoo | and I got the offending code |
21:31.50 | Gnutoo | that was before all my printk |
21:32.05 | Gnutoo | putting a check and returning -1 make it not segfault |
21:32.11 | Gnutoo | but the bar doesn't seem to work |
21:32.25 | Gnutoo | so we must have a valid endpoint |
21:33.02 | leviathan | which file, which line? |
21:33.06 | Gnutoo | ok |
21:33.12 | Gnutoo | the line you'll find it |
21:33.14 | leviathan | wants to take a look |
21:33.16 | Gnutoo | for the file it's: |
21:33.34 | Gnutoo | arch/arm/mach-msm/smd_rpcrouter.c |
21:34.27 | Gnutoo | grep for if (ept->dst_pid == 0xffffffff) |
21:34.31 | leviathan | ok |
21:34.36 | Gnutoo | so 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.02 | Gnutoo | so we must: |
21:35.05 | Gnutoo | *check for ept |
21:35.14 | Gnutoo | *find why ept is null |
21:35.32 | Gnutoo | if we do so we should get a better volume |
21:35.41 | Gnutoo | and then we implement routing |
21:35.42 | leviathan | okee |
21:35.45 | Gnutoo | like in the openmoko |
21:36.05 | Gnutoo | with all theses switchs |
21:36.22 | Gnutoo | I'll go bye |
21:36.24 | leviathan | hmm, we could make a hack with changing the value to highest value possible as default |
21:36.39 | leviathan | ok |
21:36.42 | Gnutoo | yes you could but I prefer making it work |
21:36.53 | Gnutoo | so: |
21:36.59 | Gnutoo | *you put the higest volume |
21:37.11 | Gnutoo | *I'll try to finish debugging when I'll have time |
21:37.19 | leviathan | ok |
21:37.24 | Gnutoo | because I could have returned -1 at higger level |
21:37.35 | Gnutoo | and put a high value for volume |
21:37.40 | Gnutoo | but I didn't like it |
21:37.43 | Gnutoo | so I debugged |
21:37.48 | leviathan | pls upload the current alsa driver, so that I can develop on it |
21:37.56 | Gnutoo | you've got the patch |
21:38.06 | leviathan | yeah, I mean into gitorious |
21:38.07 | Gnutoo | all what you need is to check for null |
21:38.13 | Gnutoo | ok I'll do it once it's ready |
21:38.21 | leviathan | ok |
21:38.26 | Gnutoo | can I go now:? |
21:38.37 | leviathan | yeah |
21:38.40 | leviathan | gn8 |
21:38.54 | leviathan | ill go to sleep now anyway |
21:38.55 | Gnutoo | thanks bye |
21:38.57 | leviathan | bye |
21:44.37 | leobaillard | bye 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.01 | dcordes | yawns |
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.00 | dcordes | nn |
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) |