<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/include/uapi/linux, branch dev-4.3</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.3</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.3'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2016-01-27T05:33:14+00:00</updated>
<entry>
<title>Merge tag 'v4.3.4' into dev-4.3</title>
<updated>2016-01-27T05:33:14+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2016-01-27T05:33:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=7495d280c7566dba7211b4704e71d0ce35069762'/>
<id>urn:sha1:7495d280c7566dba7211b4704e71d0ce35069762</id>
<content type='text'>
This is the 4.3.4 stable release
</content>
</entry>
<entry>
<title>uapi: export ila.h</title>
<updated>2016-01-23T04:55:47+00:00</updated>
<author>
<name>stephen hemminger</name>
<email>stephen@networkplumber.org</email>
</author>
<published>2015-12-10T17:14:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=6894e903583693f53cd41128f56e57150199f35b'/>
<id>urn:sha1:6894e903583693f53cd41128f56e57150199f35b</id>
<content type='text'>
[ Upstream commit f7fc6bc414121954c45c5f18b70e2a8717d0d5b4 ]

The file ila.h used for lightweight tunnels is being used by iproute2
but is not exported yet.

Signed-off-by: Stephen Hemminger &lt;stephen@networkplumber.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net/ncsi: Netlink support</title>
<updated>2015-11-18T04:14:19+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2015-10-06T02:52:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=073081106f8c4390e13243e1fad35aed1a5dfb7e'/>
<id>urn:sha1:073081106f8c4390e13243e1fad35aed1a5dfb7e</id>
<content type='text'>
This adds netlink support so that userland can retrieve the NCSI
topology on the specified interface. Also, more netlink commands
are introduced to retrieve information from the active channel
or configure the active channel with provided options.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>net/ncsi: Packet handler</title>
<updated>2015-11-18T04:14:18+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2015-10-06T02:52:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cf0e64286f9c0f6e3a6be18e7c646d0738bb61b8'/>
<id>urn:sha1:cf0e64286f9c0f6e3a6be18e7c646d0738bb61b8</id>
<content type='text'>
NCSI packet encapsulated in ethernet frame is recognized by the
ethernet protocol field (0x88F8). According to NCSI spec, the
destination MAC field should be 0xFF's, but the source MAC field
could be arbitrary one since channel field in NCSI header indicates
the source of the packet.

There are 3 types of packets depending on the type field in the NCSI
packet header: command, response, Asynchronous Event Notification
(AEN). The command packets are sent from NCSI enabled interace to
the NCSI package or channel for purpose of information retrival or
configuration. The response packets, as responses to the received
command packets, originate from NCSI package or channel and terminate
at NCSI enabled interface. AEN packets are sent from NCSI channel
for asynchronous events that might indicate failure detected on
the active channel.

This implements the functions to handle NCSI packets.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>net/ncsi: Resource management</title>
<updated>2015-11-18T04:14:17+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2015-10-06T02:52:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1cbc4b6a63eff3fa1a1e38d8f0858e7b1e4c4780'/>
<id>urn:sha1:1cbc4b6a63eff3fa1a1e38d8f0858e7b1e4c4780</id>
<content type='text'>
According to NCSI spec (DSP0222), the NCSI enabled interface can
connected to multiple packages simultaneously, up to 8 packages.
Each package includes multiple channels, up to 32 channels. At
one moment, one channel is enabled to provide service to the NCSI
enabled interface. Besides, each channel comprises capabilities,
modes, filters, version and statistics etc. All of them are
resources to NCSI protocol stack.

At the meanwhile, the NCSI device seen from NIC driver is
represented by "struct ncsi_dev", which is expected to populated
and started by NIC driver before the NIC can work. All possible
NCSI packages and NCSI channels connected to the NCSI interface
are tracked from the NCSI device. Also, the NCSI device recognizes
active channel that is currently providing service to NCSI enabled
interface. Also, the NCSI requests (pairs of command and response)
are embedded in NCSI device.

This introduces the data structs to represents the NCSI resources
mentioned as above. Also, functions used by NCSI stack internally
are implemented. Besides, this introduces kernel config option
CONFIG_NET_NCSI to enable NCSI stack.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>misc/bt-host: Add Aspeed BT IPMI host driver</title>
<updated>2015-11-18T04:13:09+00:00</updated>
<author>
<name>Alistair Popple</name>
<email>alistair@popple.id.au</email>
</author>
<published>2015-10-06T00:19:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c545dd0b35ef4ad860962147ef46aa09c8c9f158'/>
<id>urn:sha1:c545dd0b35ef4ad860962147ef46aa09c8c9f158</id>
<content type='text'>
This patch adds a simple device driver to expose the iBT interface on
Aspeed chips as a character device (/dev/bt).

