From: "Scott D. Davilla" <davilla@4pi.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: jarod@wilsonet.com,
"Naren (Narendra) Sankar" <nsankar@broadcom.com>,
"hancockrwd@gmail.com" <hancockrwd@gmail.com>,
"jarod@redhat.com" <jarod@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"abraham.manu@gmail.com" <abraham.manu@gmail.com>
Subject: Re: CrystalHD driver safe on big endian systems?
Date: Sun, 21 Mar 2010 23:53:15 -0400 [thread overview]
Message-ID: <p06240805c7cc98bdf217@[192.168.9.6]> (raw)
In-Reply-To: <c384c5ea1003211403t494bd794hece06d8b8cfcb54@mail.gmail.com>
>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
next prev parent reply other threads:[~2010-03-22 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 21:03 Leon Woestenberg
2010-03-22 3:53 ` Scott D. Davilla [this message]
[not found] ` <p06240805c7cc98bdf217@192.168.9.6>
2010-03-22 11:32 ` Leon Woestenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='p06240805c7cc98bdf217@[192.168.9.6]' \
--to=davilla@4pi.com \
--cc=abraham.manu@gmail.com \
--cc=hancockrwd@gmail.com \
--cc=jarod@redhat.com \
--cc=jarod@wilsonet.com \
--cc=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsankar@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®