netdev - Re: [PATCH][BNX2X] round three

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: <20071015.124205.98881309.davem@davemloft.net>
Date:	Mon, 15 Oct 2007 12:42:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eliezert@...adcom.com
Cc:	andi@...stfloor.org, netdev@...r.kernel.org, jeff@...zik.org,
	mchan@...adcom.com
Subject: Re: [PATCH][BNX2X] round three

From: "Eliezer Tamir" <eliezert@...adcom.com>
Date: Mon, 15 Oct 2007 18:22:03 +0200

> On Mon, 2007-10-15 at 18:05 +0200, Andi Kleen wrote:
> > > This is not a driver issue.
> > > Unfortunately, the firmware code is different for LE and BE machines.
> > > We had issues with the BE firmware that appear to be resolved.
> > > Hopefully, the next version will have both.
> > 
> > If the firmware is big it might be better to just add the necessary
> > conversions to the driver and always use BE. Endian conversions
> > tend to be very cheap.
> 
> For a given architecture, only the right version of the microcode is
> compiled, so the binary only contains one copy of the microcode.

But it still takes up source tree space.

> The good news is that future versions of the device will not have this
> issue.
> 

The better news is that you only need the little-endian firmware
even with these chips, simple assume little-endian for all
chip shared data-structures and swap in the driver as we've
explained to you.

The cost for big-endian cpus is almost nothing.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html