Plus various fixes from jk:

 - Fix compile warnings. We have a bunch of unused functions.
 - Remove unused members of struct bt_host
 - Fix whitespace issues
 - Use explicit u8 type for bt registers to avoid any issues with
   signed vs unsigned types.
 - Remove chrdev_region, use module_platform_driver
 - Unify device name to bt-host
 - Use a more explicit compatible string. The interface we're using here
   is specific to the aspeed hardware implementation.
 - Use a dynamic miscdev; no need to use a global miscdev here.
 - Avoid global bt_host. Rather than having a global bt_host, use
   references from the file &amp; miscdev. This removes the restriction on
   the number of bt-host devices.
 - Add ioctl to assert SMS_ATN
 - Remove bt_host-&gt;ctrl, nothing uses it.
 - Read bt ctrl state after poll_wait
 - Fix unit address for ibt
 - Add facility for interrupt-driven BT messages. This change adds a
   facility for the bt-host driver to use interrupts rather than polling
   via a timer. If we find an interrupts property in the device tree,
   we'll enable interrupts on the bt device.
 - Use devm_ioremap_resource(). No need to unpack struct resource, and
   we don't need ioremap_uncached here.

Signed-off-by: Alistair Popple &lt;alistair@popple.id.au&gt;
Signed-off-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>openvswitch: Clarify conntrack COMMIT behaviour</title>
<updated>2015-10-22T02:33:38+00:00</updated>
<author>
<name>Joe Stringer</name>
<email>joestringer@nicira.com</email>
</author>
<published>2015-10-20T02:18:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1d008a1df927846788b9dc02e770f65951f98ddc'/>
<id>urn:sha1:1d008a1df927846788b9dc02e770f65951f98ddc</id>
<content type='text'>
The presence of this attribute does not modify the ct_state for the
current packet, only future packets. Make this more clear in the header
definition.

Signed-off-by: Joe Stringer &lt;joestringer@nicira.com&gt;
Acked-by: Thomas Graf &lt;tgraf@suug.ch&gt;
Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>rtnetlink: fix gcc -Wconversion warning</title>
<updated>2015-10-13T02:40:30+00:00</updated>
<author>
<name>Arad, Ronen</name>
<email>ronen.arad@intel.com</email>
</author>
<published>2015-10-09T17:35:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e844463743095bc8b230f507de066d047c87476b'/>
<id>urn:sha1:e844463743095bc8b230f507de066d047c87476b</id>
<content type='text'>
RTA_ALIGNTO is currently define as 4. It has to be 4U to prevent warning
for RTA_ALIGN and RTA_DATA expansions when -Wconversion gcc option is
enabled.
This follows NLMSG_ALIGNTO definition in &lt;include/uapi/linux/netlink.h&gt;.

Signed-off-by: Ronen Arad &lt;ronen.arad@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>openvswitch: Change CT_ATTR_FLAGS to CT_ATTR_COMMIT</title>
<updated>2015-10-07T12:03:06+00:00</updated>
<author>
<name>Joe Stringer</name>
<email>joestringer@nicira.com</email>
</author>
<published>2015-10-06T18:00:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=ab38a7b5a4493a3658d891a8e91f9ffcb3d2defb'/>
<id>urn:sha1:ab38a7b5a4493a3658d891a8e91f9ffcb3d2defb</id>
<content type='text'>
Previously, the CT_ATTR_FLAGS attribute, when nested under the
OVS_ACTION_ATTR_CT, encoded a 32-bit bitmask of flags that modify the
semantics of the ct action. It's more extensible to just represent each
flag as a nested attribute, and this requires no additional error
checking to reject flags that aren't currently supported.

Suggested-by: Ben Pfaff &lt;blp@nicira.com&gt;
Signed-off-by: Joe Stringer &lt;joestringer@nicira.com&gt;
Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>openvswitch: Extend ct_state match field to 32 bits</title>
<updated>2015-10-07T12:03:06+00:00</updated>
<author>
<name>Joe Stringer</name>
<email>joestringer@nicira.com</email>
</author>
<published>2015-10-06T18:00:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=fbccce5965a58d56aaed9e9acd1bec75d8a66e87'/>
<id>urn:sha1:fbccce5965a58d56aaed9e9acd1bec75d8a66e87</id>
<content type='text'>
The ct_state field was initially added as an 8-bit field, however six of
the bits are already being used and use cases are already starting to
appear that may push the limits of this field. This patch extends the
field to 32 bits while retaining the internal representation of 8 bits.
This should cover forward compatibility of the ABI for the foreseeable
future.

This patch also reorders the OVS_CS_F_* bits to be sequential.

Suggested-by: Jarno Rajahalme &lt;jrajahalme@nicira.com&gt;
Signed-off-by: Joe Stringer &lt;joestringer@nicira.com&gt;
Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
