The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/22e30e808183659a209c0bc01a556737f698b463

commit 22e30e808183659a209c0bc01a556737f698b463
Author: David Tseng <dtseng@chromium.org>
Date: Wed Aug 17 22:55:41 2016

Update Brltty to version 5.4.

The upstream Gentoo package is currently on Brltty-5.2, but we require
    Brltty-5.4 to pick up support for a few new braille displays. This
    upgrades us from 4.5.

This cl makes the necessary changes to metadata.xml/manifest and adds a new
    ebuild for 5.4.

Summary of changes to patches against 5.4:
- the following patches were rebased from brltty-4.5-*.patch
  brltty-5.4-tty0-openflags.patch
  brltty-5.4-supress-messages.patch
  brltty-5.4-udev-run-script.patch

- Already committed upstream in brltty-5.4:
  brltty-4.5-remove-umask.patch
  brltty-4.5--updusbdevs.patch
  brltty-4.5-socket-path.patch
  brltty-4.5-fix-mk4build.patch (upstream is slightly different regex, but
      achieves the same case insensitive match).

These two patches are upstream support for specific displays; they do not
    apply cleanly on brltty-5.4, so there were likely changes to these
    displays since the cherrypicks. We should test these displays
    specifically:
  brltty-4.5-handytech.patch

The following patch appears to work around an issue with Seka displays; try not
    applying this patch to re-enable support
  brltty-4.5-udev.patch

BUG= chromium:637952 
TEST=A basic test (output/input, hardware keys) was done for:
- Freedom Scientific Focus Blue 40 (first gen)
- Papenmeier EL80c
- VarioUltra 20

Change-Id: I983a0b04bd06e00d0c66f48d37875cb8d1d7b8d8
Reviewed-on: https://chromium-review.googlesource.com/372318
Commit-Ready: David Tseng <dtseng@chromium.org>
Tested-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-fix-mk4build-cross.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-supress-messages.patch
[modify] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/Manifest
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-remove-umask-calls.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-api-socket-path.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-udev.patch
[rename] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/files/brltty-5.4-tty0-openflags.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/brltty-4.5-r10.ebuild
[add] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/files/brltty-5.4-udev-run-script.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-handytech.patch
[modify] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/brltty.bashrc
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-updusbdevs.patch
[modify] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/metadata.xml
[modify] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/files/brltty.conf
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-udev-run-script.patch
[delete] https://crrev.com/f67eda12f0d545916d5b1935f9b68268b734bb1d/app-accessibility/brltty/files/brltty-4.5-hims.patch
[rename] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/brltty-5.4.ebuild
[add] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/files/brltty-5.4-supress-messages.patch
[rename] https://crrev.com/22e30e808183659a209c0bc01a556737f698b463/app-accessibility/brltty/files/brltty-5.4-fix-ldflags.patch

Which build does this fix land in? I've tried appending chrome/VERSION to the above CLs, but they all return "not found"

This is a Chrome OS change, not a Chrome change, so it's not easy to associate with a Chrome version. It should show up in the next Chrome OS dev channel release.

I've Samus on Canary, so will Baum VarioUltra work via Bluetooth and USB? If so, how to configure it using BLuetooth?
Thanks so much!

We don't support braille through bluetooth. There's a bug for that.

Could you please link to the BLuetooth braille bug? Is it intended to be addressed in ChromeVox Next (phase 3-4)?

Since it's USB-only, will it be possible to connect VU to cvox2, and it "just works"?

Yes

Yes to plug-and-play. With all supported braille displays you just plug it in via USB and it works.

No to Bluetooth support in phase 3 - 4. It's definitely on our radar but not a high priority given limited resources as virtually all displays support USB.

Should a new bug be filed to announce that chromeOS/Vox Next added support for:
Freedom Scientific Focus Blue 40 (first gen)
- Papenmeier EL80c
Baum - VarioUltra 20

Or, is the easier path to update the HC article for Braille on ChromeOS/Vox Next?
https://support.google.com/chromebook/answer/7020014?hl=en&ref_topic=6323347

Wow, THanks David! Baum VarioUltra works gerat with Samus ChromeVox Next:
54.0.2837.0

bulk verified