IRC log for #htc-linux on 20110730

00:55.43*** join/#htc-linux D3tul3 (~oliver@pool-96-234-129-124.bltmmd.east.verizon.net)
01:02.56*** join/#htc-linux Segnale007 (~Segnale00@ppp-5-5.26-151.libero.it)
01:03.57*** join/#htc-linux ORi| (~ORi@91.181.110.238)
01:28.32*** join/#htc-linux arrrghhh (~arrrghhh@unaffiliated/arrrghhh)
01:42.16*** join/#htc-linux surge (surge@pool-98-118-157-221.bflony.fios.verizon.net)
01:43.06*** join/#htc-linux worldfuture (~worldfutu@58.100.251.243)
02:15.08*** join/#htc-linux ElFinLazz (~elfinlazz@112.154.189.103)
02:16.36*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
02:17.03*** join/#htc-linux Archtivity (~Archtivit@std93-4-82-229-216-127.fbx.proxad.net)
02:58.51*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
03:00.07*** join/#htc-linux arrrghhh (~arrrghhh@unaffiliated/arrrghhh)
03:33.22*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
03:44.08*** join/#htc-linux Rob2223 (~Miranda@p4FFF0BD0.dip.t-dialin.net)
04:41.29*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
05:04.09*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
05:13.49*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
05:26.19*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
05:27.05*** join/#htc-linux Regulator (~duffman@unaffiliated/regulator)
06:04.59*** join/#htc-linux rajkosto (~rajkosto@cable-188-2-156-181.dynamic.sbb.rs)
07:02.00*** join/#htc-linux dobrin (~dobrin@85.91.150.26)
07:05.17*** join/#htc-linux rob_w (~bob@ppp-88-217-90-18.dynamic.mnet-online.de)
07:14.20*** join/#htc-linux surgex (surge@pool-98-118-157-221.bflony.fios.verizon.net)
07:16.53*** join/#htc-linux balans (~server@82-170-217-205.ip.telfort.nl)
07:51.01*** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk)
07:57.15*** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star)
08:40.14*** join/#htc-linux rzk_ (rzk@95-25-142-231.broadband.corbina.ru)
08:51.22*** join/#htc-linux paulk (~paulk@lib33-1-82-233-88-171.fbx.proxad.net)
10:10.53*** join/#htc-linux GNUtoo|oeee (~GNUtoo@host186-56-dynamic.180-80-r.retail.telecomitalia.it)
10:13.23*** join/#htc-linux worldfuture (~worldfutu@58.100.253.68)
10:44.39*** join/#htc-linux Segnale007 (~Segnale00@ppp-5-5.26-151.libero.it)
10:44.41*** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star)
11:06.09*** join/#htc-linux fakker (~noobhands@cpc13-hitc6-2-0-cust129.9-2.cable.virginmedia.com)
11:07.50*** join/#htc-linux balans (~server@82-170-217-205.ip.telfort.nl)
11:51.48*** join/#htc-linux Dave888 (~Dave888@195.211.86.94)
11:52.02*** part/#htc-linux Dave888 (~Dave888@195.211.86.94)
11:54.56*** join/#htc-linux gauner1986 (~Miranda@ip-109-91-117-51.unitymediagroup.de)
12:09.10*** join/#htc-linux crabman (~bas@f151079.upc-f.chello.nl)
12:19.59*** join/#htc-linux crabman (~bas@f151079.upc-f.chello.nl)
12:39.43*** join/#htc-linux WyrM (~WyrM@unaffiliated/wyrm)
12:43.51*** join/#htc-linux gauner1986 (~Miranda@ip-109-91-117-51.unitymediagroup.de)
13:19.56*** join/#htc-linux GNUtoo|laptop (~gnutoo@ABordeaux-152-1-26-80.w83-193.abo.wanadoo.fr)
13:25.06*** join/#htc-linux Nokser (b2243818@gateway/web/freenode/ip.178.36.56.24)
13:31.36*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
13:31.36*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
14:18.37*** join/#htc-linux avinashhm (~avinash-h@192.94.92.11)
14:23.42*** join/#htc-linux rob_w_ (~bob@ppp-88-217-90-18.dynamic.mnet-online.de)
14:45.43*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
15:33.38*** join/#htc-linux rob_w_ (~bob@ppp-88-217-90-18.dynamic.mnet-online.de)
15:42.39*** join/#htc-linux Archtivity (~Archtivit@std93-4-82-229-216-127.fbx.proxad.net)
15:52.37*** join/#htc-linux newb (47e60dc9@gateway/web/freenode/ip.71.230.13.201)
15:52.56newbhi all, i was wondering if i could install android on the htc arrive
15:59.21*** join/#htc-linux Curious_ (8bb30d49@gateway/web/freenode/ip.139.179.13.73)
15:59.40*** join/#htc-linux Segnale007 (~Segnale00@ppp-5-5.26-151.libero.it)
16:32.15*** join/#htc-linux arrrghhh (~arrrghhh@unaffiliated/arrrghhh)
16:33.03*** join/#htc-linux ali1234 (~ajbuxton@robotfuzz.co.uk)
16:41.01*** join/#htc-linux Markinus (~Adium@212.255.30.48)
16:46.58*** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@94.52.236.39)
16:56.02*** join/#htc-linux Regulator (~duffman@unaffiliated/regulator)
17:16.29*** join/#htc-linux nick (3c316680@gateway/web/freenode/ip.60.49.102.128)
17:19.27*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
17:33.36*** join/#htc-linux gauner19861 (~Miranda@ip-109-91-117-51.unitymediagroup.de)
17:47.23*** join/#htc-linux toer (~tore@179.81-166-86.customer.lyse.net)
17:55.09*** join/#htc-linux o3 (~o3@201.22.181.98.dynamic.adsl.gvt.net.br)
18:00.06o3just a quick 'misc' question: what makes a spl (appsbl/hboot) compatible/not compatible with some kernels? except for setting up basic hw stuff and jumping to kernel code (which should work with every kernel), what more?
18:01.11phhonly thing i can think of is mtype
18:02.17o3machine type?
18:02.58phhyeah
18:03.36*** join/#htc-linux toer (~tore@179.81-166-86.customer.lyse.net)
18:05.44o3hmmm nice, i thought there were some extra "magic bits" on it
18:06.35phhi doubt that's the only thing though
18:06.37phhit would sound really weird
18:06.42phhoh wait.
18:06.47phhthere could be signature stuff too
18:10.35o3ah I see. I saw some customs kernels for sapphire where the author said "compatible with SPLs x,y,z. will be adding support for others versions"
18:10.59o3that left me wondering what else would be involved
18:11.41o3in case the spl won't check for any signature stuff at all, they are pretty much the same then?
18:13.29*** join/#htc-linux paulk (~paulk@lib33-1-82-233-88-171.fbx.proxad.net)
18:16.23phhspl doesn't include amss right ?
18:17.16o3no
18:17.50phhi seriously can't see what could change
18:17.50o3it does not
18:19.04o3ah ok, its probably mtype & signing then
18:19.09o3about amss stuf..
18:19.37phhamss is a lot more complicated.
18:19.41phhit can break mostly everywhere :p
18:20.07phhlike if amss' behaviour change on something, since the linux kernel is working closely with it
18:20.17phhor just RPC versions
18:20.29o3ah
18:20.39o3yep, got a question on that :)
18:22.44o3is there differences between rpc (implemented with proc_comm, right?) versions for a device with WinCE or a Android one?
18:23.33o3I mean, a device with WinCE, the RPC exposed by the AMSS is totally different from an AMSS running on a android device?
18:24.05o3since the AMSS is mostly coded by Qcom
18:34.18tmztrpc is similar but the pre-rpc stuff is totally different
18:34.33tmztamss may be written by qualcomm but they design the interface to what the oem wants
18:35.10tmztand I think the oem (google for the g1 with htc's help) has the ability to add interfaces to it as well
18:35.23tmztmight even be able to build dev versions (like on halibut)
18:35.54o3i see
18:36.01tmztmtype has ntohing to do with signing
18:36.09tmztmtype is an arm linux thing
18:36.45tmztunless by spl you are referring to tinboot or some of the other firmware for booting android on ce devices
18:36.49tmztwhich hardcode mtype
18:36.57tmztbut that has nothing to do with HTC SPL
18:37.27o3what i meant was htc spls
18:37.51o3besides the mtype and signing stuff, what else would be involved
18:38.01o3it seems nothing else :)
18:38.11o3and regarding the amss
18:38.23tmztwho said they had to be compatible, where did you see that?
18:39.15tmzt14:00 < o3> just a quick 'misc' question: what makes a spl (appsbl/hboot) compatible/not compatible with some  kernels? except for setting up basic hw stuff and jumping to kernel code (which should work with every  kernel), what more?
18:39.25tmzthmm, what do you mean by hboot?
18:39.34tmztwe mostly use that term relating to android
18:39.39o3yep
18:39.56tmztwhat device?
18:39.56o3hboot is the qcom's appsbl, right?
18:40.11tmztpretty much, but it's modified for android
18:40.21tmztand I think some android devices use a different bootloader
18:40.23tmztbut it's not clear
18:40.30tmzt(engboot)
18:41.21o3then, they are both "the bootloader which runs on ARM11 to bootstrap the main OS, which is loaded by OEMSBL", right?
18:41.58o3actually, the device i'm talking about is not a phone
18:42.03o3but is based on msm7201a
18:42.07o3and runs BREW
18:42.11tmztdev board?
18:42.16o3a game console
18:42.19tmztyou are trying to port android to it?
18:42.23o3yep
18:42.27tmztnice!
18:42.33o3:)
18:42.44o3you see, i pretty much booted an linux kernel on it
18:43.02tmztandroid's kernel has it's own format, boot.img
18:43.11tmztit has a header that is read by the spl/hboot
18:43.24o3ah
18:43.39tmztthat's probably what they mean
18:44.10tmztif you look in android.git.kernel.org you'll find tools for working with that format
18:44.30o3ok
18:44.45tmztwe have another approach, tinboot, that creates somethign that can be chainloaded from the spl
18:44.56tmztbut it's designed to be compatible with ce's xip format
18:45.05tmztI assume brew uses elf boot images?
18:45.55o3pretty much, the main executable on APPS partition, which should be the BREW itself, is actually an ELF
18:46.10o3but that really doesn't mind
18:46.17o3I can replace the APPSBL with anything
18:46.31tmztright
18:46.44tmztwhat kind of display does this device have?
18:46.46o3i've created a little bootloader to setup basic stuff and jump to kernel
18:46.54o3yep, that's a problem: none
18:46.59o3it features just a TV out
18:47.01o3:/
18:47.06tmztwe would love to replace the spl on ce devices someday
18:47.13tmztright, mddi based?
18:47.31tmzt(actually replacing hboot on android devices would be cool too)
18:47.56tmztthere's a lot of stupid reinitialization we have had to do because of spl's
18:48.04tmztrather than letting linux do it right
18:48.22o3hmm, i don't think so. wouldn't mddi be used just as a high-speed interface? as long as I know, it's all done using internal MSM's TV ENC, which is output to PMIC's TV DAC.
18:48.29tmztthere's a project doing that on HD2(leo) but it's not open so I've never seend the code
18:48.37tmztoh, ok
18:48.45*** join/#htc-linux biker (~bike@ti0122a340-dhcp0033.bb.online.no)
18:48.47tmztso it's a yuv encoder?
18:48.50o3ah, on my device, none bootloader is signed, i can change anything :D
18:48.56o3yep
18:49.03tmztis this device only in br? haven't heard of it
18:49.07*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-164-23.netcologne.de)
18:49.13o3hehe
18:49.20o3its pretty much a "dark" console
18:49.31tmztlike for hotels?
18:49.33o3it has been released on Brazil and Mexico
18:50.02tmzthttp://www.manufacturing.net/News-New-Game-Console-Uses-Qualcomm-Technology-032409.aspx
18:50.03o3no, its a game console which connects to a 3G network to download its games
18:50.25o3that one :)
18:50.50o3well, it actually dead, the main company discontinued the product here
18:51.42tmzta snapdragon version would be nice
18:51.50o3yeah!
18:52.28o3so, basically, i've been working on it for a while, and want to port android to it
18:53.05o3i need a new appsbl to replace BREWs one, which i can write a new or use one from android project
18:53.20o3and try to talk to its AMSS via RPC
18:53.41tmztwhat's happening when you boot?
18:53.48tmztdo you have serial console or any other output?
18:54.01o3yeah, serial and JTAG
18:54.09o3but there is nothing on serial port
18:54.22tmztwell you need to make you're bootloader do that first
18:54.24o3i'm using it for linux porting, but nothing from the original system itself
18:54.29tmztI don't think you need rpc calls
18:55.02tmzthttp://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/tinboot.git;a=summary
18:55.18o3really? i mean, for now, i've been setting up some clocks inside my own bootloader, since I can't ask amss to do that (no rpc)
18:55.58tmztwell the clocks might not be rpc, they might be proc_comm
18:56.10o3yep, proc_comm,sry
18:56.12o3:)
18:56.34tmztwell we have proc_comm for ce devices which are probably more similar to brew than android is
18:57.11tmztlook for linux on qualcomm msm on gitorious, but i can't say if that's the latest
18:57.34o3really? that's what I'm looking for. i'm bored to reverse its amss to document the proc_comm variant :(
18:57.57o3i've tried every supported amss version from that kernel, none works :/
18:57.59tmztours is really simple
18:58.06tmztfrom what kernel?
18:58.35o3oh no, wait. i've been using the one from codeaurora
18:58.51tmztoh, yeah
18:58.54tmztthat won't work :)
18:59.00o3lol
18:59.05tmztuse htc-linux kernel
18:59.19tmztat least figure out if the proc_comm works and get serial
18:59.36tmztbut you can do proc_comm yourself in the bootloader and setup serial output
19:00.00tmztyou see openzeebo.org ?
19:00.05o3yeah
19:00.17o3i'm the founder ;)
19:00.24tmztso it's has jtag?
19:00.28o3yep
19:00.37tmztamazing, we could have used this years ago
19:00.53tmztmaybe have booted ce amss on it
19:00.57o3amazing indeed, i can step code nicely :)
19:01.50o3as a first shot, i tried running homebrew stuff on it
19:01.56o3inside brew
19:02.12tmztwhat debugger are you using?
19:02.26tmztwell, step brew enough to get the proc_comm figured out
19:02.28o3eclipse connected to openocd gdb server
19:02.32tmztand add it to our 2.6.29 kernel :)
19:02.57o3yep, i'm bored to do that, that's why I've searching for something compatible hahaha
19:03.11o3but yeah, will do that
19:03.58o3first, I need to get rid of my hacky bl, i'll fork tinboot and have a look at it
19:04.34tmztwe'd really like to get uboot or something like that working on htc devices
19:04.42tmztI guess android devices now
19:05.00o3but every bootloader is signed, right?
19:05.17tmztnot with hardspl
19:05.42o3ah ok, but what about oemsbl/qcsbl?
19:07.03tmzthey, it's cdma based right?
19:07.17tmztis there anyway to disable the radio completely?
19:07.33o32g/3g
19:07.53tmzto3: the hardspl method means we can modify those on most devices
19:08.02tmztcdma not gsm
19:08.23tmztI found one for 50, I might get it but I don't want it trying to connect to verizon or anything
19:08.58o3well, pretty much, when I'm researching, I always put the AMSS in a endless loop lol. no need for the radio for the game functions
19:09.07o3ah, you mean the console?
19:09.33tmztyeeah
19:10.01o3a friend of mine on the US brought one. i told him to swap it's internal SIM card and change the APN config
19:10.06o3it worked !
19:10.12tmztoh so it's gsm
19:10.15tmztokay
19:10.18o3yeah, GSM
19:10.29tmztwhat carrier is it in br?
19:10.35o3Claro
19:10.49o3i'm using mine with TIM, since Claro sucks :P
19:11.49tmztokay
19:11.51tmztcool
19:12.18o3if you ever buy one
19:12.25o3it would be nice, join our team ;D
19:13.00o3hehe
19:13.04tmztI'm just playing with this stuff now
19:13.10tmztI've got an android phone that I can live with :)
19:13.17tmzt(g2 desire z)
19:13.31o3yep, i got one myself too on may, loving it!
19:14.01tmztprobably the best handset HTC has made
19:14.06tmztat least qwerty
19:14.15tmzthave to replace the screen though
19:14.30tmzthope you get zeebo working with linux
19:14.32o3oww :/
19:14.48o3ah yep, thanks
19:14.51o3long road ahead
19:15.16o3but since i'm able to boot a vanilla kernel already, that's a nice progress i guess
19:15.46tmzthow do you know it's booting?
19:15.49tmztjtag?
19:15.54o3serial
19:16.01tmztyou have serial output?
19:16.05o3yeah
19:16.14tmztoh okay, I thought you were still working on that
19:16.29tmztos what you really need is a framebuffer driver that supports tv out
19:16.42o3yeah, i've been worried about that :/
19:16.47tmztwe have the start of one of those, and a samsung 7201 kernel we found has one
19:16.54o3the tv drivers are on staging for now
19:16.57o3really?
19:17.04tmztyeah
19:17.11tmztyou'll have to search the logs
19:17.21tmztit has a very different msm_fb (there's a bunch of them floating around)
19:17.34tmztalso, we have something called htc_fb_console which is an earlyfb that blits the mddi
19:17.43tmztit could probably be modified to active the tv output instead
19:17.47tmztto give you a place to start
19:17.56o3hmmm nice
19:18.01tmztand cr2 was kind of our expert on tvout
19:18.07tmztbut he hasn't been around lately
19:18.09tmzt~seen cr2
19:18.14aptcr2 <n=cr2@ip-109-84-74-80.web.vodafone.de> was last seen on IRC in channel #htc-linux, 553d 22h 57m 21s ago, saying: 'MrPippy: where is this source ?'.
19:18.21tmztouch
19:18.23o3wow
19:18.31o3hah
19:18.32*** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk)
19:18.38tmztGlemSom: hey
19:19.08tmztyou worked on bootloaders didn't you?
19:19.37GlemSomtmzt, If something is broken.. Then, NO I DID NOT DO IT!!
19:19.38GlemSom;)
19:19.42GlemSomheh
19:19.54GlemSomHonestly, No - I did not work with bootloaders..
19:20.00tmztwhat was it?
19:20.05tmztI forget
19:20.54*** join/#htc-linux surgex (surge@pool-98-118-157-221.bflony.fios.verizon.net)
19:25.26*** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@94.52.236.39)
19:27.47*** join/#htc-linux dekar_ (~dekar@drms-590cf10c.pool.mediaWays.net)
19:37.07o3proc_comm_wince.c :)
19:38.33tmztyep
19:40.11o3i guess it won't be very different
19:40.46o3i did some quick comparison between my amss and one from sapphire
19:40.59o3they seem to be compatible to some extent
19:41.40o3i mean, if i remember well, they both stores the proc_comm version (i think it is) in the same offset inside smem
19:42.06o3so, yeah, hope it's not too much work lol
19:42.45o3too much arm asm these last months, i want some rest hehe
19:43.23o3is the bootloaders, amss from this device of any use to you guys? i mean, for research purposes?
19:43.34o3i guess no, but.. :)
19:47.35WyrMo3: bootloader for which device?
19:48.21o3zeebo game console
19:49.04tmztWyrM: hey, somebody was asking about adding sdhc/sd2.0 support to genblob
19:49.23tmztcan't remember who but it would have been in #openezx
19:49.24WyrMtmzt: Hi.
19:50.03WyrMshouldn't be hard to do.
19:57.49WyrMo3: looks like a fun device to hack. :)
19:58.19WyrMi also live in Brasil, but have never seen one.
19:58.46o3wow
19:58.48tmztare you ntsc?
19:58.55tmzt50/60 ?
19:58.57o3really? :)
19:59.02o3pal-m
19:59.04tmztoh
19:59.12tmztthat might be an issue for me
19:59.24o3but you can change tv out control register and switch to ntsc ;D
20:00.47tmztright
20:00.59o3well, with jtag, that is
20:01.04tmztdoes it have svideo or just composite?
20:01.10*** join/#htc-linux Segnale007 (~Segnale00@ppp-5-5.26-151.libero.it)
20:01.13o3composite only
20:01.24tmztthat should be easy enough to fix
20:01.29tmztI'm sure y/c is in there somewhere
20:02.04o3you mean extract the signal directly from board?
20:02.53o3WyrM: interested in giving it a go? :)
20:04.13WyrMI don't have the hardware, so i don't know if i can help much.
20:05.04WyrMo3: are you trying to port android to it?
20:05.10WyrMor mainline linux?
20:06.01o3well, i really was thinking about that, but by porting android, i think it would be more user friendly
20:06.30o3and, i guess there is no full 3d acceleration + gl libs when dealing with mainline linux
20:07.03o3(i may be wrong)
20:07.28tmztyou mgiht be able to get an android 3d driver working
20:07.32o3at least with android we got those, from actual phones
20:07.44tmztunfortunately they aren't compatible with normal linux linkers
20:07.58o3yeah, that's one of the reasons to pick android instead of vanilla linux
20:08.47o3since it's a game console, no 3d is quite a no-no
20:09.07tmztif you are using it as a game console
20:09.10tmztwhat is the controller like
20:09.29o3its a simple usb one
20:09.41o3hid, standard stuff
20:10.03o3it also comes with a keyboard, for browsing
20:10.11o3to help on*
20:10.16tmztso plugging in bluetooth would be easy
20:10.31o3yes
20:10.41o3it has 3 usb host ports
20:10.56tmztI might just save up and get a samsung tv though
20:10.59o3and 1 slave, that is mapped to qcom diag, nmea, modem
20:11.03tmztI can do the same stuff
20:11.06o3hehe
20:11.09o3yep
20:11.15tmztport X even :)
20:11.19tmztjust because I want to
20:11.26o3that would be cool
20:12.05o3the console itself is not that great. i played on it like, 2 times? lol
20:12.30tmztget fb working :)
20:12.32o3i got it just for tinkering
20:12.51o3i will lol
20:13.05o3hopefully
20:13.15tmztstart with htc_fb_console
20:13.24tmztit's a bit simpler than msmfb
20:13.42o3ok
20:13.43tmztsearch the logs for the samsung kernel, probably for the original galaxy
20:13.49o3i7500?
20:13.52tmztyeah
20:14.10o3yep, googling for it!
20:14.24o3then, i need to "glue" it with tv_enc
20:15.57tmztyeah
20:23.40WyrMtmzt: about the samsung tv, buy a sony bravia and help us instead. ;) http://sourceforge.net/apps/mediawiki/openbravia/index.php?title=Main_Page
20:24.16tmzthmm
20:24.29tmztI'm just glad there's more than one project
20:24.37tmztbut I'm looking for one with an open (or reversable) dsp
20:25.34tmztirc?
20:27.02WyrMno irc channel yet. just starting the project.
20:27.11tmztI like sony's panels
20:27.19tmztI just wonder if they'll get drm for scea
20:27.28WyrMwe have console access, but there is no shell running in it.
20:27.30tmztfrom
20:28.12tmztserial is on the remote port?
20:28.38WyrMDebug connector with 3 serial ports.
20:30.21WyrMemma3tl2 seems quite impressive: http://www2.renesas.com/digital_av/en/mpegdec_tv/emma3tl2.html
20:32.48tmzthmm, I thought samsung switched to arm on the newer models, I guess sony is still mips?
20:34.19WyrMsome newer  sonys use arm processors.
20:34.25WyrMso i guess they switched too.
20:34.42WyrMthe google tv also has a emma3.
20:36.58tmztbut that might be beside atom
20:37.02tmzton google tv
20:37.03tmztor not
20:38.17WyrMyes, the google/android part is an atom. The tv part is an emma3. :)
20:39.57tmztright
20:40.07tmztI wonder how they interface those, maybe hdmi internally
21:01.23*** join/#htc-linux HQRaja (Eureka@unaffiliated/hqraja)
21:01.54*** join/#htc-linux biker (~bike@ti0122a340-dhcp0033.bb.online.no)
21:26.00*** join/#htc-linux bikerer (~bike@ti0122a340-dhcp0033.bb.online.no)
21:55.58*** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star)
22:01.37*** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star)
22:08.51*** join/#htc-linux GNUtoo|htcdream (~GNUtoo@90.84.144.140)
22:30.58*** part/#htc-linux HQRaja (Eureka@unaffiliated/hqraja)
22:31.34*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
22:58.36*** join/#htc-linux BHSPitLappy (~BHSPitLap@unaffiliated/bhspitmonkey)

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