| 00:00.01 | marajin | they tried it as far back as the hermes but the hermes lacks the RAM for WM7 |
| 00:00.08 | tcccp | su - |
| 00:00.08 | tcccp | r007b4by |
| 00:00.16 | dcordes_ | what did ali say? you must try to ommit as many landmarks in the hierarchy as possible |
| 00:00.43 | dcordes_ | so if at all one should contact htc |
| 00:00.43 | marajin | wonders what dcordes_ is on about. |
| 00:00.55 | dcordes_ | it's a complete different thought sorry |
| 00:01.02 | marajin | qualcomm would seem the final step man |
| 00:01.03 | marajin | but yeah |
| 00:01.13 | marajin | QC, MS and HTC aren't going to tell us a thing |
| 00:01.16 | marajin | legal blah blha |
| 00:01.32 | dcordes_ | see what ali said |
| 00:01.38 | ali1234 | qualcomm are the only ones who could legally |
| 00:01.50 | marajin | yeah |
| 00:01.51 | ali1234 | everyone else would be made to sign an NDA by QC |
| 00:01.55 | marajin | precisely |
| 00:02.00 | marajin | NDAs.. bane of my fuckin' life |
| 00:29.35 | tmzt | what are you looking for, the gl stuff? |
| 00:29.49 | tmzt | gles |
| 00:41.09 | dcordes_ | tmzt: no the discussion was triggered by sd talk |
| 00:48.40 | tmzt | sd? |
| 00:49.47 | dcordes_ | the dma problems with kaiser mmc driver |
| 00:50.17 | tmzt | who were you asking? |
| 00:51.25 | dcordes_ | for documents? |
| 00:52.55 | tmzt | I thought you said "no discussion was triggered" |
| 00:52.57 | tmzt | ok |
| 00:55.15 | dcordes_ | sorry |
| 00:55.22 | tmzt | that log you posted was for 2.6.24? |
| 00:55.40 | tmzt | what happened to dzo/ginge 2.6.25 in git? |
| 00:55.41 | dcordes_ | the diff? |
| 00:55.46 | dcordes_ | :/ |
| 00:55.52 | tmzt | no, the trace |
| 00:55.54 | dcordes_ | still undone |
| 00:56.24 | tmzt | getting things as close too google/android would help with sdcc, would'nt it? |
| 00:56.46 | dcordes_ | I use it to work with code easily available for reference. it is not so vital to the fso tryouts |
| 00:57.24 | tmzt | have you tried fso-unstable or shr.bearstech.com? |
| 01:05.07 | *** join/#htc-linux tmzt (n=ircuser@adsl-70-228-98-147.dsl.akrnoh.ameritech.net) [NETSPLIT VICTIM] |
| 01:05.07 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
| 01:05.08 | *** join/#htc-linux jeanseb (n=jeanseb@88.164.32.155) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-76-88-212-37.bak.res.rr.com) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux Raketemensch (n=Rakete@24-151-90-116.static.nwtn.ct.charter.com) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux kfm82 (n=kfm82@p54BEE34E.dip.t-dialin.net) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux Marex (n=vasum7am@auryn.karlin.mff.cuni.cz) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux LunohoD (n=alex@e180070069.adsl.alicedsl.de) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux lama (n=lama@estel.wpia.uw.edu.pl) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux Dinde (n=kayser@sur-internet.net) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux marajin (n=marajin@87-194-102-189.bethere.co.uk) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux SanMehat (n=san@nat/google/x-2347ebc4955b6019) |
| 01:05.08 | *** join/#htc-linux NiZoX (n=none@2a01:e35:8a13:a2b0:21c:c0ff:fe25:ff68) |
| 01:05.08 | *** join/#htc-linux nh_ (n=nh@aurora.msi.umn.edu) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux paulproteus (n=paulprot@2002:cbb2:8293:0:0:0:0:1) |
| 01:05.08 | *** join/#htc-linux Foxdie (n=foxdie@fox.akao.co.uk) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) [NETSPLIT VICTIM] |
| 01:05.08 | *** join/#htc-linux toi (n=pleemans@d5152D3B4.access.telenet.be) [NETSPLIT VICTIM] |
| 01:05.09 | *** join/#htc-linux dase (i=dase@p1atin.de) [NETSPLIT VICTIM] |
| 01:05.42 | dcordes_ | tmzt: I'm not sure if I heard of this |
| 01:06.01 | tmzt | ril |
| 01:06.15 | dcordes_ | that works with the kaiser |
| 01:06.16 | dcordes_ | in android |
| 01:06.19 | dcordes_ | you can make calls with it |
| 01:06.43 | tmzt | yes, but those would be the at commands and the order to call them in |
| 01:08.09 | dcordes_ | cr2 has the init sequences for kaiser |
| 01:08.41 | tmzt | that mux stuff won't work |
| 01:08.48 | dcordes_ | yea |
| 01:08.59 | dcordes_ | what about single line? |
| 01:09.02 | tmzt | init for data, I mean for voice, sms |
| 01:09.14 | tmzt | look at ril |
| 01:09.24 | dcordes_ | yes I want to focus only on making calls |
| 01:09.48 | dcordes_ | ATD working with the frameqworkd phone would be a first step |
| 01:09.49 | tmzt | 1 /dev/mux0 should be /dev/smd0 |
| 01:09.55 | dcordes_ | in single line? |
| 01:10.09 | tmzt | not sure what you mean |
| 01:10.25 | dcordes_ | /dev/mux0 where is that? |
| 01:11.17 | tmzt | on moko phone, msm doesn't use gsm mux |
| 01:11.36 | tmzt | freescale_neptune/modem.py |
| 01:13.50 | dcordes_ | but that's not used on moko phone |
| 01:14.00 | dcordes_ | that's the ezx modem code no |
| 01:15.37 | tmzt | gsm mux is a standard, used on moko, ezx, others |
| 01:15.54 | swetland | mtzt: we've worked on sdcc with the sdio stack in 2.6.25 and some fixes backported from 2.6.26 |
| 01:16.07 | swetland | things may not work under 2.6.24 due to sdio stack differences |
| 01:16.50 | tmzt | dcordes: are the dzo/ginge patches for 2.6.25, do they have 2.6.26 sdio stack? |
| 01:19.05 | tmzt | wait, those are in git.android android-msm-2.6.25 then? |
| 01:20.17 | dcordes_ | 2.6.24 vs 2.6.25 does not change our DMA problem |
| 01:21.28 | tmzt | swetland: the sdio 2.6.26 backports are in git.android android-msm-2.6.25 then? |
| 01:22.06 | tmzt | dcordes: getting everything as close to android upstream would make it easier to debug though? |
| 01:23.16 | dcordes_ | tmzt: ginge did that. the gitdiffs posted earlier are against this branch |
| 01:23.31 | dcordes_ | android-msm-2.6.25 |
| 01:23.36 | tmzt | but you're not using it? |
| 01:23.54 | dcordes_ | and it turned out SanMehat's latest sd patches do not affect kaiser DMA problem |
| 01:24.10 | dcordes_ | no as I said, since it doesn't change quality of use, it's not vital to fso |
| 01:24.47 | *** join/#htc-linux kedar (n=kstate@r9cc239.net.upc.cz) |
| 01:25.19 | kedar | hi all :) any news with Diamond or TouchPro ? :) |
| 01:25.39 | tmzt | dcordes: sdcc and sdio haven't changed in you kernel? what do you mean dma is not effected? |
| 01:25.47 | dcordes_ | kedar: not that I have heard of. do you frequent the relevant threads in xda? |
| 01:26.34 | dcordes_ | tmzt: I mean it doesn't matter what kernel I use to try fso |
| 01:28.08 | dcordes_ | and in reply to what swetland said: the gitdiff is against android-msm-2.6.25 (the branch which obviously has the backported 2.6.26 mmc code and contains SanMehat's latest msm_sdcc code) |
| 01:28.27 | dcordes_ | it's htc-msm rebased cleanly on top of that branch |
| 01:28.51 | dcordes_ | and with the tree resulting from that gitdiff, the kaiser SD issues persist |
| 01:32.05 | tmzt | ok, if that is what google is doing and they know how to fix sdcc on their kernel on A hw, does it make sense to use the same kernel on msm7200 and see what is wrong with it at the dma level? |
| 01:32.52 | tmzt | so we can add whatever printk's or tracing or whatever to find out why the dma is causing these problems |
| 01:33.46 | kedar | dcordes_: thx. i monitor "[PRJ][OS]Linux and Android on HTC Diamond" thread |
| 01:34.09 | dcordes_ | we are as close to google as we can with this tree http://www.headfuzz.co.uk/files/android/git-diff-110808-b.diff |
| 01:34.51 | tmzt | have you been able to build that kernel and run it on kaiser? |
| 01:34.53 | dcordes_ | it is ginge's code, he altered the driver for use with kaiser and he uses the .25 as working tree |
| 01:34.57 | dcordes_ | yes |
| 01:35.25 | dcordes_ | I was poking around with merging the 2.6.25 tree with htc-msm |
| 01:35.42 | dcordes_ | not finished it |
| 01:36.04 | tmzt | ok, can you build a kernel from git.android android-msm-2.6.25 with the latest ginge patch? |
| 01:36.10 | dcordes_ | and I think we should just put a new branch, putting the diff as one monolithic plop |
| 01:36.27 | dcordes_ | what for I won't be able to do anything with it |
| 01:36.43 | dcordes_ | I have a build of that tree |
| 01:39.31 | dcordes_ | tmzt: it would make sense to build that tree now if the diff in the link would be ginge latest work |
| 01:39.34 | dcordes_ | but it isn't |
| 01:39.48 | tmzt | ok |
| 01:41.16 | swetland | tmzt: everything we use is in android-2.6.5 and msm-2.6.25 |
| 01:41.27 | swetland | I need to merge down to android-msm-2.6.25 I think it's a little behind |
| 01:41.51 | swetland | I have a bunch of audio/dsp stuff to push this weekend and will probably do the merge down after that |
| 01:42.06 | dcordes_ | android* doesn't have teh commits which were added 6 days ago |
| 01:42.10 | dcordes_ | the |
| 01:43.08 | tmzt | what would be the best way to debug the sdcc dma issues? |
| 01:45.53 | swetland | probably have to ask San that sometime |
| 01:46.01 | swetland | I don't know much about the sdcc other than it's a pain in the butt |
| 01:47.43 | tmzt | ok, thank you |
| 01:49.11 | dcordes_ | San also suggested to use the .25 branch because it has the latest sd code |
| 01:49.28 | swetland | yeah, you're definitely best off working with the latest stuff we have on top of .25 |
| 01:49.50 | dcordes_ | we do |
| 01:50.00 | swetland | we can confirm that it does work on actual 7201A hardware. |
| 01:50.03 | tmzt | let's forget about sdcc for a moment, dcordes, what do we need to find out what's wrong in the sdio part? |
| 01:50.21 | tmzt | sdio stack |
| 01:50.36 | dcordes_ | I have no clue how that actually works. |
| 01:50.47 | dcordes_ | I'm a bit confused about mmc sdcc etc |
| 01:50.56 | dcordes_ | I know tehre are two host controllers |
| 01:50.58 | dcordes_ | on kaiser |
| 01:51.03 | tmzt | or just get better logs on what kind of errors you are getting |
| 01:51.38 | tmzt | what is a dma error, what are the symptoms, can we boot from initramfs and test the sd with something |
| 01:52.01 | dcordes_ | yes I'm using the rootfs on sd all the time |
| 01:52.04 | tmzt | what does a dma error/message look like in dmesg? |
| 01:52.18 | dcordes_ | DATAEND error |
| 01:52.34 | tmzt | if you grep DATAEND what do you get? |
| 01:52.34 | dcordes_ | ali1234 described it quite well I think |
| 01:52.48 | tmzt | grep -r |
| 01:53.47 | dcordes_ | 23:16 < ali1234> what happens is that mmc card uses DMA and when the access is finished it is supposed to signal that back to the CPU via an interrupt |
| 01:53.50 | dcordes_ | 23:16 < ali1234> but sometimes it just never does |
| 01:53.53 | dcordes_ | 23:16 < ali1234> and nobody has a clue why |
| 01:54.14 | tmzt | sdcc is a periphrial on which core? |
| 01:54.25 | tmzt | arm9 or arm11 |
| 01:54.36 | dcordes_ | swetland: ? |
| 01:54.40 | dcordes_ | arm11 I'd say |
| 01:55.14 | dcordes_ | else there'd be no real driver but only some channel thing in the kernel |
| 01:55.35 | tmzt | in your logs from earlier, the 4bit mode is disabled and the hz value is in there |
| 01:56.15 | dcordes_ | it's the 2.6.24 |
| 01:56.43 | dcordes_ | isn't 4 bit mode the thing enables SDHC? |
| 01:58.30 | tmzt | yes, sdhc was disabled, sdhc is the addressing though more than the parallel bus |
| 01:59.22 | tmzt | irq 26,27 dma 8 |
| 02:00.15 | swetland | my suggestion would be get the filesystem out of the loop, boot a kernel with ramdisk and do some stress tests on block read/write |
| 02:01.01 | tmzt | dcordes: can you convert console to cpio.gz? |
| 02:01.52 | dcordes_ | yes. I wish I had ginge's latest code |
| 02:02.55 | tmzt | you have a 25 zImage now? |
| 02:03.06 | dcordes_ | I have the tree from the gitdiff above. |
| 02:03.09 | dcordes_ | locally |
| 02:03.25 | dcordes_ | and some older 25 kernel image |
| 02:05.34 | dcordes_ | is building git-diff-110808-b.diff zImage |
| 02:11.18 | tmzt | do you have a scratch sd card/partition? |
| 02:12.04 | dcordes_ | empty one? |
| 02:12.18 | tmzt | would be best, but a blank partition will work |
| 02:12.29 | dcordes_ | oops |
| 02:12.43 | dcordes_ | I think the diff lacks msm_fb patches |
| 02:13.02 | tmzt | for kaiser specifically? |
| 02:13.31 | dcordes_ | right |
| 02:13.33 | tmzt | pull in msm_fb with the mods from .24 and fixup makefile |
| 02:14.00 | swetland | do you guys have a git repo with your changes for kaiser, vogue, etc stacked on top of our stuff? |
| 02:14.37 | tmzt | dcordes: are those in ltg yet? |
| 02:14.38 | dcordes_ | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm |
| 02:14.48 | tmzt | what version is that? |
| 02:15.35 | dcordes_ | swetland: this is a very old clone of android-msm-2.6.24 with most of the kaiser and polaris stuff (and non maintained old vogue stuff) on top of it |
| 02:16.04 | tmzt | did kevin get you a htc-msm-2.6.25? |
| 02:16.06 | dcordes_ | swetland: unfortunately we have the 2.6.25 based code not in git |
| 02:16.46 | dcordes_ | tmzt: no but I talked to pH5, he told me to merge the 2.6.24 with 25 to not lose the log |
| 02:16.50 | dcordes_ | but I didn't manage that |
| 02:16.56 | dcordes_ | it's complicated |
| 02:17.40 | tmzt | I have know idea about that, but the split is upstream (android) so how would we do that? |
| 02:18.00 | dcordes_ | no clue |
| 02:18.19 | dcordes_ | I'm happy I managed to maintain' |
| 02:18.24 | tmzt | maybe ph5/kevin2 we should get per user git |
| 02:18.29 | dcordes_ | I'm happy I managed to 'maintain' the 2.6.24 to this point |
| 02:18.30 | tmzt | like kernel.org |
| 02:19.16 | dcordes_ | that would not make much sense ginge doesn't like to get an own account |
| 02:20.22 | tmzt | can you put ginge patch on ~lgo ? |
| 02:20.36 | dcordes_ | to finally get the latest code into git I could simply put an android-msm-2.6.25 clone and apply the ginge diff as one big blob |
| 02:21.09 | tmzt | yes, but I think you want each -b branch or tag either before or after |
| 02:21.25 | tmzt | I tried to do this, just found it again |
| 02:22.33 | dcordes_ | http://linuxtogo.org/~lgorris/git-diff-110808-b.diff |
| 02:23.04 | dcordes_ | it lacks the fb code |
| 02:23.32 | dcordes_ | that and it's not latest stuff |
| 02:24.03 | dcordes_ | there have been many changes to fb code I fear |
| 02:24.20 | dcordes_ | between current git .24 and ginge .25 |
| 02:24.26 | tmzt | we don't have serial access though |
| 02:24.34 | dcordes_ | serial? |
| 02:24.39 | tmzt | console |
| 02:24.42 | dcordes_ | there's always gps |
| 02:24.45 | dcordes_ | gprs |
| 02:25.25 | tmzt | where do you get the msm_fb code with the X patches? |
| 02:25.25 | dcordes_ | I hope ginge will show soon so I can bug him for more recent code and to add fb code |
| 02:25.52 | dcordes_ | you're right there are different .25 diffs |
| 02:25.54 | tmzt | ~seen ginge |
| 02:26.05 | apt | ginge <n=ginge@host81-149-155-58.in-addr.btopenworld.com> was last seen on IRC in channel #htc-linux, 1d 12h 53m 10s ago, saying: 'Your english is better than mine, at least less lazy. I basically said:- yes, I should look at that but I didn't decompile the gps dll yet'. |
| 02:26.42 | tmzt | if I see him I will ask |
| 02:26.47 | dcordes_ | ok |
| 02:27.01 | dcordes_ | there's http://linuxtogo.org/~lgorris/kaiser-2.6.25.diff |
| 02:27.24 | tmzt | which is? |
| 02:27.27 | dcordes_ | 04-Aug-2008 |
| 02:27.35 | dcordes_ | I could use its fb |
| 02:27.49 | tmzt | and make one git diff? |
| 02:28.32 | dcordes_ | don't know |
| 02:28.40 | dcordes_ | let's wait for ginge |
| 02:52.54 | *** join/#htc-linux surgex (i=surge@pool-72-88-90-206.bflony.fios.verizon.net) |
| 02:53.11 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 03:14.04 | dcordes | good night |
| 03:48.27 | *** join/#htc-linux ellisway (n=ellis@80-46-67-47.static.dsl.as9105.com) |
| 05:20.33 | *** join/#htc-linux goxboxlive (n=goxboxli@139.84-48-212.nextgentel.com) |
| 06:44.32 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 06:59.38 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfd795.pool.einsundeins.de) |
| 07:18.15 | *** join/#htc-linux LunohoD_ (n=alex@e180071068.adsl.alicedsl.de) |
| 07:32.13 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d8665f2.pool.einsundeins.de) |
| 08:11.49 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
| 08:24.32 | *** join/#htc-linux keda1 (n=kstate@r9cc239.net.upc.cz) |
| 08:32.27 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 09:42.01 | *** join/#htc-linux Marex (n=vasum7am@auryn.karlin.mff.cuni.cz) |
| 09:51.17 | *** join/#htc-linux goxboxlive_ (n=goxboxli@139.84-48-212.nextgentel.com) |
| 10:18.43 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
| 11:10.38 | *** join/#htc-linux goxboxlive_ (n=goxboxli@139.84-48-212.nextgentel.com) |
| 11:31.12 | *** join/#htc-linux ginge (n=baz@78-105-175-81.zone3.bethere.co.uk) |
| 11:31.25 | ginge | morning |
| 11:55.21 | *** join/#htc-linux kfm82ibook (n=kfm82@p54BEDA6A.dip.t-dialin.net) |
| 11:56.54 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 12:34.10 | *** join/#htc-linux TeringTu1y (n=maarten@195-241-125-243.ip.telfort.nl) |
| 12:42.22 | *** join/#htc-linux pH5 (n=ph5@p5485EEE9.dip.t-dialin.net) |
| 13:06.28 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 13:14.40 | dcordes | ginge: ping |
| 13:16.11 | ginge | dcordes: pong |
| 13:18.04 | dcordes | ginge: I'd like to make a new branch anrdoird-msm-2.6.25 as planned and just push your stuff as one big diff, what do you think? |
| 13:18.35 | ginge | dcordes: well It is up to you I guess. I think it needs to go in somehow, and a new branch makes sense. |
| 13:20.24 | dcordes | yea that's the point. doesn't matter how elegant it's put, history or not |
| 13:20.34 | dcordes | people can look up the history to that point in the 24 branch |
| 13:21.12 | swetland | we're going to be recompressing history on the main branch when we push out to the lkml, etc anyway |
| 13:21.49 | dcordes | yea ok |
| 13:21.52 | swetland | getting stuff layered on top assembled a set of patches, per-subsystem would probably make it easier to maintain over time, I expect |
| 13:22.18 | dcordes | so in the long run it won't matter anyway |
| 13:22.23 | ginge | swetland: agreed. I did start to do something like that so we can at least have some commit explanation of what is happening |
| 13:22.26 | dcordes | if we drop history now |
| 13:22.52 | swetland | basically my goal is to get into the mainline and our history will be a casualty of that process, I think |
| 13:22.52 | ginge | dcordes: well if we are smart we can at least give people a rough idea of what eac patch set is for |
| 13:23.16 | dcordes | "merge of htc-msm-2.6.24 into android-msm-2.6.25" ? |
| 13:23.21 | swetland | as I don't believe the mainline folks want all the noise to-date plus whatever noise is generated by tidying up their patches |
| 13:23.27 | swetland | er their patch feedback |
| 13:23.35 | swetland | er tidying up our patches based on their feedback! |
| 13:23.39 | swetland | I need to go to sleep. |
| 13:23.53 | ginge | :) |
| 13:24.47 | ginge | dcordes: no more like |
| 13:24.47 | ginge | smd.diff - msg something like: {summary of .24 against mainline} + {.25 changes} |
| 13:24.47 | ginge | fb.diff message as above |
| 13:24.47 | ginge | etc.diff etc etc |
| 13:25.19 | ginge | so roll up the .24 branch history with a link to that branch and also changes against android mainline |
| 13:25.20 | swetland | also, you may want to consider doing a parallel smd implementation |
| 13:25.37 | swetland | so that one can choose to build for 6.x vs whatever is in kaiser, etc |
| 13:26.05 | dcordes | ginge: do you have a tree that works in a way we can base that procedure on? |
| 13:26.08 | ginge | swetland: I did consider making a header that defines the fifo channel layout, that is mostly all that changes in our AMSS |
| 13:26.36 | swetland | ginge: I'm not sure how much of the power collapse stuff, etc is compatible either |
| 13:26.42 | ginge | dcordes: erm... I was just going to dice up my git diff based on feature |
| 13:26.54 | ginge | swetland: good point, pretty much none :) |
| 13:26.57 | swetland | and we've departed a bit further now that we're using the smd item with the name->cid mapping and stuff (which was definitely newly added in 6.x) |
| 13:27.02 | ginge | #if 0 ;) |
| 13:27.08 | swetland | I'm starting to look at MSM8K support |
| 13:27.16 | ginge | good grief :O |
| 13:27.22 | swetland | and we're liking going to have to do something similar for clock/power/pm for that as well |
| 13:27.32 | ginge | maybe they fixed some of the more stupid bugs by 8k |
| 13:27.34 | swetland | though a lot of the peripherals are compatible |
| 13:27.47 | swetland | here's hoping! I haven't got devboards or looked over all the datasheets yet |
| 13:28.07 | ginge | dreams about getting datasheets |
| 13:28.16 | swetland | but I have talked with some of the hw team and provided some feedback on our least favorite parts of 7k. With luck they'll fix some of 'em. |
| 13:28.20 | ginge | dcordes: has anyone even asked nicely for the datasheets |
| 13:28.35 | ginge | dcordes: or even qualcomm's help at all? |
| 13:28.55 | swetland | I think it took well over six months to negotiate the contract that ended up with us getting databooks and being able to create GPL'd drivers. |
| 13:28.58 | ginge | swetland: I bet that was a fun conversation? |
| 13:29.11 | ginge | jebus. insanity |
| 13:29.14 | swetland | while it can't hurt to ask, I wouldn't get your hopes up about them just chucking pdfs over the wall at you ^^ |
| 13:29.28 | ginge | swetland: stranger things have happened at sea |
| 13:29.32 | swetland | it is true |
| 13:29.46 | swetland | 4 years ago when we started all this, we were working on omap730/850 |
| 13:30.01 | swetland | and TI was making noises about trying to get legal to scrub their databooks for release |
| 13:30.04 | ginge | I got some datasheets from TI for a chip they dont officially make. All I did was ask the dev team |
| 13:30.24 | swetland | I see that you can actually download OMAP34xx and 35xx TRMs with no NDA, clickthrough license, etc |
| 13:30.46 | ginge | these days most sensible companies realise that free specs is an asset |
| 13:30.58 | ginge | idoits like me will only reverse engineer it anyway |
| 13:30.59 | swetland | if your primary goal is to sell silicon |
| 13:31.10 | swetland | having more software that can run on it seems like a win |
| 13:31.31 | ginge | true |
| 13:32.24 | ginge | shakes fist at sd drive |
| 13:32.27 | ginge | r |
| 13:34.13 | swetland | is taking a break from 7k to do some omap3 hacking this weekend |
| 13:34.39 | ginge | heh. I should get my beagle soon |
| 13:34.48 | swetland | friend of mine is getting a tiny kernel he's been hacking on booting on the beagleboard, I'm hoping to do some bootloader hacking |
| 13:35.20 | swetland | http://git.android.com/?p=lk.git |
| 13:35.44 | ginge | nice |
| 13:36.08 | ginge | okay, now I have an initrd that boots angstrom stresses out the sd and posts the dmesg back to my server... I hope |
| 13:36.18 | swetland | I haven't hacked on lk in forever. it's a nice little system. last time I touched it was on atmel sam7 parts several years ago |
| 13:36.39 | swetland | no exposed uart on kaiser? |
| 13:36.57 | ginge | not without taking it apart, and I am expecting calls today ;) |
| 13:37.49 | swetland | adventurous is hacking on your primary phone |
| 13:38.00 | ginge | basically this kaiser is a bit crap. I might design my own damn PDA phone that fits the needs of the linux hungry geek |
| 13:38.13 | ginge | bloody stupid is hacking your primary phone :) |
| 13:40.01 | ginge | at least these days they are not as easy to hose |
| 13:43.14 | *** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl) |
| 13:46.40 | *** join/#htc-linux BabelO_N800 (n=BabelO@AToulouse-151-1-92-222.w86-217.abo.wanadoo.fr) |
| 13:46.45 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d8665f2.pool.einsundeins.de) |
| 13:47.58 | kiozen | BabelO_N800: hi, I am working for you the whole mornig now |
| 13:51.19 | *** join/#htc-linux TeringTu2y (n=maarten@195-241-125-243.ip.telfort.nl) |
| 13:56.00 | *** join/#htc-linux amarus (n=chatzill@77.44.158.192) |
| 13:56.53 | amarus | NickServ Amarus |
| 14:06.40 | *** join/#htc-linux exco (n=exco@e181071195.adsl.alicedsl.de) |
| 14:07.33 | *** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl) |
| 14:15.38 | *** join/#htc-linux TeringTu1y (n=maarten@195-241-125-243.ip.telfort.nl) |
| 14:20.11 | *** join/#htc-linux SmallR2002 (n=SmallR20@79-69-87-203.dynamic.dsl.as9105.com) |
| 14:28.47 | *** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl) |
| 14:29.18 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfd795.pool.einsundeins.de) |
| 14:33.01 | *** join/#htc-linux tsdogs (n=tsdogs@62.123.180.130) |
| 14:35.06 | *** join/#htc-linux sni1 (n=igor@92.124.31.194) |
| 14:36.52 | *** join/#htc-linux TeringTu2y (n=maarten@195-241-125-243.ip.telfort.nl) |
| 14:45.49 | *** part/#htc-linux sni1 (n=igor@92.124.31.194) |
| 17:04.03 | *** join/#htc-linux patoche (n=root@lns-bzn-61-82-250-111-229.adsl.proxad.net) |
| 17:19.52 | *** join/#htc-linux Alex[sp3dev] (n=alex_dfr@86.110.163.25) |
| 17:55.36 | *** join/#htc-linux patoche (n=pat@lns-bzn-61-82-250-111-229.adsl.proxad.net) |
| 17:56.51 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 17:57.12 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 18:39.04 | *** join/#htc-linux jmhalder (n=jmhalder@c-76-16-113-82.hsd1.il.comcast.net) |
| 18:43.56 | *** join/#htc-linux Red_Lion (n=lion@79.164.130.87) |
| 19:33.48 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 19:52.39 | *** join/#htc-linux patoche (n=Patrice@lns-bzn-61-82-250-111-229.adsl.proxad.net) |
| 20:10.40 | marajin | allo |
| 20:28.04 | ginge | ayeup |
| 20:32.47 | *** join/#htc-linux patoche (n=pat@lns-bzn-61-82-250-111-229.adsl.proxad.net) |
| 20:38.44 | *** join/#htc-linux ali1234 (n=al@62.24.214.38) |
| 21:01.32 | *** join/#htc-linux kedar (n=kstate@r9cc239.net.upc.cz) |
| 21:03.29 | *** join/#htc-linux ellisway (n=ellis@80-46-67-47.static.dsl.as9105.com) |
| 21:16.10 | *** join/#htc-linux patoche (n=Patrice@lns-bzn-61-82-250-111-229.adsl.proxad.net) |
| 21:39.03 | *** join/#htc-linux kedar (n=kstate@r9cc239.net.upc.cz) |
| 22:35.57 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
| 23:56.47 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |