<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>chromeos | Blue Duck Valley Rd</title><link>https://juju.nz/michaelh/categories/chromeos/</link><atom:link href="https://juju.nz/michaelh/categories/chromeos/index.xml" rel="self" type="application/rss+xml"/><description>chromeos</description><generator>Source Themes Academic (https://sourcethemes.com/academic/)</generator><language>en-us</language><copyright>© 2017-2025 Michael Hope</copyright><lastBuildDate>Tue, 17 Dec 2013 21:09:09 +0000</lastBuildDate><image><url>img/map[gravatar:%!s(bool=false) shape:circle]</url><title>chromeos</title><link>https://juju.nz/michaelh/categories/chromeos/</link></image><item><title>FTDI serial adapters and Chrome OS</title><link>https://juju.nz/michaelh/2013/12/ftdi-serial-adapters-and-chrome-os/</link><pubDate>Tue, 17 Dec 2013 21:09:09 +0000</pubDate><guid>https://juju.nz/michaelh/2013/12/ftdi-serial-adapters-and-chrome-os/</guid><description>&lt;p>Looks like I’ve run into my first problem: FTDI based USB to serial adapters don’t work as they seem to be automatically disconnected shortly after plug in. I suspect that it’s udev running the brltty rules, not finding a assistive device, and aborting.&lt;/p>
&lt;p>The udev scripts are under &lt;code>/lib/udev/rules.d&lt;/code> but I can’t hack it as the rootfs is read only. Let’s see what
&lt;a href="https://code.google.com/p/chromium/issues/detail?id=323282" target="_blank" rel="noopener">the devs think.&lt;/a>.&lt;/p></description></item></channel></rss>