I know this is a moldy old topic, but I am also curious.
There have been developments on opening up chromebooks, even though they have some very non-standard hardware inside them.
Take for instance, the support for full bios replacements on many models, via coreboot (and the maintained easy install scripts
and precompiled coreboot images
thanks to MrChromebox
). This completely converts a chromebook into a minimally powered (and provisioned) sub-notebook with some slightly non-standard hardware inside, capable of running windows, linux, and in some cases, OSX.
There are various communities on Reddit and the like that offer how-to documents, driver download mirrors, etc-- for various chromebook models.
The keyboard and mouse will almost certainly not work with ReactOS, since the hardware is connected to either the I2C or SPI bus on these systems, and not to something more x86 standard, like PS/2 controller, or USB port. However, there are suitable drivers for windows, so with a little loving, perhaps ReactOS could one day support those drivers. (I doubt that there has been much work on implementing the needed hooks the drivers need, since there is not really a compelling reason to devote those resources at this time, when there is much more important stuff to do.) That might be fixed due to the updates MrChromebox has rolled in on some models his maintained images support, as he has rolled in updates to the embedded microcontroller (the thing that the keyboard, mouse, and pals are actually connected to) so that it emulates a PS/2 controller to the host operating system on supported models (even though a real PS/2 controller does not actually exist.) It might allow these systems to work with reactOS immediately, then again, it might not.
I have a "legacy boot enabled" chromebook (Celes) that I could attempt to boot the liveCD on via USB (no native optical disk, but the legacy boot package I installed via MrChromebox's handy script does support optical boot via USB) but the chromebook lacks a hardware serial port, and so any diagnostic data that might be of interest to developers cannot be easily retained. I suppose network based debugging might be possible assuming reactoOS works well enough to enable the integrated wifi chip and connect to an access point... but I doubt it. I think I have a USB to Serial cable floating around someplace, but I would need two of them to collect logging data that way. (One for the chromebook and one for the system I am collecting logs with.) There is a planned full UEFI replacement package that MrChromebox is currently testing that supports my model, which might give me better results.
The unit I own also lacks anything even resembling a SATA controller, and instead uses eMMC based storage. That might also complicate matters as far as what the liveCD expects to find.
Targeting chromebooks would be an interesting proposition, as they are hardware well suited to ReactOS's core goals (Low power, low space consumption, low memory needs), but they are very nonstandard/proprietary hardware. On the other hand, the hardware out there is fairly consistent, as there are few models in the wild.
Has anyone already tried to do this?