summaryrefslogtreecommitdiffstats
path: root/mboxd_flash.c
Commit message (Collapse)AuthorAgeFilesLines
* mboxd_flash: strerror() requires errno for argumentAndrew Jeffery2017-04-261-2/+2
| | | | | Change-Id: I68381ed74ab8b75dac195b53d61fd8ccabcf6fb1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* mboxd_flash: Initialise flash size if necessaryAndrew Jeffery2017-04-261-0/+25
| | | | | Change-Id: I0587088f72df0664e03977c704da042314580f8a Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* mboxd_flash: Fix infinite loop on EOFAndrew Jeffery2017-04-261-4/+6
| | | | | Change-Id: If3684d8c386dd41ce7f7a40353e55267e13d5b07 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* mboxd: Update mboxd to implement protocol V2 and add dbus supportSuraj Jitindar Singh2017-04-111-0/+278
Version 2 of the mbox protocol contains a few changes such as: - All sizes are in block size - Adds an erase command - Adds new response codes - Adds new BMC events - Open windows commands now take a size directive Update the mailbox daemon to support version 2 of the protocol which includes implementing all of the V2 functionality. Also entirely refactor the mboxd.c code to make it more modular improving readability and maintainability. At the same time improve the functionality by adding: - Multiple windows in the daemon (still only one active window) to cache flash contents - Implement a dbus interface to allow interaction with the daemon - Handle sigterm and sigint and terminate cleanly The previous implementation utilised the entire reserved memory region. Update the daemon so that on the command line the number of windows and the size of each which the reserved memory region will be split into can be specified. The reserved memory region is then divided between the windows, however there can still only be one "active" window at a time. The daemon uses these windows to cache the flash contents meaning the flash doesn't have to be copied when the host requests access assuming the daemon already has a copy. A dbus interface is added so that commands can be sent to the daemon to control it's operation from the bmc. These include suspending and resuming the daemon to synchronise flash access, telling the daemon to point the lpc mapping back to flash and telling the daemon when the flash has been modified out from under it. Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com> Change-Id: I10be01a395c2bec437cf2c825fdd144580b60dbc
OpenPOWER on IntegriCloud