Searched hist:f62601b8 (Results 1 – 4 of 4) sorted by relevance
| /openbmc/hiomapd/ |
| H A D | transport.h | f62601b8 Wed Oct 31 22:14:25 CDT 2018 Andrew Jeffery <andrew@aj.id.au> transport: Fix event handling
Events were not quite being handled as per the intent of the recent
refactor: The protocol layer was meant to record the raw set of events
and provide the protocol-version-specific mask to the transport layer,
which the transport layer would then use to flush out the state in
accordance with its implementation-specific requirements.
What was going wrong was that the transport implementations were
overwriting the raw set of events with the protocol-specific masked set
of events, meaning that we'd lose the raw state and provide an
incomplete BMC state value on protocol upgrade.
Rework the event handling to make sure the responsibilities are properly
split between the layers.
Change-Id: Iace6615a121e4ce7dcca690d9adf62e5ab9ccee2
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
| H A D | transport_dbus.c | f62601b8 Wed Oct 31 22:14:25 CDT 2018 Andrew Jeffery <andrew@aj.id.au> transport: Fix event handling
Events were not quite being handled as per the intent of the recent
refactor: The protocol layer was meant to record the raw set of events
and provide the protocol-version-specific mask to the transport layer,
which the transport layer would then use to flush out the state in
accordance with its implementation-specific requirements.
What was going wrong was that the transport implementations were
overwriting the raw set of events with the protocol-specific masked set
of events, meaning that we'd lose the raw state and provide an
incomplete BMC state value on protocol upgrade.
Rework the event handling to make sure the responsibilities are properly
split between the layers.
Change-Id: Iace6615a121e4ce7dcca690d9adf62e5ab9ccee2
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
| H A D | transport_mbox.c | f62601b8 Wed Oct 31 22:14:25 CDT 2018 Andrew Jeffery <andrew@aj.id.au> transport: Fix event handling
Events were not quite being handled as per the intent of the recent
refactor: The protocol layer was meant to record the raw set of events
and provide the protocol-version-specific mask to the transport layer,
which the transport layer would then use to flush out the state in
accordance with its implementation-specific requirements.
What was going wrong was that the transport implementations were
overwriting the raw set of events with the protocol-specific masked set
of events, meaning that we'd lose the raw state and provide an
incomplete BMC state value on protocol upgrade.
Rework the event handling to make sure the responsibilities are properly
split between the layers.
Change-Id: Iace6615a121e4ce7dcca690d9adf62e5ab9ccee2
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
| H A D | protocol.c | f62601b8 Wed Oct 31 22:14:25 CDT 2018 Andrew Jeffery <andrew@aj.id.au> transport: Fix event handling
Events were not quite being handled as per the intent of the recent
refactor: The protocol layer was meant to record the raw set of events
and provide the protocol-version-specific mask to the transport layer,
which the transport layer would then use to flush out the state in
accordance with its implementation-specific requirements.
What was going wrong was that the transport implementations were
overwriting the raw set of events with the protocol-specific masked set
of events, meaning that we'd lose the raw state and provide an
incomplete BMC state value on protocol upgrade.
Rework the event handling to make sure the responsibilities are properly
split between the layers.
Change-Id: Iace6615a121e4ce7dcca690d9adf62e5ab9ccee2
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|