00:10.40 | BruteFrce | can i map it with setkeycode ? |
00:10.47 | BruteFrce | tmzt? |
00:10.56 | BruteFrce | tmzt_ even |
00:33.24 | *** join/#htc-linux Arilou (n=DeluxeIR@79.101.86.51) |
00:35.32 | Arilou | Qt Extended ported successfully on Magician ;) |
00:49.26 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
00:52.40 | *** join/#htc-linux surgex (i=surge@pool-98-118-165-224.bflony.fios.verizon.net) |
01:05.39 | Kevin2 | NetRipper: Does the flashlight sequence (using virtual addresses) work if called before mmu_trampoline() but after Mach->hardwareShutdown()? |
01:19.45 | *** join/#htc-linux heise2k (n=rheise@65-78-40-52.c3-0.upd-ubr6.trpr-upd.pa.cable.rcn.com) |
01:22.37 | *** join/#htc-linux apt (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
01:22.37 | *** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup. |
01:39.09 | *** join/#htc-linux ALoGeNo (n=pi@243.Red-217-125-20.staticIP.rima-tde.net) |
01:40.17 | ALoGeNo | sup |
02:02.59 | *** join/#htc-linux BruteFrce (n=IrcNet@m7f0e36d0.tmodns.net) |
02:25.06 | *** join/#htc-linux ALoGeNo (n=pi@243.Red-217-125-20.staticIP.rima-tde.net) |
02:36.13 | *** join/#htc-linux dcordes_ (n=dcordes_@unaffiliated/dcordes) |
02:44.42 | ALoGeNo | hi dcordes_ |
03:02.38 | *** join/#htc-linux exco1 (n=exco@e181082098.adsl.alicedsl.de) |
03:18.55 | *** join/#htc-linux oohnoitz (i=prinny@adsl-065-005-208-086.sip.msy.bellsouth.net) |
04:03.07 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-52-97.hsd1.nj.comcast.net) |
04:40.03 | *** join/#htc-linux oohnoitz (i=prinny@adsl-065-005-208-086.sip.msy.bellsouth.net) |
05:01.24 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
05:11.25 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
05:12.44 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
05:40.19 | *** join/#htc-linux p3t3r__ (n=peter@134.245.164.105) |
05:54.54 | *** join/#htc-linux kiozen (n=oeichler@p54929FD5.dip0.t-ipconnect.de) |
05:55.59 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
06:16.47 | *** join/#htc-linux Spike1506 (n=Joshua@cable-62-238-192-3.zeelandnet.nl) |
06:19.48 | *** join/#htc-linux goxboxlive (n=goxboxli@139.84-48-212.nextgentel.com) |
06:20.57 | *** join/#htc-linux kiozen (n=oeichler@p54929FD5.dip0.t-ipconnect.de) |
06:26.54 | *** join/#htc-linux kiozen (n=oeichler@p54929FD5.dip0.t-ipconnect.de) |
06:47.27 | NetRipper | Kevin2, using the virtual memory addresses (instead of the physicals), yes it does work after hardwareshutdown |
06:51.08 | NetRipper | Kevin2, hardwareShutdown() does nothing though for the MSM arch, it doesn't override the hardwareShutdown() method so the default one from Machine class is used |
06:51.13 | NetRipper | Kevin2, which is empty |
07:06.40 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) |
07:23.50 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
07:33.54 | *** join/#htc-linux nebi (n=nebi@c-498fe253.02-145-7570701.cust.bredbandsbolaget.se) |
07:55.25 | *** join/#htc-linux ginge___ (n=ginge@host81-149-155-58.in-addr.btopenworld.com) |
07:56.37 | *** join/#htc-linux yvo (n=musman@195.154.155.26) |
07:57.07 | yvo | hi |
07:58.33 | ginge___ | morning |
07:59.38 | *** join/#htc-linux jeanseb (n=jeanseb@88.164.32.155) |
08:02.52 | *** join/#htc-linux kaze (n=kaze@ABordeaux-152-1-56-91.w82-125.abo.wanadoo.fr) |
08:13.57 | *** join/#htc-linux Babel1 (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
08:14.52 | BabelO_ | morning |
08:15.11 | kiozen | morning |
08:16.07 | BabelO_ | kiozen: you see my email ? is it clear ? |
08:17.44 | kiozen | BabelO_: his answer looks like he understood what you want :) |
08:18.00 | kiozen | let's what is happening :) |
08:19.08 | kaze | is gone.. autoaway after 15 min ..[cyp(l/on.p/on)] |
08:19.54 | BabelO_ | kiozen: check the small screenshot of this http://www.memory-map.fr/produit.php |
08:22.00 | kiozen | BabelO_: I know. looks sleek, but after a certain play time you get bored of too much 3D and return to 2D for planning |
08:22.29 | kiozen | the contour shading is really usefull |
08:22.47 | BabelO_ | kiozen: yes agree, but new user love this kind of feature |
08:23.21 | BabelO_ | kiozen: yes when i plan a walk i always keep shading contour on to see if mountain are not too high |
08:23.33 | kiozen | BabelO_: I know, it's the first they ask for, the last they really need/use |
08:24.04 | kiozen | BabelO_: that's what kept me from spending time on it so far |
08:27.52 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-52-97.hsd1.nj.comcast.net) |
08:29.30 | BabelO_ | kiozen: how much thread do you want to start for symbols search ? |
08:29.36 | BabelO_ | one per cpu ? |
08:30.35 | kiozen | BabelO_: no just 1 to keep the GUI operational. AFAIK you can't spread threads over CPUs yet, Only process |
08:30.59 | BabelO_ | yes right |
08:35.01 | *** join/#htc-linux Spike1506 (n=Joshua@cable-62-238-192-3.zeelandnet.nl) |
08:40.28 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
08:47.29 | kaze | hello, any news about android on htc kaiser? |
08:52.34 | kaze | got 0.8 running pretty good but any 1.0 build released? |
09:07.33 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
09:15.24 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) [NETSPLIT VICTIM] |
09:15.24 | *** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk) [NETSPLIT VICTIM] |
09:15.24 | *** join/#htc-linux swetland (n=swetland@nat/google/x-6eae5cb1f4c43e79) |
09:15.25 | *** join/#htc-linux zule (i=foglem@shadowmite.com) [NETSPLIT VICTIM] |
09:15.25 | *** join/#htc-linux SanMehat (n=san@nat/google/x-5a5f3c82ee99ec20) |
09:15.25 | *** join/#htc-linux rwhitby (n=rwhitby@nslu2-linux/rwhitby) |
09:15.25 | *** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1) |
09:15.25 | *** join/#htc-linux hao (i=heanol@karantan.org) [NETSPLIT VICTIM] |
09:22.44 | BabelO_ | kiozen: your virtualbox was 1.5.2 ? |
09:23.44 | kiozen | yes |
09:32.12 | BabelO_ | kiozen: that is why, i found a reference that 1.5.2 as some problem with some usb device |
09:36.55 | kiozen | need to get vb running on my laptop.. had problems with starting my image from 1.5.2 on a more recent vbox |
09:52.29 | goxboxlive | BabelO_: damn, i have received the MB now, but my power has another plug than the one required on the board. My power plug is to narrow :-( |
09:53.06 | BabelO_ | goxboxlive: yes that what i was meaning, sorry my power plug was too old too |
09:53.39 | goxboxlive | hmm is there an converter on the market? My power is 600W AFAIR so i guess it's powerfull enough. |
09:53.46 | BabelO_ | kiozen: you can update to 1.5.4 only |
09:54.28 | BabelO_ | goxboxlive: good question i don't know, i bought a sonata III box with power supply and fan included, because by olddesktop was too small |
09:54.39 | goxboxlive | ok |
09:54.50 | kiozen | BabelO_: images can't be ported to newer versions? |
09:55.17 | kiozen | BabelO_: wait I have 1.5.6 |
09:55.46 | kiozen | BabelO_: should have looked into the about dialog not just my brain |
10:05.07 | BabelO_ | kiozen: i restart all my images in newer version each time |
10:05.19 | BabelO_ | kiozen: just need to recreate a new profile |
10:06.05 | Marajin_ | goxboxlive: you mean the ATX power connector? |
10:06.07 | kiozen | BabelO_: the boot process stops with a bluescreen, no clue why |
10:06.23 | BabelO_ | kiozen: aïe you use windows, lol |
10:06.24 | Marajin_ | goxboxlive: You have a 20 pin powersupply and a 24 pin board right? |
10:07.18 | kiozen | BabelO_: I am _forced_ to use it :) |
10:07.29 | Marajin_ | BabelO_: Is that the problem? the board has more holes to connect to than the powers supply gives? (4 more to be precise) ? |
10:07.51 | BabelO_ | kiozen: that is because you have activated acpi or some parameters different from the orifgianl set |
10:08.08 | BabelO_ | kiozen: same happen to me when i migrate from 1.6 to 2.0 |
10:08.33 | kiozen | BabelO_: not that I would know, but who knows ... |
10:08.47 | BabelO_ | Marajin_: yes that is don't know why newer have more pin :( |
10:09.29 | Marajin_ | BabelO_: I do, it's the ATX 2.0 standard versus the old ATX standard. The fact is you can just ignore the extra pins, the 20 pin connector will still connect if you look carefully at the shapes and match it up |
10:09.38 | Marajin_ | and the board will still work fine |
10:10.46 | Marajin_ | on some boards you will also see the 12 volt connector (normally a square of 4 pins) is now 8 pins also. Again you can just ignore the 4 extra pins if your powersupply lacks them |
10:12.42 | Marajin_ | goxboxlive: did you see that? you don't need a convertor, if you check carefully your powersupply will actually still connect and the board will work |
10:13.07 | dcordes | ginge___: hey I havet he HTCflasher info 8 output |
10:13.52 | ginge___ | nice |
10:14.46 | Marajin_ | ginge___: collecting underscores are you? :p |
10:15.32 | dcordes | ginge___: I don't know if it's that useful |
10:16.34 | dcordes | http://wiki.xda-developers.com/index.php?pagename=KaiserNAND |
10:16.48 | dcordes | Partition[0], type=0x20, start=0x2, total=0x63E |
10:16.48 | dcordes | Partition[1], type=0x23, start=0x640, total=0x700 |
10:16.48 | dcordes | Partition[2], type=0x25, start=0xD40, total=0x9140 |
10:16.48 | dcordes | Partition[3], type=0x4, start=0x9E80, total=0x11440+ |
10:16.50 | dcordes | basically |
10:17.06 | Marajin_ | cool |
10:17.23 | ginge___ | oh, ok. I dont think I was too far off then |
10:17.28 | dcordes | ginge___: well looks somewhat different than the pdocreat output |
10:17.34 | ginge___ | did you remove the 0x2400000 from them? |
10:17.53 | ginge___ | thats because these are block sizes |
10:17.55 | dcordes | no that is the bare output from the HTCflasher output. I did not change it. see link above for full output |
10:18.05 | ginge___ | multiply by 0x800 and it will be in bytes |
10:18.26 | ginge___ | got a link to the source I pastebinnned? |
10:18.45 | dcordes | I paste my local file |
10:19.37 | dcordes | http://rafb.net/p/0xC8JO51.html |
10:19.54 | dcordes | should be the same. I don't know why the paste looks strange. |
10:21.35 | ginge___ | okay, that looks good. You could try just removing the 0x24 offset I put in |
10:21.54 | dcordes | ginge___: must we get multiple /dev/mtd? for the different partitions? |
10:21.58 | dcordes | ok I will try that |
10:22.30 | ginge___ | dcordes: we should, but only once the system can determine proper partition data. |
10:23.09 | ginge___ | I think that large offset should only be applied to the one partiotn, but we can worry about that later |
10:23.58 | ginge___ | Marajin_: good point. I wonder where I am still logged in :) |
10:25.01 | dcordes | ginge_: I don't understand the relation between the partitioning data in the msm_nand_partitions function and the HTCflasher output. |
10:25.47 | ginge_ | HTC flasher outputs the partition sizes and partition start in blocks |
10:25.57 | ginge_ | we know that each block is 0x800 |
10:26.38 | ginge_ | so partition 1 is 0x63E blocks or 0x31f000 bytes |
10:26.52 | dcordes | ah thank you |
10:26.54 | ginge_ | (0x63e x 0x800 = 0x31f000) |
10:27.28 | dcordes | why do you think I get the block size errors when I try to access the mtd0 device? |
10:27.32 | ginge_ | the first parition is offset by 0x02 blocks or 0x100 bytes, and the rest of the partitions sit back to back from end other. |
10:27.39 | dcordes | (in a way other than hexdump /dev/mtd0) |
10:27.54 | ginge_ | dcordes: probably because of that offset value which was wrong |
10:28.35 | dcordes | so it is definetly partition related? |
10:28.47 | dcordes | I want to asure we are not searching on the wrong end |
10:29.48 | ginge_ | not sure at the moment. I am doing quite a bit of guessing on this one |
10:35.55 | dcordes | ok so what's interesting now is how the driver likes the partition table without 0x24* offsets? |
10:36.12 | dcordes | is there anything else I can try? |
10:39.16 | ginge_ | did that not work? |
10:50.51 | dcordes | ginge_: will be able to tell you in a minute |
10:53.38 | dcordes | ginge_: is there anything except of entry-macro that could cause smd1 to not work? |
10:54.00 | ginge_ | dcordes: lots and lots of things |
10:54.01 | dcordes | I experience that problem with the code from local 2.6.25 builds |
10:54.39 | ginge_ | check to make sure that there isnt a switch or if block that discards that channel on smd code |
10:55.32 | dcordes | I didn't touch that. probably it would be the best to get your latest diff, restore the git entry-macro and then diff the two trees. |
10:55.44 | dcordes | so I can sort what I broke locally |
10:55.49 | dcordes | booting |
10:56.33 | dcordes | ginge_: it hangs in haret |
10:57.56 | ginge_ | can you pastebin the smd |
10:58.04 | ginge_ | hangs in haret?? how odd |
10:58.31 | dcordes | I'm almost certain it is not nand related |
10:58.57 | dcordes | hangs again |
10:59.02 | dcordes | I must have destroy the build again |
10:59.41 | dcordes | sorry but I fear I can't try further now. I have to go fix home adsl |
11:00.22 | dcordes | I'm taking kaiser with a working smd kernel. maybe I can try from on the go |
11:00.24 | dcordes | later |
11:02.58 | ginge_ | later |
11:07.47 | goxboxlive | Marajin_: i tested the 20pin connector and it fitted, and when i turn on the main switch the powerled on the Motherboard turn green. But when i hit the powerbutton nothing happens. I have even tried to shorten the two pins on the motherboard power switch, but nothing |
11:09.39 | *** join/#htc-linux EA21 (n=chipper@cpe-024-074-138-191.carolina.res.rr.com) |
11:17.54 | Marajin_ | goxboxlive: that's not your Powersupply though, the green light on the board proves that |
11:18.15 | Marajin_ | goxboxlive: are you positive it's the right pins? some motherboards are kinda vague about which pins are which |
11:21.55 | goxboxlive | Marajin_: yes i follow the drawing so it should be right |
11:22.27 | goxboxlive | I talked to the shop i bought it from and they told me to return it so they could test it |
11:22.33 | Marajin_ | goxboxlive: just short the pins in pairs till something works. You can't do any harm while the system is off |
11:23.51 | goxboxlive | marajin: Ok, i'll try once more shorten the reset and the power pins just to check. |
11:27.32 | *** join/#htc-linux the_sys0p` (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) |
11:31.22 | dcordes | ahh the joys off cellular networks |
11:32.00 | dcordes | ginge_: retried the kernel with the offsets removed 5 times |
11:32.13 | dcordes | old reference kernel works well |
11:32.45 | *** join/#htc-linux Arilou (n=DeluxeIR@79.101.86.51) |
11:32.56 | Arilou | Can someone help me |
11:32.59 | Arilou | I got this message |
11:33.13 | Arilou | "/dev/mtdblock0: can't read superblock" |
11:38.17 | marajin | goxboxlive: ok, good luck |
11:46.31 | goxboxlive | thanks :-) |
11:46.32 | dcordes | goxboxlive: I use the same mainboard p5kc. you can't power on? |
11:47.12 | goxboxlive | dcordes: no, the greenpower led on the mainboard is on, but it doesnt react when i hit the power button, |
11:53.13 | *** part/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
11:53.23 | dcordes | sounds like something with the board is broken to me |
11:54.10 | *** join/#htc-linux fo_Q (n=foq@85.124.97.111) |
11:55.07 | dcordes | goxboxlive: did you try with one mem module only? maybe power supply problem? |
12:21.01 | goxboxlive | dcordes: i had two mem in channel A. The power seems to work ok, it did with my old computer |
12:21.30 | goxboxlive | at least it should have bootet in to bios, because the green powerled on the board where lighting |
12:23.10 | marajin | goxboxlive: Dcordes has a point, faults with the memory or harddrive can actually result in it failing to power on |
12:23.48 | marajin | goxboxlive: unplug everything except the motherboard, CPU and try to start it, it should start and beep because no memory. |
12:23.50 | *** join/#htc-linux DasFx (n=John@5354790B.cable.casema.nl) |
12:24.00 | goxboxlive | marajin: ok, well now it's to late. I have allready deliverd it to the postoffice. I required a new card. |
12:24.09 | marajin | ah well |
12:24.21 | marajin | you have no local shop where you can walk in? |
12:24.35 | goxboxlive | marajin: i did, but i had the memory plugged in though, else everything where unplugged |
12:25.50 | marajin | well it's probably a buggered motherboard anyway :) |
12:40.55 | kaze | hi there, any new android for kaiser release? |
12:41.11 | marajin | kaze: nope |
12:41.15 | kaze | :\ |
12:41.31 | kaze | thanks for the answer anyway :) |
12:45.27 | marajin | well keep on hoping |
12:45.43 | marajin | but till we find a way out of our storage woes, things aren't likely to progress well |
13:21.29 | Arilou | someone help |
13:21.31 | Arilou | "/dev/mtdblock0: can't read superblock" |
13:21.52 | Arilou | how to fix this ? :( |
13:22.22 | ginge_ | Arilou: what device? |
13:25.37 | Arilou | no |
13:25.45 | Arilou | this is not in device' |
13:25.49 | Arilou | i want to mount |
13:25.54 | Arilou | a jffs2 image |
13:25.59 | Arilou | and i get this error |
13:26.38 | ginge_ | you say image, is it an ikage on a disk already? |
13:26.53 | ginge_ | i.e loopback |
13:29.52 | *** join/#htc-linux Raketemensch (n=Rakete@192.234.2.49) |
13:34.28 | *** join/#htc-linux oohnoitz (i=prinny@adsl-065-005-208-086.sip.msy.bellsouth.net) |
13:48.46 | kaze | "<marajin> but till we find a way out of our storage woes, things aren't likely to progress well" what do you mean by storage woes? |
13:51.22 | marajin | kaze: We can't use the SD card properly, it dma errors and locks up |
13:54.16 | *** join/#htc-linux webPragmatist (n=none@99-6-241-169.lightspeed.rcsntx.sbcglobal.net) |
13:56.37 | *** join/#htc-linux Raketemensch (n=Rakete@192.234.2.49) |
14:03.10 | *** part/#htc-linux exco1 (n=exco@e181082098.adsl.alicedsl.de) |
14:43.24 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
15:15.18 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
15:19.32 | *** part/#htc-linux p3t3r__ (n=peter@134.245.164.105) |
15:22.16 | *** join/#htc-linux fo_Q (n=foq@85.124.97.111) |
15:58.40 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
16:13.06 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d339.pool.einsundeins.de) |
16:18.43 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) |
16:26.23 | *** join/#htc-linux zdooder (n=troy@c-67-160-50-188.hsd1.wa.comcast.net) |
16:31.34 | *** join/#htc-linux unomi (n=Garden@ppp-124-121-210-103.revip2.asianet.co.th) |
16:41.01 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
16:45.29 | *** join/#htc-linux miknix (n=miknix@bl5-242-224.dsl.telepac.pt) |
16:57.16 | cr2_ | marajin: i have seen some patch on the android ML |
16:57.53 | cr2_ | marajin: http://groups.google.com/group/linux-msm-kernel/browse_thread/thread/34e7fd8164f84dca |
16:58.37 | cr2_ | don't know if it helps |
17:11.51 | *** join/#htc-linux ssapphiree (n=sapphire@ppp85-140-117-157.pppoe.mtu-net.ru) |
17:12.07 | dcordes | cr2_: evening. seen kaiser HTCflasher info 8 output? its the same scheme as raphael |
17:12.27 | cr2_ | dcordes: yes |
17:12.44 | cr2_ | dcordes: do you have this dma patch above applied ? |
17:12.49 | *** join/#htc-linux ssapphiree (n=sapphire@ppp85-140-117-157.pppoe.mtu-net.ru) |
17:22.55 | dcordes | cr2_: don't know.when was it commited? it might be the same code SanMehat provided ginge with already |
17:23.22 | dcordes | I'm trapped in 3x6 qvga console now |
17:25.10 | cr2_ | i don't know if it was committed. check the source |
17:25.27 | *** join/#htc-linux kaze (n=kaze@pac33-1-82-235-251-34.fbx.proxad.net) |
17:25.40 | cr2_ | i think SanMehat has completely rewritten the driver |
17:26.54 | ssapphiree | dcordes hi ) someone here told me that you're the one I should ask about Linux for HTC Touch ) do you know something about where it's being developed and when will become something bootable? ) |
17:28.04 | cr2_ | ssapphiree: what is htc touch ? |
17:28.20 | ssapphiree | it's htc p3450 |
17:28.21 | ssapphiree | elf |
17:28.31 | ssapphiree | just one of it's names ) |
17:28.47 | *** join/#htc-linux bertramt (n=chatzill@63.246.89.17) |
17:29.16 | *** join/#htc-linux LunohoD_ (n=alex@e180065232.adsl.alicedsl.de) |
17:29.44 | *** join/#htc-linux amd64lover (n=miknix@bl4-94-124.dsl.telepac.pt) |
17:29.45 | cr2_ | hmm. |
17:30.00 | cr2_ | which cpu does it have ? |
17:30.16 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
17:30.22 | ssapphiree | hm |
17:30.37 | cr2_ | have you run haret on it ? |
17:30.40 | ssapphiree | omap 850 I guess |
17:31.06 | cr2_ | ok, then it's a completely different beast |
17:31.18 | cr2_ | bbl |
17:31.28 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
17:31.33 | ssapphiree | I haven't tried any linux on it ) and also it has no keyboard, I guess it can become a trouble ) |
17:31.58 | ssapphiree | bbl? |
17:32.04 | ssapphiree | what's it )) |
17:38.01 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
18:04.56 | ginge | cr2_: that patch doesn't seem to be committed. I will try it as soon as my phone has charged. damn thing doesn't even last a day any more |
18:19.37 | *** join/#htc-linux exco (n=exco@e181082098.adsl.alicedsl.de) |
18:20.09 | goxboxlive | BabelO: what is the link to linux hardware compability list you gave me? |
18:20.16 | goxboxlive | I need to check out P5N |
18:20.29 | goxboxlive | found it |
18:20.41 | BabelO | goxboxlive: can you give it back, i forgot :) |
18:20.50 | goxboxlive | :-) |
18:20.58 | goxboxlive | http://www.debianlinuxhcl.org/browse |
18:24.57 | BabelO | goxboxlive: then that s not me :) |
18:26.36 | *** join/#htc-linux rmoravcik1 (n=rmoravci@ip-89-102-255-171.karneval.cz) |
18:27.16 | *** join/#htc-linux nebi (n=nebi@c-498fe253.02-145-7570701.cust.bredbandsbolaget.se) |
18:30.15 | goxboxlive | BabelO: the webshop told me that it would take over a week before they could take a look at my motherboard. I am considering canceling the p5K board becuase of the delay. SO i am considering buying the P5Q instead |
18:30.26 | goxboxlive | but where do i get the working atheros drivers? |
18:30.40 | goxboxlive | Because without network card a pc is useless |
18:31.23 | BabelO | goxboxlive: not hard, i have download it for my eeepc :) |
18:32.41 | goxboxlive | BabelO: ok |
18:32.58 | goxboxlive | so that driver will work with the P5Q |
18:34.54 | goxboxlive | BabelO: do you have the link where i can download the source? |
18:36.15 | BabelO | goxboxlive: asus website for motherboard |
18:36.43 | goxboxlive | ohhh |
18:38.50 | goxboxlive | hmm 0 files found for the p5Q card and linux os |
18:40.16 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
18:40.44 | *** part/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
18:41.13 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
18:43.24 | *** join/#htc-linux lastik_ (n=linuxrul@80.92.96.29) |
18:45.30 | BabelO | goxboxlive: http://dlsvr03.asus.com/pub/ASUS/mb/socket775/P5KPL-CM/LinuxDrivers.zip |
18:48.04 | cr2_ | BabelO: have you managed to compile qt-ext ? |
18:48.29 | cr2_ | goxboxlive: i don't even know what is a credit card :) |
18:50.31 | dcordes | goxboxlive: my p5kc came with linux driver sources |
18:50.43 | dcordes | they put them on a seperate linux folder on the driver cdrom |
18:54.37 | *** join/#htc-linux TwinReverb (n=robert@unaffiliated/twinreverb) |
18:56.04 | BabelO | cr2_: yes already compiled since first day and tested on BA, tsdogs do same on uni |
18:56.40 | TwinReverb | i need a professional opinion. thanks for the help yesterday btw. i am going to need a simple organizer when i go overseas soon. i use kontact in linux. what is the cheapest hand held computer, fast or slow, big or small, preferably inexpensive as possible, so that i can store my appointments and email on it, and some light documents / shell scripting? i don't need it to be a phone necessarily, nor a camera, nor a radio. just somethi |
18:56.40 | TwinReverb | ng simple so i don't miss appointments, and so i can store some basic stuff. |
18:59.21 | *** join/#htc-linux szsoftware (n=sven@e178223012.adsl.alicedsl.de) |
18:59.44 | szsoftware | evening |
19:01.37 | *** join/#htc-linux Spike1506 (n=Joshua@cable-62-238-192-3.zeelandnet.nl) |
19:04.34 | dcordes | TwinReverb: uuhh zaurus? |
19:04.56 | dcordes | n810? openpandora? some ipaq? |
19:10.34 | exco | how do I create a linload.exe? |
19:11.24 | *** join/#htc-linux wasup (n=Tech@208.47.103.106) |
19:16.31 | wasup | ali1234: did u here zdooder had the keyboard working |
19:19.42 | dcordes | wasup: oh that's nice. you guys should have a talk with dzo about putting a titan machine type in the git. |
19:24.17 | wasup | dcordes: oh... i will... when is the next time he is on |
19:24.33 | wasup | or wait he is on |
19:24.38 | wasup | ~seen dzo |
19:24.39 | apt | dzo is currently on #htc-linux, last said: 'yes'. |
19:27.15 | szsoftware | dzo: Hi dzo, are you around. I have a Problem with the green on screen keyboard. There are some Symbols not typeable |
19:27.50 | szsoftware | dzo: Some help or hints for debugging very appreciated! Thanks in advance |
19:29.08 | dcordes | szsoftware: why not rewriting the 20000 line driver? |
19:29.21 | dcordes | I've been wondering how those are generated |
19:39.19 | szsoftware | dcordes: sure I will take a look at the driver, but first I want to know if there is some trick |
19:40.00 | szsoftware | dcordes: do you know where that fb-kb stuff is located? |
19:41.05 | szsoftware | hm, trying to get the latest git revision... "git-rev-parse --tags --until=2008-10-08" ??? Any hint? |
19:44.45 | goxboxlive | BabelO: thx, i changed the the P5K... to P5Q and the drivers where also available |
19:44.53 | goxboxlive | cr2_: :-) |
19:45.41 | BabelO | goxboxlive: ok, p5Q should work too, just a tweak for lmsensors that'q all |
19:46.46 | goxboxlive | BabelO: That file had only audio drivers in it |
19:48.17 | BabelO | goxboxlive: mine ? nooo |
19:48.26 | BabelO | i use it for my lan eeepc |
19:49.03 | goxboxlive | BabelO: no, the one i downloaded for P5Q. But do we have the same Network card so i can use that driver you provided me? |
19:49.53 | BabelO | goxboxlive: yes it is same, newest chip on asus board are same, it is provided on 2.6.27 that's why you have only audio |
19:51.46 | goxboxlive | BabelO: ok so i can use that network card driver then |
19:51.50 | szsoftware | Sorry guys. "git-rev-parse --tags | tail -n1" == latest revision of a git-repository ? |
19:53.20 | BabelO | szsoftware: don't know much about git, sorry |
19:58.42 | *** part/#htc-linux TwinReverb (n=robert@unaffiliated/twinreverb) |
19:59.21 | *** join/#htc-linux lastik_ (n=linuxrul@80.92.96.29) |
20:03.24 | *** part/#htc-linux lastik_ (n=linuxrul@80.92.96.29) |
20:05.24 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
20:17.39 | *** join/#htc-linux Marex (n=vasum7am@auryn.karlin.mff.cuni.cz) |
20:20.50 | cr2_ | hi Marex |
20:27.35 | tmzt | dzo: cr2_ ginge : has anyone looked at zdooder's keyboard, know what the conflicts with vogue keypad is? |
20:32.25 | *** join/#htc-linux lastik_ (n=linuxrul@80.92.96.29) |
20:37.35 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
20:38.01 | ginge | tmzt: no idea what you are talking about, sorry |
20:38.42 | tmzt | cr2_: ginge: dcordes: has anyone looked at zdooder's keyboard driver, know what the conflicts with vogue keypad is? |
20:38.52 | tmzt | oh, missed that |
20:39.13 | tmzt | zdooder has support for titan keyboard but it is conflicting with the keys on the vogue |
20:39.21 | tmzt | he is using the kaiser keyboard as a base |
20:39.21 | ginge | tmzt: what device does this zdooder have? is it based on one of my patches |
20:39.29 | tmzt | titan |
20:39.48 | ginge | I see. well, he needs to rule them out one by one |
20:40.00 | wasup | ginge: he said he had it working :) |
20:40.07 | wasup | just not the side buttons |
20:40.19 | ginge | oh, well that should be easy enough then |
20:40.46 | wasup | yeah... he was supposed to email me the new zImage... but he didnt :( |
20:40.53 | wasup | so maybe if he is online today |
20:41.02 | ginge | ask him for a patch too |
20:41.26 | tmzt | is this going to require breaking out titan then? |
20:41.32 | tmzt | from vogue |
20:41.49 | ginge | yes, its a one page include |
20:41.55 | ginge | we should unify them all anyway |
20:42.09 | ginge | there really isnt much difference between them |
20:42.30 | tmzt | somewhat related question, does the proc_comm from android work with the htc (non g1) devices? |
20:42.38 | tmzt | for pmic and low-level stuff? |
20:43.14 | ginge | I dont think so. I think google had the amss for g1 modified to do a lot of stuff that htc default doesnt have |
20:43.20 | ginge | such as clocks |
20:43.23 | wasup | ginge: ok ill ask him for the patch |
20:43.54 | tmzt | they are pushing it to rmk, wonder if there needs to be something to diferentiated on amss? |
20:44.13 | ginge | not sure how they are going to handle that part |
20:45.17 | tmzt | we have code for clocks/power? |
20:45.57 | ginge | we wrote our own clock handler. power is still tricky, but isnt proc_comm |
20:46.29 | tmzt | it seems the are only pushing MACH_HALIBUT |
20:46.38 | ginge | makes sense |
20:46.49 | ginge | even if you cant get the halibut boards |
20:53.22 | goxboxlive | BabelO: well i canceled the P5K and bought a P5Q instead. I hope compiling the driver will work ok. The only thing that concern me is if debain manage to install all the packages i need for compiling the driver |
20:53.57 | goxboxlive | I dont know if the headers are installed from the cd or if need to have a internet connection to download the source from a repo |
20:54.40 | goxboxlive | I tested to compile the driver on my laptop and it compiled. |
20:55.06 | *** join/#htc-linux hqqh (n=hqqh@e178164033.adsl.alicedsl.de) |
20:57.23 | BabelO | cr2_: what was you laptop reference ? |
21:00.01 | wasup | ginge: is titan the only device with touch screen issues? |
21:00.07 | wasup | like moving the clock |
21:00.43 | ginge | wasup: define issues? |
21:00.57 | wasup | the touchscreen is not accurate |
21:01.03 | wasup | sometimes it is |
21:01.09 | wasup | but most of the time. |
21:01.19 | wasup | you press one thing and something else will open up |
21:01.39 | ginge | wasup: yeah kaiser is a bit like that |
21:01.43 | wasup | if you try to drag the main clock on the screen.... it will not drag, it freaks out |
21:02.32 | wasup | is there anyway to improve the reliablilty of the touchscreen? |
21:02.56 | cr2_ | BabelO: laptop ? |
21:03.11 | wasup | you think when the g1 when it comes out... help with any of those issues? |
21:03.28 | cr2_ | ginge: i think i'd document _all_ the msm7201A registers i can see |
21:04.08 | cr2_ | ginge: for some of them it will be not easy to assign the name/purpose, but only an action |
21:04.33 | cr2_ | there are much more clocks than one can see in the wince & wince spl. |
21:04.38 | BabelO | cr2_: yes your computer with amd cpu :) |
21:05.02 | cr2_ | BabelO: nx6325, but it's more than 1 year old already |
21:05.47 | cr2_ | BabelO: there was also the acer 1500, but it was the first amd64 laptop. completely outdated |
21:08.11 | ali1234 | wasup: did you calibrate the touchscreen? |
21:08.31 | BabelO | cr2_: thx |
21:08.39 | BabelO | cr2_: you see my email yesturday ? |
21:10.02 | *** join/#htc-linux Raketemensch (n=Rakete@192.234.2.49) |
21:11.24 | tmzt | swetland's emails on arm-kernel mentioned names for a bunch of clocks, don't have the link right now |
21:12.18 | hqqh | hi, g1 and htc touch hd have the same cpu (msm7201a). so will be all linux drivers (gsm, gps ...) open source? |
21:13.00 | tmzt | hey, I need to go, be back in an hour or so |
21:13.04 | cr2_ | BabelO: yes, looks really cool. |
21:13.49 | cr2_ | tmzt: many clocks are documented in the wiki. there are some differences between 7200 and 7201A in the register postitions |
21:14.12 | *** join/#htc-linux diogene31_ (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
21:14.40 | BabelO | cr2_: and symbols detection works well too :) |
21:14.43 | cr2_ | hqqh: gsm and gps are controlled by arm9 (amss microkernel). afaik there is, and there will be no source for it. |
21:14.53 | cr2_ | BabelO: what about rivers |
21:15.33 | cr2_ | hqqh: since htc uses a different microkernel, we need to write some code missing in the git.android |
21:15.41 | cr2_ | hqqh: i guess it was intentional |
21:16.55 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
21:16.57 | cr2_ | hqqh: wifi driver is the most interesting piece of software in android. if it's for ti125x |
21:20.12 | cr2_ | g1 ;-) |
21:20.37 | BabelO | cr2_: shoud not be too hard to extract river |
21:25.07 | wasup | ali1234: yeah i did |
21:25.59 | swetland | cr2: the g1 kernel source release will include a ti1251 driver |
21:27.42 | cr2_ | swetland: these are really great news. very promising :) |
21:29.25 | swetland | I'm very much looking forward to seeing what you folks do with full platform sources, once available |
21:29.31 | swetland | I expect it will be interesting times |
21:30.30 | wasup | what is the ti1251 driver? |
21:33.33 | cr2_ | swetland: agreed. i can't even count the amount of the devices that will become a working wifi. |
21:33.58 | BabelO | cr2_: ti1251 , i can use this driver on my artemis too :) |
21:34.13 | BabelO | hi swetland |
21:35.10 | cr2_ | BabelO: yes. and n560, and hermes, and ... |
21:35.22 | BabelO | swetland: android plateform will be released so we can fully compile it for our actual mobile device ? |
21:35.51 | BabelO | cr2_: :) very good, i ve to check again the ti chipset ni atrtemis |
21:35.53 | swetland | the only pieces which will not be open source (that I can think of): |
21:36.02 | swetland | - some of the google specific apps (gmail, gmaps) |
21:36.15 | cr2_ | it's reasonable |
21:36.20 | BabelO | yes agree |
21:36.23 | cr2_ | it's not the kernel after all |
21:36.33 | swetland | - a couple pieces of qualcomm proprietary code in userspace (camera library, h264 library) |
21:36.54 | swetland | - the radio interface library (glue between the framework and the specific radio) from htc |
21:37.16 | cr2_ | the last one is not rocket science |
21:37.21 | swetland | there is a generic/reference radio interface library (the emulator uses a variant), and I doubt people will have trouble customizing it for various hardware |
21:37.30 | hqqh | wasup: i think the wlan baseband processor made by ti tnetw1250 (http://www.ti.com/litv/pdf/splt148) |
21:37.48 | swetland | and yes, not at all rocket science |
21:37.49 | BabelO | swetland: aleready the case in qtopia, we have to adjust dialog for each modem |
21:37.51 | cr2_ | swetland: does g1 really have a digital compass ? |
21:38.06 | swetland | babelo: yeah this stuff tends to need to be tweaked to the specific radio in any case |
21:38.13 | swetland | cr2: yes, compass/accelerometer |
21:38.39 | swetland | that's how the maps streetview compass mode works, for example |
21:38.40 | cr2_ | swetland: compass = magnetic field measurement ? |
21:39.03 | swetland | cr2: I believe so (I haven't actually dealt with that specific component myself) |
21:39.13 | BabelO | hope that's HTC release a ROM for artemis :) |
21:39.21 | cr2_ | interesting. |
21:40.01 | swetland | anyway, you will get code for pretty much the entire system userspace and kernel except for the handful of things I described above (probably one or two others, but all relatively minor pieces) |
21:40.02 | cr2_ | BabelO: it#s a manpower problem == will not happen |
21:40.38 | cr2_ | swetland: brf6300 will work too ? |
21:40.47 | hqqh | cr2_: yes, a colleague used such a ic for a marine-compass project |
21:40.51 | BabelO | cr2_: anyway if wifi is ok, i can continu to look only at gsm + batteri so artemis will be like BA |
21:40.57 | swetland | in theory, one should be able to grab the 4-5 proprietary libraries from a production G1, recompile everything else, and you'll have a G1 build |
21:41.06 | swetland | bluetooth certainly will work ^^ |
21:41.29 | BabelO | cr2_: artemis -> TI TNETW1230 |
21:41.48 | cr2_ | hqqh: i don't see the compass in raphael. yet. |
21:42.23 | cr2_ | BabelO: look at the acx100 chipset support list |
21:42.57 | cr2_ | BabelO: i think they differ mostly in the firmware |
21:43.13 | BabelO | cr2_: that's ok with support list |
21:43.14 | cr2_ | swetland: will the source be released on 22oct ? |
21:43.27 | *** join/#htc-linux ellisway (n=ellis@80-46-67-47.static.dsl.as9105.com) |
21:44.58 | swetland | we are hoping to have the source release happen as close to the hardware ship date as possible. I don't have an official date/time I can say, but I believe people will be quite happy with the results. |
21:45.36 | cr2_ | ok |
21:45.36 | swetland | there's a lot of work going on to get the external infrastructure set up (we're not just dumping a pile of tarballs out there -- this will be live repositories, patch submission systems, etc, etc) |
21:45.46 | BabelO | swetland: anyway it is a good progress :) will see if omap can be finished to support full android |
21:46.03 | swetland | it should totally be possible to run android well on omap |
21:46.18 | swetland | I've got a couple of these omapzoom reference devices that I'd like to get stuff running on |
21:46.23 | BabelO | swetland: actually i run it on my artemis, but with some lack :( |
21:46.40 | cr2_ | BabelO: it's a bit tricky because omap850 has it's own arm7+dsp |
21:46.42 | swetland | and I had stuff running on n800 last christmas -- anyone know if they ever released a new wifi driver (for 2.6.25 or thereabouts)? |
21:46.46 | cr2_ | with its own firmware |
21:47.07 | swetland | ah yeah, 850 startup will probably be a bit of work to pull off without support from the vendor |
21:47.07 | cr2_ | swetland: for which chipset ? |
21:47.12 | BabelO | swetland: i have n800 too |
21:47.18 | swetland | cr2: the conexant stuff in n800 |
21:47.29 | swetland | the driver is binary only and last I checked only worked with 2.6.21 |
21:47.34 | BabelO | swetland: i read nothing about it |
21:48.01 | swetland | which is why I shelved my n800/810 work, because I don't feel like working on backports to a pretty old kernel and without wifi the devices are not terribly interesting |
21:48.25 | BabelO | cr2_: big work on artemis will be the sound part :( i don't think i can get it to work |
21:48.41 | swetland | sound on 850 is a pain in the ass |
21:48.48 | BabelO | cr2_: sound can be routable as bt, but playing mp3 or ringtone that |
21:48.59 | swetland | because you generally need to cooperate with the baseband for routing and control |
21:49.09 | cr2_ | BabelO: i didn't look how it works. is it on arm7 ? |
21:49.12 | BabelO | swetland: i still don't knwo if it is EAC or DSP or aic external chipset |
21:49.31 | cr2_ | BabelO: you don't have the motherboard pictures ? |
21:49.33 | swetland | probably EAC, but has to be coordinated with the baseband |
21:49.48 | swetland | at least the 850 stuff we worked with was like that |
21:49.50 | BabelO | cr2_: yes service manual, but bad picture :( |
21:49.58 | cr2_ | yeah |
21:50.06 | BabelO | swetland: i see a EAC driver without PCM support |
21:50.14 | *** join/#htc-linux LunohoD_ (n=alex@e180068019.adsl.alicedsl.de) |
21:50.15 | BabelO | never try it on artemis |
21:50.57 | BabelO | swetland: was poaying with sdio wifi init, but i ll wait now :) and try to get syren spi working like i do for touchscreen |
21:52.11 | BabelO | s/poaying/playing/ |
21:53.56 | cr2_ | BabelO: the omap850 diagramm shows the pcm spi port |
21:54.31 | BabelO | cr2_: where is it ? i did not see in memory map :( |
21:56.24 | BabelO | swetland: so, no doc G3 driver :) |
21:59.40 | BabelO | cr2_: http://markmail.org/download.xqy?id=wytl5tc5b6tegxaw&number=1 |
22:01.45 | BabelO | cr2_: i understand why someone speak to me about my touchscreen spi driver for omap850 :) and some other thing like GPS / BT |
22:02.32 | cr2_ | BabelO: yes, i2s+EAC |
22:24.27 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
23:04.00 | *** join/#htc-linux bertramt (n=chatzill@f.moraine.tec.wi.us) |
23:12.36 | *** join/#htc-linux zdooder (n=troy@c-67-160-50-188.hsd1.wa.comcast.net) |
23:12.53 | zdooder | Hey wasup that e-mail I sent you yesterday bounced... |
23:16.39 | *** join/#htc-linux Raketemensch (n=Rakete@24-151-90-116.static.nwtn.ct.charter.com) |
23:23.17 | wasup | samuelbarthelemy@gmail.com |
23:23.47 | wasup | can you send me it again |
23:24.39 | *** join/#htc-linux timebomb (n=timebomb@e176101065.adsl.alicedsl.de) |
23:27.41 | zdooder | wasup: should be on its way now |
23:29.04 | *** join/#htc-linux webPragmatist (n=none@99-6-241-169.lightspeed.rcsntx.sbcglobal.net) |
23:33.50 | wasup | k..thanks...what email did i give you yesterday? |
23:35.01 | zdooder | not sure... looks to me like it's the same one (?) |
23:35.40 | wasup | zdooder: hmm..thats the right one |
23:36.14 | wasup | i still haven't gotten it... |
23:37.16 | zdooder | how about http://wormhole.akropolys.com/htclinux/zImage-wasup_TRY_THIS_ONE |
23:37.25 | zdooder | ;-) |
23:37.51 | wasup | hahaha....nice... :) |
23:38.13 | wasup | so...what happens when you boot android with this zimage? |
23:38.28 | zdooder | haven't really played with it much, but the keyboard appears to work... |
23:38.44 | wasup | yeah? |
23:38.52 | wasup | does the side power button still work? |
23:39.07 | zdooder | I was able to type but am testing it on a not-in-service titan, so no data connection or anything. |
23:40.07 | zdooder | no the power button doesn't work anymore |
23:40.14 | zdooder | (At least I don't think so) |
23:41.31 | wasup | so in other words if the screen goes to sleep.....bye bye titan? |
23:41.37 | wasup | or hello soft reset? |
23:41.45 | zdooder | BTW, the soft keys on the keyboard (ONLY -- not on the front of the phone) are left=menu, right=back |
23:42.06 | wasup | oh nice...:) |
23:42.14 | zdooder | Well... yeah maybe... obviously the next step is to get the other buttons working (again?) ... the directional keypad and the softkeys on the front and side of the phone. |
23:42.53 | zdooder | I'm a little worried about playing with the power button after hearing some of what dzo said about the power collapse mechanism and all that, but it worked before, right? |
23:42.53 | wasup | yeah....so how does that work? |
23:43.39 | wasup | i mean how can we fix that? |
23:45.18 | zdooder | More experimenting to determine the cpld bits used by them... I think the Titan is like the Kaiser in that there is no IRQ for them so we'll need a polling driver to monitor for them (which is how they did it in the Kaiser) |
23:45.46 | zdooder | (Of course, I'm assuming that they're all cpld bits, I could be wrong there, but I was starting with the directional keypad thing and I'm pretty sure it is) |
23:47.16 | cr2_ | lol |
23:47.22 | cr2_ | http://forum.xda-developers.com/showthread.php?t=434535 |
23:47.53 | wasup | well i was thinking |
23:48.12 | wasup | would it be better to use the kaiser tree instead of the vogue? |
23:48.31 | wasup | like in order for the screen to rotate when we open the keyboard |
23:48.43 | wasup | or just take that stuff from the kaiser. |
23:49.00 | cr2_ | wasup: on raph100 it's just an msm gpio event. |
23:49.06 | zdooder | I'm not sure, it was looking to me like we'd want the vogue tree because it has the touchscreen driver and it seems like dzo is *the man* when it comes to the power management and modem bridge and stuff like that. |
23:49.41 | zdooder | Regarding the screen rotation thing I think it's a gpio event on Titan too, just not sure how to "tell" Android/the OS that it should rotate the screen... cr2_ any ideas? |
23:51.43 | wasup | hmm...we cant just take it from the other working ones, :( |
23:51.48 | zdooder | does the kaiser have the slide-out keyboard? |
23:52.49 | tmzt | could the differences be handled through platform resources in the machine file? |
23:53.44 | zdooder | Might be the smart way to do it, I am still learning about them :-/ |
23:53.54 | zdooder | "the machine file" I mean :) |
23:54.09 | zdooder | I assume you mean "board-<platform>.c" right? |
23:54.26 | tmzt | at least for gpio-keys or whatever is doing the extra keys on vogue/side of titan |
23:54.30 | tmzt | and kaiser/polaris |
23:54.34 | tmzt | yes, that file |
23:54.47 | tmzt | it doesn't have that consistent a name on pxa |
23:54.52 | zdooder | Seems like Kaiser was handling the keys from the keyboard driver, though... right? |
23:55.09 | zdooder | (all of that "timer20hz" stuff) |
23:55.35 | cr2_ | zdooder: screen rotation is a userspace thing. opie had it for ages |
23:55.57 | tmzt | its on input device, right? |
23:55.58 | cr2_ | zdooder: it was working perfectly even on my sl5500 |
23:56.11 | zdooder | cr2_: Sure, but how does driver (kernelspace thing) tell userspace to do it? |
23:56.30 | cr2_ | zdooder: gpio button or switch event. |
23:57.05 | zdooder | cr2_: userspace can't read those can it? |
23:57.11 | cr2_ | it's the same on the universal. |
23:57.13 | tmzt | X is already monitoring other input devices, though things like frameworkd are handling it on om |
23:57.24 | cr2_ | why ? it's just one more "button" |
23:57.38 | cr2_ | like keyboard event |
23:58.07 | zdooder | ok my knowledge of kernel internals is very weak |
23:58.17 | zdooder | I can see that keyboard driver calls input_report_key() when a key is pressed |
23:58.33 | zdooder | Are you saying that there is a "rotate-the-screen" key that should be reported? |
23:58.44 | zdooder | Or that that is some other kind of input event? |
23:58.56 | tmzt | EV_SWITCH? |
23:59.01 | tmzt | ?? |
23:59.08 | zdooder | ahhh... input_report_switch() maybe? |
23:59.11 | zdooder | smacks head. |