[jira] [Resolved] (MYNEWT-82) The current RF interrupt priority is not the highest priority interrupt on the ble controller
[ https://issues.apache.org/jira/browse/MYNEWT-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William San Filippo resolved MYNEWT-82. --- Resolution: Not A Problem Looks like I did actually set the RF priority to priority zero and that all other priorities are assigned a lesser priority. > The current RF interrupt priority is not the highest priority interrupt on > the ble controller > - > > Key: MYNEWT-82 > URL: https://issues.apache.org/jira/browse/MYNEWT-82 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Affects Versions: v0_8_0_beta1 >Reporter: William San Filippo >Assignee: William San Filippo >Priority: Critical > Fix For: v0_8_0_beta1 > > > The current code does not assign the highest priority interrupt to the RF. > The RF interrupt needs to be the highest priority for the controller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-29) Fixup License Headers
[ https://issues.apache.org/jira/browse/MYNEWT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145620#comment-15145620 ] Justin Mclean commented on MYNEWT-29: - Some files in the newt and larval repos are missing headers and/or in a few cases have double headers. There also a LGPL (YAML) dependancy [1] in the newt repo that needs to be dealt with in some way. 1. ./newt/Godeps/_workspace/src/gopkg.in/yaml.v2 > Fixup License Headers > - > > Key: MYNEWT-29 > URL: https://issues.apache.org/jira/browse/MYNEWT-29 > Project: Mynewt > Issue Type: Task >Reporter: Sterling Hughes >Assignee: Justin Mclean > Fix For: v0_8_0_beta1 > > > - Rename license headers from Runtime to ASF license headers > - Remove ASF license headers from 3rd party files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MYNEWT-23) Newt should generate a build manifest file
[ https://issues.apache.org/jira/browse/MYNEWT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila resolved MYNEWT-23. -- Resolution: Fixed > Newt should generate a build manifest file > -- > > Key: MYNEWT-23 > URL: https://issues.apache.org/jira/browse/MYNEWT-23 > Project: Mynewt > Issue Type: New Feature > Components: Newt >Reporter: Sterling Hughes >Assignee: Marko Kiiskila > Fix For: v0_8_0_beta2 > > > The manifest file should contain information about the build: > - Date and time of build > - Packages compiled into the build (e.g. os@v0.8.9) > - Target definition of the build > - SHA-256 of build & manifest parameters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-26) Revise Image Management Scheme
[ https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila updated MYNEWT-26: - Description: We need the following in our image management and bootloader scheme: - Image should contain a SHA-256 in it that uniquely identifies the image - Bootloader should support verifying the SHA-256 and the signature of the image. was: We need the following in our image management and bootloader scheme: - Image header should have a SHA-256 in it that uniquely identifies the image - That SHA-256 must be signed by a device private key in order to boot. By default newt shall use the Apache Mynewt Development public/private key. This is in no way secure, but will keep the process uniform across devices, so when people add security, they don't have to change bootloader or image formats. - Bootloader should support verifying the SHA-256 and the signature of the image. > Revise Image Management Scheme > -- > > Key: MYNEWT-26 > URL: https://issues.apache.org/jira/browse/MYNEWT-26 > Project: Mynewt > Issue Type: New Feature > Components: Image Mgmt >Reporter: Sterling Hughes >Assignee: Marko Kiiskila > Fix For: v0_8_0_beta2 > > > We need the following in our image management and bootloader scheme: > - Image should contain a SHA-256 in it that uniquely identifies the image > - Bootloader should support verifying the SHA-256 and the signature of the > image. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-29) Fixup License Headers
[ https://issues.apache.org/jira/browse/MYNEWT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145623#comment-15145623 ] Justin Mclean commented on MYNEWT-29: - Interestingly enough it's based on http://pyyaml.org/wiki/LibYAML which is MIT licensed. > Fixup License Headers > - > > Key: MYNEWT-29 > URL: https://issues.apache.org/jira/browse/MYNEWT-29 > Project: Mynewt > Issue Type: Task >Reporter: Sterling Hughes >Assignee: Justin Mclean > Fix For: v0_8_0_beta1 > > > - Rename license headers from Runtime to ASF license headers > - Remove ASF license headers from 3rd party files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-26) Revise Image Management Scheme
[ https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila updated MYNEWT-26: - Due Date: 16/Feb/16 > Revise Image Management Scheme > -- > > Key: MYNEWT-26 > URL: https://issues.apache.org/jira/browse/MYNEWT-26 > Project: Mynewt > Issue Type: New Feature > Components: Image Mgmt >Reporter: Sterling Hughes >Assignee: Marko Kiiskila > Fix For: v0_8_0_beta2 > > > We need the following in our image management and bootloader scheme: > - Image header should have a SHA-256 in it that uniquely identifies the image > - That SHA-256 must be signed by a device private key in order to boot. By > default newt shall use the Apache Mynewt Development public/private key. > This is in no way secure, but will keep the process uniform across devices, > so when people add security, they don't have to change bootloader or image > formats. > - Bootloader should support verifying the SHA-256 and the signature of the > image. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MYNEWT-64) BLE Host - HCI callback thread-safety
[ https://issues.apache.org/jira/browse/MYNEWT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-64. --- Resolution: Fixed This is implemented via two changes: * Add a ble_hci_sched mutex that gets locked whenever the list of HCI tx slots is read or modified. * Add a handle per HCI tx slot. This allows client code to cancel an HCI transmission before the tx callback is rendered unusable. > BLE Host - HCI callback thread-safety > - > > Key: MYNEWT-64 > URL: https://issues.apache.org/jira/browse/MYNEWT-64 > Project: Mynewt > Issue Type: Bug > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v0_8_0_beta2 > > > When the host schedules an outgoing HCI command, it configures a callback > which does the actual command formation. Some events can occur before the > callback is executed which render the callback invalid (e.g., connection > terminated). > The fix is to ensure the appropriate resources are protected from deletion > while an HCI command is scheduled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
