lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 30 Jul 2014 12:55:19 +0000
From:	David Hendel <david@...icom.co.il>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	Anna Lukin <annal@...icom.co.il>
Subject: FW: ethtool patch to support bypass / fail-to-wire function

Dear Sir/Madam,

Per the below,
We have our bypass driver updated and we would like to move forward with integrating it into the kernel.
We think it need to be under drivers/net/

The description is per the below, taken from readme in linux.
The patch is attached,
Let me know how we can proceed with that. what should be the next step.

-------------
Theory of Operation:

The Silicom Bypass Network Interface Cards (NICs) are network cards with paired ports (2 or 4).
The pairs either act as a "wire" allowing the network packets to pass or insert the device in
between the two ports.  When paired with the on-board hardware watchdog or other failsafe,
they provide high availability for the network in the face of software outages or maintenance.

The software requirements are for a kernel level driver that interfaces with the bypass and watchdog,
as well as for control software. User control can be either the provided standalone executable
(/bin/bpctl) or the API exposed by the Silicom library.  
----------------------

Regards, David


-----Original Message-----
From: Stephen Hemminger [mailto:stephen@...workplumber.org] 
Sent: Wednesday, June 11, 2014 9:36 PM
To: David Hendel
Cc: netdev@...r.kernel.org; Elad Blatt
Subject: Re: ethtool patch to support bypass / fail-to-wire function

On Wed, 11 Jun 2014 16:55:27 +0000
David Hendel <david@...icom.co.il> wrote:

> Stephen,
> OK, so what should be the next step? How do we move forward with that?
> 
> Regards, David
> 
> 
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@...workplumber.org] 
> Sent: Wednesday, June 11, 2014 7:18 PM
> To: David Hendel
> Cc: netdev@...r.kernel.org; Elad Blatt
> Subject: Re: ethtool patch to support bypass / fail-to-wire function
> 
> The driver using this is not upstream. You need to get that driver reviewed and incorporated in upstream kernel before the changes to ethtool will be considered.
> 
> I expect that the driver will not be accepted as is, and therefore you will have to make changes (including API changes), that render this ethtool API moot.
> 
> 

Read kernel/Documentation/SubmittingPatches

Download attachment "linux-3.16-rc6_silbp.patch" of type "application/octet-stream" (624904 bytes)

Powered by blists - more mailing lists