This message is being posted from Haiku on my Chromebook c202s. Probably the first person on Earth to post such a thing using the native keyboard and trackpad.
This chromebook has several show stoppers with respect to using it in any capacity. The first is the touchpad. I needed to enable the C202S's intel I2C controller, and wired the existing Elan I2C touchpad driver to the i2c controler, and playued with the clickpad/report handling enough for basic movement, clicks, and gestures.
The second is the keyboard. I started down a cros_ec route because I was led to believe you needed the microcontroller to work to successfully read the keyboard, but during development of that driver, it became clear we were on the wrong track. The keyboard was actually exposed through the legacy ps2 path, so we fixed the haiku ps2 driver to poll for input when it appears there's keys ready to be delivered but irq1 isn't being delivered consistently.
I believe both the keyboard and touchpad fixes can be easily upstreamed, I'll look more at that later.
The next steps are the emmc support (I'm running off a small usb stick at the moment), and sound support (which is turning out to be really tough because linux drivers and haiku drivers are way different)
In my view, haiku is ideal for this little chromebook (though the chromebook may not be ideal for haiku!) because it has limited memory and limited storage, so a 500MB OS that lives comfortably on a 16GB stick.
Next step is emmc support, which seems to just be a little extension of the existing emmc/sdmmc code, plumbing the quriky chromebook stuff into the existing work. That's been where the most bang for my buck has come from, and that's why the sound has been such a challenge -- You definitely can't just port linux drivers over easily.
This chromebook has several show stoppers with respect to using it in any capacity. The first is the touchpad. I needed to enable the C202S's intel I2C controller, and wired the existing Elan I2C touchpad driver to the i2c controler, and playued with the clickpad/report handling enough for basic movement, clicks, and gestures.
The second is the keyboard. I started down a cros_ec route because I was led to believe you needed the microcontroller to work to successfully read the keyboard, but during development of that driver, it became clear we were on the wrong track. The keyboard was actually exposed through the legacy ps2 path, so we fixed the haiku ps2 driver to poll for input when it appears there's keys ready to be delivered but irq1 isn't being delivered consistently.
I believe both the keyboard and touchpad fixes can be easily upstreamed, I'll look more at that later.
The next steps are the emmc support (I'm running off a small usb stick at the moment), and sound support (which is turning out to be really tough because linux drivers and haiku drivers are way different)
In my view, haiku is ideal for this little chromebook (though the chromebook may not be ideal for haiku!) because it has limited memory and limited storage, so a 500MB OS that lives comfortably on a 16GB stick.
Next step is emmc support, which seems to just be a little extension of the existing emmc/sdmmc code, plumbing the quriky chromebook stuff into the existing work. That's been where the most bang for my buck has come from, and that's why the sound has been such a challenge -- You definitely can't just port linux drivers over easily.
- replies
- 0
- announces
- 0
- likes
- 2