linux-kernel - Re: CrystalHD driver safe on big endian systems?

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] [day] [month] [year] [list]

Message-Id: <p06240805c7cc98bdf217@[192.168.9.6]>
Date:	Sun, 21 Mar 2010 23:53:15 -0400
From:	"Scott D. Davilla" <davilla@....com>
To:	Leon Woestenberg <leon.woestenberg@...il.com>
Cc:	jarod@...sonet.com,
	"Naren (Narendra) Sankar" <nsankar@...adcom.com>,
	"hancockrwd@...il.com" <hancockrwd@...il.com>,
	"jarod@...hat.com" <jarod@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"abraham.manu@...il.com" <abraham.manu@...il.com>
Subject: Re: CrystalHD driver safe on big endian systems?

>has the CrystalHD driver/library been tested on big endian systems?
>
>The (staging GIT tree) driver sources seem to use bitfields in C, is
>this safe under different endianess?
>
>I'm currently testing two BCM70012 modules on a big-endian PowerPC
>system and it fails changing the clock PLL to 175 MHz. This could be a
>pair of defective modules, or the wrong bits being modified.
>Unfortunately, I do not have a little endian system with mini-PCIe
>available to do a A-B check.

Not sure if anyone has done work testing under big endian platforms. 
 From what I've seen in code, it looks definite little endian based 
and would need a look over regarding byte swap.

Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/