Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2020-04-30 13:11:39 -0400 #1810

Closed
wants to merge 1,091 commits into from
Closed

Release 2020-04-30 13:11:39 -0400 #1810

wants to merge 1,091 commits into from

Conversation

bradjc
Copy link
Contributor

@bradjc bradjc commented Apr 30, 2020

gkelly and others added 30 commits March 19, 2020 12:42
This test takes a long time to run in the verilator environment. Just
disable it for now.
1708: Create core-notes-2020-03-20 r=alevy a=ppannuto

### Pull Request Overview

Call notes.

### Testing Strategy

N/A

### TODO or Help Wanted

N/A

### Documentation Updated

- [x] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [x] Ran `make formatall`.


Co-authored-by: Pat Pannuto <pat.pannuto@gmail.com>
…ory.

This script is currently unmodified, and will need to be tweaked further
for Tock's use.
1710: Add tock-on-titan's print_memory_usage.py script to the tools/ directory. r=phil-levis a=jrvanwhy

### Pull Request Overview

This pull request adds the tock-on-titan print_memory_usage.py script to tock's tools/ directory. The script is currently unmodified, and I expect it will be further modified to support Tock.


### Testing Strategy

This pull request was tested by...


### TODO or Help Wanted

This pull request still needs...


### Documentation Updated

- [X] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [X] Ran `make formatall`.


Co-authored-by: Johnathan Van Why <jrvanwhy@google.com>
1711: Updates size tool to have fixes requested in #1673 r=alevy a=phil-levis

### Pull Request Overview

This pull request applies the changes under #1673 to a properly licensed version of the size script and closes that branch. It is a separate PR for source licensing reasons: a different version of the original file from tock-on-titan needed to be submitted by @jrvanwhy . This PR applies all of the suggested fixes and changes to the original script in #1673.


### Testing Strategy

This pull request was tested by running it on a generated imix ELF file.


### TODO or Help Wanted


### Documentation Updated

- [x] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [x] Ran `make formatall`.


Co-authored-by: Philip Levis <pal@cs.stanford.edu>
…rengthen the isolation required from UART drivers and similar buses, and clarify that temperature/ADC samples may be shared.
… the threat model contains policies that have not yet been implemented. Remove the use of the word "secrets" from the threat model, as it is not a particularly useful idea and is somewhat confusing.
alistair23 and others added 28 commits April 22, 2020 11:17
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
This reverts commit 958edaa.

It seems empirically that commas are not permitted as characters in ELF section
names (though I'll be damned if I can find that documented anywhere).
This matches what is done in the arch crate.
OpenTitan: README: Update the OpenTitan SHA
rv32i: try a different section identifier
doc: Add syscall filter to syscall documentation
add comments

make debug two lines
Unexpected behavior: Running the process console causes
uart.receive_abort to be called after every character.

Cause: start_receive gets called twice, once with a rx_buffer, and the
second time without since it is being used after the first call. The
first call happens because process console starts a new receive after
handling its current read, and the second call happens because uart mux
calls start_receive on its client's behalf after the callback.

Fix: Remove the mux calling start_receive on its client's behalf.
This fixes the issue where receives issued from callbacks were always
resulting in abort() calls by not replacing the underlying UART receive
buffer until after all of the client callbacks have finished. This
"flag", in conjunction with the `completing_read` bool are what
start_receive uses to determine whether to start or abort a receive.

This also fixes determining the minimum length of a receive by
calculating it in all cases where another receive is needed.
Without this check, the virtual uart will continue issuing reads to
receive rx_len bytes, even if the buffer is not big enough to store
them.
1793: Hifive updates r=ppannuto a=bradjc

### Pull Request Overview

Some updates I found while trying to get hifive1a to work.

- Enable external interrupts (which is how the PLIC is connected).
- Better label LEDs.
- Fix register field name in PWM.


### Testing Strategy

This pull request was tested by running the kernel on a hifive1a board.

It doesn't seem to really work, perhaps because there is a bootloader that runs.


### TODO or Help Wanted




### Documentation Updated

- [x] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [x] Ran `make formatall`.


Co-authored-by: Brad Campbell <bradjc5@gmail.com>
capsules: virtual_uart: avoid double receive, check rx len, support custom buffer
Add core WG talk notes for 2020-04-24.
doc: fix stack/data position on arch diagram
@bradjc bradjc changed the title Preparing release pull request... Release 2020-04-30 13:11:39 -0400 Apr 30, 2020
@bradjc bradjc closed this Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet