diff options
| author | Paul Sokolovsky <pmiscml@gmail.com> | 2007-02-12 18:32:28 +0000 |
|---|---|---|
| committer | Paul Sokolovsky <pmiscml@gmail.com> | 2007-02-12 18:32:28 +0000 |
| commit | 761bfdca711fcfd38a1be2f15119ec3a6a0d63ee (patch) | |
| tree | eec59e0cb51478a18b3512bfd4d2e8e4dd02b56d /packages/bluez/bluez-utils.inc | |
| parent | 4f2ab4a21f451bace3a029be94419489b17cf15d (diff) | |
bluez-utils 3.9: Add patch to handle EINTR while being attached to uart properly.
* EINTR is not really an error, but a Unix (mis)feature, and requires special
handling (i.e. retrying). Bluez authors/maintainers really should do a bit of trivial
Unix programming reading before wring BT stacks.
* Specifically EINTR happens when resuming from suspend. So, with this patch
(and assuming there're no weird APM scripts), configured BT finally survives
suspend/resume (tested on h4000). Hurrah!
Diffstat (limited to 'packages/bluez/bluez-utils.inc')
| -rw-r--r-- | packages/bluez/bluez-utils.inc | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/packages/bluez/bluez-utils.inc b/packages/bluez/bluez-utils.inc index 912c419f8c..21cbea1b70 100644 --- a/packages/bluez/bluez-utils.inc +++ b/packages/bluez/bluez-utils.inc @@ -11,7 +11,8 @@ LICENSE = "GPL" SRC_URI = "http://bluez.sourceforge.net/download/bluez-utils-${PV}.tar.gz \ file://hcid.conf \ file://02dtl1_cs.sh \ - file://hciattach-ti-bts.patch;patch=1" + file://hciattach-ti-bts.patch;patch=1 \ + file://handle-eintr.patch;patch=1" # Almost all serial CF cards w/ manfid 0x0000,0x0000 seem to use the bcs protocol # Let's default to that instead of 'any' until further notice... |