> > > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie <airlied at gmail.com> > > > > > wrote: > > > > > > can you guys ask someone internally about it also, there is a > > > > > > driver somewhere in Google also for driving the LVDS->HDMI > > > > > > adapter but I'm not sure what i2c bus its hanging off. > > > > > > > > > > > > Dave. > > > > > > > > > > > > > > > http://git.chromium.org/gitweb/?p=chrontel.git;a=tree > > > > > > > > > > may or may not be the thing. > > > > > > > > > > Dave. > > > > I'll see if it works... > > > Is there a public clone URI for that repo? I dont want to have to > > > download the full ChromiumOS... > > Okay, I guessed it right: http://git.chromium.org/git/chrontel.git > Simply running the resulting executables didn't work, it fails to detect > the chip, the code also references accesses through GPIO and seems it > wants an nm10_gpio driver which isn't in my kernel tree. My board is an > NM10 chipset system, as is the target "Cr48 Chrome Notebook" so it could > well be the same hardware.
I cherry-picked the nm10_gpio driver from the ChromeOS kernel, but while it worked fine the chrontel driver still couldn't detect the chip: XAUTHORITY=//home/mythtv/.Xauthority ./ch7036_monitor -v -p ./ch7036_monitor: starts Found device ID 0xff ./ch7036_monitor: Fatal: Device ID 0xff not the expected 0x56 So either it isn't a ch7036 or I'm still not doing everything necessary to expose it.
