Messages in this thread | | | From | Mike Waychison <> | Date | Fri, 7 Jan 2011 17:34:00 -0800 | Subject | Google firmware drivers in staging? |
| |
Hi Greg, Linus,
I'm going through our core dependencies for changes to the kernel that we use in house. FWIW, these "core" dependencies are essentially required for our userland stack to function properly in our cluster environment. My goal is to make it seamless for other Google engineers to use otherwise mainline kernels on our machines, enabling them to develop more of their code against mainline.
Anyhow, rummaging down the list of stuff that we consider "core", I've come across a couple firmware specific drivers. These drivers are specific to our machines, and would likely never apply to anyone else's hardware. That said, they aren't very complicated (they are mostly isolated) and generally just help us plumb information between userland and the firmware itself (like system event log data).
I'd like to get rid of these drivers as a delta between mainline and our in-house trees. Note that I can't really change anything on the firmware side as those ABIs are sorta written in stone for all intents and purposes, but I'd be happy to adapt the userland-exposed sides of the drivers if needed.
I'd like to release these guys publicly if there is any hope that they can wind up in the official tree. What are your thoughts on putting them through the staging tree?
Mike Waychison
| |