irclog2html for #htc-linux on 20061207

00:03.55lkcloh maan.  udev synthesising hotplug events has _always_ killed performance.  roll on depinit...
00:10.50BabelOuedlkcl : any success attaching uda1380 ?
00:10.54lkclyep.
00:11.00lkclon the i2c bus anyway
00:11.14lkclwhen i modprobed pxa-i2c suddenly things woke up oops
00:11.20BabelOuedthat s a good start :)
00:11.34BabelOuedoverrun ?
00:12.57lkcldunno yet.  usual audio rubbish stuff... GPIO...
00:13.24lkclasoc: DAI[0:0] failed to match format
00:13.24lkclasoc: DAI[1:0] failed to match rate
00:13.25lkclasoc: no matching DAI found between codec and CPU
00:13.25lkclALSA sound/core/oss/pcm_oss.c:940: HW_PARAMS failed: -22
00:13.25lkcloops
00:13.35lkclwell... that's different
00:15.11BabelOuedsometimes on my BA i can't run i2cdetect, it return XX for all adress :(
00:16.29lkclahh, that'll be due to the codec being powered off.
00:34.33lamikrHi, I put the screenshot from newest gomunicator: http://aragorn.kortex.jyu.fi:8080/h6300/screenshots/gomunicator_front.png
00:36.23lamikroperator info is now on the right... And there is also millivolts, battery and radio link levels working. We need get the mvolt info disappear from the screen for devices not supporting it.
00:54.33lkclRalith: blueangel (aka xda IIs)
00:54.55Ralithah.
00:55.02lkclsorry.  was investigating asoc.  pita.  mismatch between ssp driver params and codec params.
00:55.28lkclthe new asoc code (alsa system-on-chip) code is quite sophisticated... but not finished :)
00:55.50lkclit used to be all hacked-in, into one really baaad set of code
00:56.40lkclok.  at the _moment_ i'm on blueangel.  last week it was sable.  last year it was universal.  year before that it was blueangel and himalaya.  year before _that_ it was himalaya :)
00:57.00lkcllamikr: cool!
00:57.38lkclRalith: what device you have (i missed the earlier conversation as my router got unplugged somehow)
00:59.36Ralithlkcl, I'm intending to purchase a universal soon, and very eager to have linux on it.
00:59.40lkclcool.
01:00.25Ralithalso interested in helping out if possible, although I'm not really very experienced in C, let alone reverse engineering/kernel hacking
01:01.24lkclwell, the universal is the closest thing to 'complete' of the HTC phones.
01:02.16Ralithwhich is one of the reasons I'm going for it instead of, say, the TyTN
01:03.00lkclif you wanted to help out, you could always set up an openembedded.org build environment, and build your own opie+familar and gpe distributions, and then publish them.
01:03.04lkclheh.
01:03.15lkclwell, the TyTN (codenamed hermes) is next on the list.
01:04.13Ralithisn't there already a published opie+familiar distro?
01:04.58Ralith(also, the Universal is much cheaper on ebay than the TyTN, and the full VGA screen + bigger keyboard are both things I look forward to eagerly)
01:05.27lkclyerss.... published, yes, not-necessarily-up-to-date-and-specifically-tailored-to-the-universal, no
01:05.44lkclbut speak to people here as they drop by, and ask if that would be something useful.
01:06.13lkclahh, but the universal's battery life (due to the pxa27x absolutely shit power management) kills it for me.
01:06.39lkcli much prefer the hermes as it has the samsung s3c2442 processor.  6 day battery life
01:06.42Ralithcan't a software-level cpufreq scaler help?
01:07.26Ralithalso, I don't intend to be away from my charger for more than 12 hours
01:09.08Raliththoughts?
01:10.33lkclit's the suspended (0Hz) state that has the awful power management on the intel arm processors.
01:11.02Ralithhow long does it take to boot?
01:11.03lkclat least the Texas Instruments OMAP processors got it right, although those are _really_ bad processors capable of at most 200mhz
01:11.24Ralithinto, say, the opie gui
01:11.33lkclthe universal?  probably about... 1 to 2 minutes, at a guess.
01:11.46Ralithhm.
01:11.51lkclit's a 500mhz processor, equivalent to a 1ghz Pentium III
01:11.58Ralithso there's a good reason to suspend
01:12.38lkclbut, in user-space, there is udev, which takes a good 20 seconds of that boot time just sitting there (i know why - it's complicated to explain: look up depinit advogato on google)
01:12.58lkclhttp://www.advogato.org/person/lkcl/diary.html?start=280
01:13.14Ralithis that something that can be overcame?
01:13.18lkcl10 may entry
01:13.19lkclyes.
01:14.06lkclbut like i said, it's complicated to explain.  you need a parallel init (startup / process management) system to get round the problem.
01:14.13Ralithis there any chance of that being done soon? :P
01:14.33Ralithis that likely to be implemented?
01:14.46lkclso - if you _really_ wanted a task-and-a-half, then you could try compiling up depinit for your shiny new universal you're about to get :)
01:14.58Ralith:P
01:14.59lkcli can send you my scripts that i have running on my fujitsu laptop.
01:15.06lkclare you any good at shell scripts etc?
01:15.18RalithI know the basics of bash and can learn.
01:15.57lkclthe boot-time would be cut to about under 30 seconds, using depinit, and power-down time to under FIVE seconds.
01:15.57Ralithcool.
01:15.58lkclsysvinit is shit.
01:16.24lkclhttp://www.nezumi.plus.com/depinit/index.html
01:16.47Ralithand yer sure that depinit is the best option?
01:16.56lkcli think that the arm processors of 400mhz + can be considered 'modern' by now
01:17.51lkclok - there _are_ alternatives: there is gentoo's parallel-startup system, which is based on the principles of depinit, because depinit was in linux-from-scratch, and gentoo started from linux-from-scratch with portage (ported from freebsd to linux)
01:17.53lkclwhew :)
01:18.21lkclbut i _understand_ depinit, and i know the author.  so i can help advise you.
01:18.27Ralithheh
01:18.31Ralithworks for me
01:18.37lkclgood man!
01:19.07lkclif you get it started, that will at least encourage me to kick in and help
01:19.21lkclanyway.  i got to sort out sound.
01:19.32Ralithgood luck
01:20.00Ralithoh, one more random question, if you have time: what's wince's boot time, for comprison?
01:21.26BabelOuedlkcl: if you want to find where time is lose : http://www.bootchart.org/
01:26.12*** join/#htc-linux BHSPitMonkey (n=stephen@adsl-65-68-200-65.dsl.rcsntx.swbell.net)
01:26.14lamikrlkcl: How is the power management handled in htc devices. Do you use apm kernel emulation or "echo mem /sys/power/state" way of doing things...
01:26.20BHSPitMonkeygood afternoon
01:29.49BHSPitMonkeyI hate to be so inappropriately appropriate, but I figured here would be my best shot:  is there a way to share internet access with my smartphone via bluetooth? (phone=wm5.0, pc=linux)
01:30.06Ralithyeah
01:30.16Ralithwell
01:30.18Ralithwhich way?
01:31.25lkcltaaa
01:31.57Raliththe phone can be made to act as a modem
01:32.08Ralithit's been done before
01:32.14Ralithgoogle will find a fair number of results
01:32.17lkcllamikr: i just do apm --suspend, from opie
01:32.18BHSPitMonkeyyeah, I meant the reverse
01:32.51RalithBHSPitMonkey, it should be possible, but I dunno how.
01:33.16lkclBabelOued: my fujitsu laptop, running debian with depinit, takes the usual 20 seconds to start all the kernel, and the first process, instead of /sbin/init, is /sbin/depinit.  from there, it is under 20 seconds to start Xorg and _all_ other services.
01:33.17BHSPitMonkeyI used to do it with my symbian phone
01:33.45lkclthe same laptop: if i use /sbin/init, then /sbin/init takes OVER NINETY seconds to get everything started.
01:34.45lamikrlkcl: Ok, with omap kernels the apm emulation is not supported.--> will hang. Instead we use this "/sys/power/state" way. I am just missing an userspace app like apmd for this other way of doing things which could but my device to sleep after couple of minutes inactivity.
01:34.48lkclsysvinit was designed for when context-switching took forever, because the maximum CPU speed available, on a 68020 or 68030, was 16mhz if you were lucky.
01:34.58BabelOuedlkcl: on suse we have same, it is startpar :) and bootchart help me to optimise a little between io usage and cpu usage
01:35.24lkclstartpar is a parallel ok cool.  very good.
01:36.05lkcldepinit is sufficiently advanced that it actually finds bugs in the linux kernel :)
01:36.36Ralithhaha
01:36.36Ralithnice
01:36.55Ralithsounds impressive
01:37.07lkclyou couldn't use it for early 2.6 kernels because signals would not be correctly sent to process 1, if process 1 had been put into 'stop' state rather than 'running' :)
01:38.06lkclthe solution was to have a script which constantly sent a kill -HUP to process 1, every second.  that kept process 1 'awake' and so it received all the other signals from all (parent - i.e. eeevery) processes.
01:38.12lkclit's a long story.
01:38.40lkclbut Ralith: you would do well to investigate e.g. startpar, and the gentoo one, and depinit etc. etc.
01:39.22Ralith-_-
01:39.25lkclwhich brings me on to another - different - point: kernel-driver parallel-initialisation
01:39.30Ralithsounds like an obscene amount of work
01:39.38Ralithand how likely is that to get implemented?
01:39.47lkclwell, it took me two weeks to get depinit installed on my debian laptop.
01:40.23lkclbasically, i was working from richard lightman's customised (and very sophisticated) linux-from-scratch depinit example scripts, to create debian-ish ones.
01:40.39lkcllong story.
01:40.41Ralithbest to use custom ones anyway, in a context like this
01:41.22lkclwell, they're pretty much customised anyway: see /etc/init.d on the opie distro for example.
01:41.54Ralithso what's this about parallel driver init?
01:42.13lkclbut basically, for every entry in /etc/init.d/ you need to create a matched corresponding pair of /etc/depinit/<name>/startup and stop scripts or... well, that's not quite true: it's a long story
01:42.15lkclah.
01:42.20lkclwell...
01:42.51lkclif you have two busses, what the hell are you waiting around to initialise one bus - and its devices - followed subsequently by then starting on the second bus??
01:43.23Ralithexplain depinit to me once I have the universal (which might not be too soon)
01:43.24Ralith:P
01:43.32Ralithbut yeah
01:43.35lkclthat's the basic question.
01:43.36RalithI get why it's a good idea
01:43.45Ralithbut how likely is it to be done?
01:43.59lkclplatform_device(s) are now set up as 'children'.
01:44.07lkclthe asic3_base.c is a good example.
01:44.17lkclso in theeeoory, it should be possible to do :)
01:44.26Ralithyeah, but who's going to? :P
01:44.38lkclwell... me, probably.  as an experiment.
01:45.00Ralithheh
01:45.01lkclbut, to be honest, udev with modprobe does most things in parallel, anyway.
01:45.02Ralithyay!
01:45.08Ralitheven so.
01:45.11Ralithgood to be complete
01:45.20lkclit's just that if you compile your kernel with everything built-in...
01:45.29Ralithand how far-ranging will be these changes?
01:45.31lkclso, udev takes care of _most_ of it.
01:45.35lkcli honestly don't know.
01:45.36Raliththat phone, HTC phones, or all of linux?
01:45.41Ralithnot in terms of code :P
01:48.39lkclall of linux.
01:48.44lkclit's only a thought, so far.
01:48.48Ralithcool.
01:48.50Ralithgood luck :)
01:49.05lkclit _might_ be something as simple as putting in a call to schedule_work() somewhere in platform_device_register()
01:49.31lkclanyway.  sleep time soon.
01:53.22Ralithseeya.
02:02.34*** join/#htc-linux ellisway (n=ellis@host-87-74-241-174.bulldogdsl.com)
02:10.38*** join/#htc-linux ralith_ (n=ralith@soggy202.drizzle.com)
02:27.58*** join/#htc-linux lkcl_ (n=lkcl@535411CB.cable.casema.nl)
04:18.38*** join/#htc-linux psokolovsky_ (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com)
06:11.20*** join/#htc-linux JTRipper86 (n=jtripper@p54B1D52A.dip.t-dialin.net)
07:06.47*** join/#htc-linux goxboxlive (n=goxboxli@gw.hjelcowi.no)
07:14.39*** join/#htc-linux LunohoD (n=alex@e180064146.adsl.alicedsl.de)
07:25.55*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
07:59.52*** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk)
08:09.33*** join/#htc-linux Fossi (n=cmewes@195.177.48.115)
09:30.32*** join/#htc-linux bd2 (n=ufo@89.113.84.151)
10:07.23*** part/#htc-linux goxboxlive (n=goxboxli@gw.hjelcowi.no)
12:08.44*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.231)
12:29.11*** join/#htc-linux rob_w (n=bob@p85.212.155.144.tisdip.tiscali.de)
13:16.05*** join/#htc-linux TripleDES (n=sergio@89.129.143.241)
13:22.19*** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk)
13:24.49*** join/#htc-linux psokolovsky_ (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com)
13:51.16*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
14:33.15*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
15:17.49*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
15:24.04psokolovsky_Hi!
15:24.49psokolovsky_I sent a report regarding OPIE's issues in Angstrom and way to solve the situation to htc-pxa@ list.
15:25.01psokolovsky_expecting your response, guys ;-)
15:56.11*** join/#htc-linux rob_w (n=rob_w@p549B93C5.dip0.t-ipconnect.de)
15:58.51*** join/#htc-linux Ralith (n=ralith@66.150.12.86)
16:45.48*** join/#htc-linux ellisway (n=ellis@host-87-74-241-174.bulldogdsl.com)
16:58.57*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
17:02.49*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
17:11.49*** join/#htc-linux Ralith (n=ralith@66.150.12.86)
17:14.13*** join/#htc-linux ralith_ (n=ralith@66.150.12.86)
17:22.40goxboxlivehi
17:23.11goxboxlivepsokolovsky_ So you think that we shal make a new distr.
17:23.39goxboxliveThere are AFAIK two issues with angstrom and opie.
17:23.49goxboxlive1) Is the missing getkey
17:24.06psokolovsky_goxboxlive, no, that's just an idea ;-) but I lean to it, after all, assuming we'll be able to work together on it.
17:24.15Ralithyou can just fork the existing ones, can't you?
17:24.18Ralithadd what you need
17:24.20goxboxlive2) Is that psplash screwing up the opie gui
17:25.00goxboxliveI think i have solved the psplash stuff.
17:25.45goxboxliveIn /etc/init.d/opie there is a line that days this:         echo Starting Opie....
17:25.45goxboxlive<PROTECTED>
17:25.54psokolovsky_goxboxlive, believe me, those are only first and relatively minor issues ;-)
17:26.16psokolovsky_goxboxlive, but you're right that with own distro we would be free to solve them as we like ;-)
17:26.33goxboxliveIf we move it to terminal 3 i guess it will work. Seems like bootup takes tty1, psplash tt2 and also opie tty2.
17:27.20psokolovsky_goxboxlive, but the real big issue OPIE, GPE, and anything else has in OE (and any other such system) is inconsistent device support. That's what I'd be interested to address. And there will be lots of breakage on that way ;-)
17:27.25goxboxliveYes, we could just as you said make a new one based on Angstrom
17:27.32psokolovsky_goxboxlive, Sounds scary, right? ;-)
17:28.12goxboxliveyes :-)
17:28.12psokolovsky_goxboxlive, good analysis on psplash issue
17:28.36psokolovsky_goxboxlive, so, please give it good thought, discuss with cr2/other folks, and then let's see what we'll have... ;-)
17:29.23goxboxliveYes, of course.
17:31.46goxboxliveBut if you do that, i think we just shall just consentrate on Opie since there are allredy a distro that has fully GPE support.
17:32.05goxboxlives/you/we/
17:34.38psokolovsky_goxboxlive, sure, only opie. angstrom will do gpe ;-)
17:34.39goxboxlive22222222Ralith: Yes you can fork the exiting ones, but the issue here is that Angstrom will not support Opie, only GPE. So at the moment the Angstrom-opie-image doesnt work quite right. You have to do some hacks to get it working right.
17:34.46goxboxlivepsokolovsky_  right.
17:37.25cr2goxboxlive: can you explain me why opie support is such a big issue (in technical sense) ?
17:37.58goxboxlivecr2: Do you mean from our suide of view or that Angstrom wouldnt support it?
17:38.08cr2i have created http://wiki.xda-developers.com/index.php?pagename=HTC_Audio
17:38.16cr2goxboxlive: from our side
17:38.46cr2what is so special about angstrom with gpe removed ?
17:39.12goxboxlivecr2: Well, the Angstrom distro is mor up 2 date than familiar.
17:39.31cr2think angstrom+openmoko, or angstrom+x11+qt
17:39.54goxboxlivebut i think angstrom+x11+qt will be to slow
17:40.09cr2why ?
17:40.24cr2let's be more specific.
17:40.33cr2can i remove gpe from angstrom ?
17:41.00cr2remove == exclude all gpe-dependent packages.
17:41.01goxboxliveYes, you are able to make a angstrom-bootstrap-image
17:41.12cr2ok.
17:41.16goxboxliveAnd that should be gpe free.
17:41.26cr2can we build a eabi opie image.
17:41.51cr2afaik it's located completely in /opt/Qt*
17:42.01goxboxliveisent it eabi in angstrom?
17:42.13cr2does it need some additional packages ?
17:42.21goxboxlivei guess my compillator is eabi
17:42.38cr2eabi is binary convention in a sense. like elf/ecoff.
17:43.23cr2ok, so we can build eabi opie
17:43.42cr2are there eabi-related opie problems ?
17:44.35cr2keyboard is not eabi-related :)
17:45.21goxboxliveno, there arent, But it is the getkey support, and if there will be any changes in angstrom later they wouldnt take care about opie issues
17:45.39cr2which package is getkey ?
17:45.48goxboxliveNOt that we SO need getkey. But that's the first issue.
17:46.02goxboxliveThere is no getkey package, it is a patch to busybox
17:46.21cr2busybox,i guess. does busybox support stty 921600 now ?
17:46.47cr2if not, we need to patch it too.
17:46.55goxboxlivei dont know, i havent tried
17:47.05cr2so getkey+921600 pathes are needed.
17:47.16cr2s/pathes/patches/
17:47.22cr2we need it on sable.
17:47.43goxboxliveI dont know about 921600. Ask psokolovsky_ if they have have support for it.
17:47.54cr2we will resolve the keyboard issue.
17:48.05cr2sable is the only device is know that needs it.
17:48.21goxboxliveok
17:49.00cr2the zroadmap patch from your collection you can submit to oe anyway.
17:49.44cr2maybe they don't care, but it's an openzaurus package, so it should be accepted.
17:51.25goxboxliveyes, i know. But that's not a porblem i think. But the problem is as i said when changes in Angstrom distro they wouldnt care about breaking some opie stuff. And that will end up with a useless opie image. Nad when no one is able to build opie then it will be remved form OE.DEV
17:52.13goxboxliveBecause, if you use familar now, opie wouldnt build. You have to do some hack to build it.
17:53.56goxboxliveAnd if we made a own distro based on the angstrom, but optimized for Opie we will have both gpe (with agnstrom)  working, and Opie working with a Angstrom based distro.
17:54.25*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
17:54.57goxboxliveBut, maybe we shouldnt do this before we have tried out Openmoko. If Openkoko is a killer then i guess no one will use Opie/GPE anyway.
17:55.50goxboxliveBeacuse i think Angstrom will support Openmoko since Mickey isone of the Openmoko gyus and he also is a Angstrom developer.
17:56.49cr2i want zroadmap, and it's a qt app :) so i do care.
17:57.04cr2i think this is all too abstract talk.
17:57.37cr2if this "distro" will differ by 1k patches, i don't really care.
17:57.59cr2and don't tell me getkey breaks opie :)
17:58.14cr2i just don't see how angstrom can break opie.
17:58.35goxboxliveNo, it doesne break opie. But as i said, what's next
17:58.55cr2well, what _can_ break opie ?
18:00.30cr2i will not put too much hope in openmoko in near future, because it does not have bt,wifi,umts,videophone.
18:00.30goxboxliveWell i guess it want break Opie, but what about if they include some GTK+ shit, and building angstrom will break without it.
18:00.40goxboxlivei c
18:01.06cr2you have told me there is angstrom-bootstrap.
18:01.30cr2let's think what we need on top of angstrom-bootstrap.
18:02.28goxboxlivehmm, yes there is a angstrom-bootstrap-image
18:02.32cr2if they want to break opie intentionally, they can always do it. but i doubt it's a very big issue, because this breakage will not be big.
18:03.19cr2and they are not microsoft, their code is open, it is easy to fix the breakage.
18:05.26cr2i don't really think the running something off the framebuffer is a very bright idea nowdays, that's why i'd always like to have a x11+qt option.
18:05.51goxboxlivei c
18:08.03goxboxliveWell i dont know what to do, but i understand that psokolovsky mention it, because stuff that he would like to add or fix in favour of Opie wouldnt be accepted, and that's kind of frustrating for him i guess since he is the only one who maintain Opie in OE.
18:10.12psokolovsky_goxboxlive, well, I'm not the only one who works on opie, but I'm the one who took duties it will be kept in OE, and will serve purpose for users. So, current movement is more based on the issues you experience right now, then myself.
18:10.41psokolovsky_(As you know, I work on many things, and don't have enough time right now to pay to opie)
18:10.58psokolovsky_That's why I ask you to think well what route youw nat to take -
18:10.59goxboxliveok
18:11.40psokolovsky_I don't want to lead you into something you didn't really want, nor want to work on something which won't help opie as a whole ;-)
18:12.57*** join/#htc-linux BabelOued (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net)
18:14.26cr2psokolovsky_: what _real_ problems do we have with opie now ?
18:15.23psokolovsky_cr2, "There's no distro which supports contemporary OPIE."
18:15.24goxboxliveYou right. Well i dont know what's best to do. For now, there are only thoose two issues i know about. And both of them are solved. I think we shall remove getkey form opie, and cgange the opie start to tty3.
18:16.04psokolovsky_goxboxlive, I'm glad about your decision regarding getkey
18:16.07goxboxliveAnd i have just asked koen about angstrom support of Openmoko, and they will support it as long as it's not dead as Opie.
18:16.34psokolovsky_ok
18:16.49cr2what distro support do we need/expect ?
18:17.01BabelOuedhi everybody
18:18.14cr2making sure that opie works with standard linux keyboard is an opie internal problem, not distro-specific.
18:18.53psokolovsky_cr2, In my view, there should be distro which would support OPIE 1.2.2 in such way taht it is usable after install, and for as much devices as possible (and the key to that would be supporting different devices consistently and uniformly)
18:19.42cr2ok, but isn't it more a problem of the kernel interface ?
18:19.56psokolovsky_cr2, at this time, you may have hard time knowing what OPIE-specific problems exist at all, as you can't get arbitrary device and install QAed release of OPIE 1.2.2 on it
18:20.33psokolovsky_cr2, yeah, good catch ;-) exactly, what should be done on kernel level, should be done there, not on userspace level ;-)
18:20.33cr2ok. how many devices do we have in active development ?
18:21.34psokolovsky_that's essense of my sly plan - drop all the gory crap out of qte, libopie2 and force kernel maintainers of individual devices to their homework. Bwa-ha-ha!!! ;-)
18:21.51psokolovsky_cr2, we can count 10 easily
18:22.25cr2it seems to me that full hx4700+universal support will cover all possible PDA/phone options
18:22.43cr2i have a feeling that it's more close to 5.
18:23.05cr2really different systems, that need attention.
18:23.13psokolovsky_cr2, if you want to call it that way - "hx4700+universal". I'd call it "normal PDA support + extended phone features"
18:23.38cr2i count all htc pxa phones as 1 device.
18:23.41cr2agreed.
18:23.46psokolovsky_cr2, well, *all* PDAs are just the same. so, 1 system ;-P. phone stuff is extra, not difference.
18:24.12cr2hx4700 and universal as a pda are mostly exact clones.
18:24.58cr2it makes some difference if you have pxa or s3c24xx.
18:25.02cr2or omap.
18:25.03psokolovsky_Any PDA has LCD, backlight, CPU with need for suspend/freq ctrl, buttons, memory card slots.
18:25.13psokolovsky_Some PDAs have BT, WiFi, kbd, etc.
18:25.24psokolovsky_- any PDA will fit that description
18:25.57psokolovsky_and differences between 2 different kbd's would rather be handled on kernel level as mush as possible.
18:26.07cr2yes, but the cpu is a main "building block".
18:26.14cr2yes.
18:26.23psokolovsky_cr2, CPU diff is also on kernel level, right? ;-)
18:26.30cr2yes.
18:26.33cr2:)
18:26.56cr2but if you have /sys/class/pxafb it makes a difference.
18:27.40psokolovsky_cr2, don't rely on pxafb, rely on /sys/class/lcd/*/... ;-)
18:27.47cr2yes.
18:27.52psokolovsky_unless we talk about hw accel, but that's another matter
18:28.12cr2it's great which works you have done unifying all asic3-dependent devices.
18:28.15psokolovsky_it's also like "some PDAs have hw accel for X, but all that handled consistently"
18:28.35psokolovsky_cr2, we all do that, and there's even more to do ;-)
18:28.37cr2very little current pdas have hw accel
18:28.45cr2true.
18:29.03psokolovsky_but yes, the picture as described is what I have in mind as the aim ;-). a bit distant, but worthy, imho
18:29.42cr2agreed.
18:31.09*** join/#htc-linux rob_w (n=bob@p85.212.187.248.tisdip.tiscali.de)
18:32.08*** join/#htc-linux cr2 (n=konversa@crpl22.physik.uni-wuppertal.de)
19:30.06BabelOuedlkcl_: are you here ?
19:30.30BabelOuedba doesn't boot with latest kernel :( black screen
19:35.04*** join/#htc-linux Fossi (n=Fossi@e176126097.adsl.alicedsl.de)
19:39.30*** join/#htc-linux asylumed (n=insanity@196.211.28.91)
19:44.26BabelOuedlkcl_: it is problem with latest w100fb patch :(
20:03.13goxboxlivecr2: When i am using gpe and hit the suspend icon it suspends. It also resume in to GPE again.
20:10.10*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
20:29.04cr2goxboxlive: ok. it's obviuosly the second annoying opie bug.
20:32.21goxboxlive:-)
20:46.36*** join/#htc-linux ellisway (n=ellis@host-87-74-241-174.bulldogdsl.com)
20:59.34*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.231)
21:07.04*** join/#htc-linux RoEn_PC (n=roen@p54A66A2E.dip.t-dialin.net)
21:11.14psokolovsky_BabelOued, did you try that it's exactly latets patch to w100fb? If so, please report that to kernel-dicuss@.
21:17.00BabelOuedpsokolovsky_: it is revision 1.29 "Add Manuel Tiera's patch"
21:17.13psokolovsky_BabelOued, please report.
21:17.25BabelOuedmaybe it need some new initialisation, i m looking at
21:17.46psokolovsky_ok, fixing it would be indeed better ;-)
21:18.01psokolovsky_I asume Matt tested it on hx4700 before committing...
21:18.52BabelOuedpsokolovsky_: ok so i look at hx4700 to see if there is new initialisation to add into blueangel
21:32.05*** join/#htc-linux WizMaui_ (n=WizMaui@62.112.90.231)
21:54.27*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
21:59.37goxboxliveohh no, my universal just died.wtf
22:02.55goxboxlivehmm it waked up, strange. I have allmost 80% battery. The powerled turned red and it was all dead, beside when i removed the usb cable the red led shut off. But when i plugged the cable again it turned red.
22:03.30goxboxlivewell, it's working now, powerled are again orange
22:15.30*** join/#htc-linux BabelOued_ (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net)
22:54.59*** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk)
23:11.17*** join/#htc-linux florian (n=fuchs@87.193.38.108)
23:42.04*** join/#htc-linux awelux (n=awelux@lvps87-230-8-217.dedicated.hosteurope.de)
23:45.35*** join/#htc-linux awelux (n=awelux@lvps87-230-8-217.dedicated.hosteurope.de)
23:52.18*** join/#htc-linux awelux (n=awelux@lvps87-230-8-217.dedicated.hosteurope.de)

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.