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  linux-cve-announce  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]
Message-ID: <20130731200756.GA3737@radagast>
Date:	Wed, 31 Jul 2013 23:07:56 +0300
From:	Felipe Balbi <balbi@...com>
To:	Richard Cochran <richardcochran@...il.com>
CC:	Felipe Balbi <balbi@...com>, Mugunthan V N <mugunthanvnm@...com>,
	<netdev@...r.kernel.org>, <davem@...emloft.net>,
	<linux-omap@...r.kernel.org>
Subject: Re: [net-next PATCH 1/1] drivers: net: cpsw: Add support for new
 CPSW IP version

Hi,

On Wed, Jul 31, 2013 at 10:04:28PM +0200, Richard Cochran wrote:
> On Wed, Jul 31, 2013 at 10:45:23PM +0300, Felipe Balbi wrote:
> > 
> > one more thing, why do you consider a new revision to be an error ?
> 
> Okay, so why don't you go and remove the version checking code
> altogether?

if you need to treak certain aspects of the IP differently, you need the
revision check, don't be so childish.

what I'm saying is that we can give new IP revision a chance to work if
they have no programming model differences (except for, perhaps, new
features and different erratas).

On dwc3 (drivers/usb/dwc3) we support every single revision of the IP.
We only have revision checks to enable (or not) known silicon erratas.

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