Donald,
kala mazoo wrote:
> Greets,
> I've spent the last too many hours trying to recreate
> exactly what I'd done on the 32bit machine, on this box - an
> AMD/x2 64bit unit. The software instance installed is a
> 'pure_64bit' type with no 32bit compat at all. The board is
> using
Michael,
I have discovered that both sprom_extract_r123() in the ssb driver,
and ssb-sprom use a two-byte quantity to extract the board revision.
In the specifications detailed in
http://bcm-v4.sipsolutions.net/SPROM, a single-byte is used for this
parameter.
It is unlikely that this causes a
Michael,
This version modifies the setting of the patch to ssb_sprom to handle
systems with multiple SSB-based devices.
Larry
---
Index: ssb_sprom/README
===
--- ssb_sprom.orig/README
+++ ssb_sprom/README
@@ -13,3 +13,106 @@ Require
Greets,
I've spent the last too many hours trying to recreate
exactly what I'd done on the 32bit machine, on this box - an
AMD/x2 64bit unit. The software instance installed is a
'pure_64bit' type with no 32bit compat at all. The board is
using the nvidia CK804 chipset.
Forgetting
On Thu, 2008-04-24 at 21:48 +0200, Richard Jonsson wrote:
> Hello,
>
> First some background:
> I am currently running latest mainline from git. This kernel suffers
> from a scheduler?
I think this question is more suited for LKML.
> While trying to find what these hickups come from I ran watch
Hello,
First some background:
I am currently running latest mainline from git. This kernel suffers
from a scheduler? issue where keys get stuck and audio skips every now
and then. Confirmed to be triggered by a commit named "sched: fix fair
sleepers".
I am currently on wired lan and have the w
This adds a workaround for invalid bluetooth SPROM settings
on ASUS PCI cards.
This will stop the microcode from poking with the BT GPIO line.
This fixes data transmission on this device, as the BT GPIO line
is used for something TX related on this device
(probably the power amplifier or the radio)
This adds more workarounds for devices with broken BT bits.
This patch is in wireless-testing.git, commit
4b43b16f74b362d4d2ce7df5b761eb838dfd5d32
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
Index: linux-2.6.25/drivers/net/wireless/b43/main.c
==
From: Larry Finger <[EMAIL PROTECTED]>
In the SSB SPROM a field set to all ones means the value
is not defined in the SPROM.
In case of the boardflags, we need to set them to zero
to avoid confusing drivers. Drivers will only check the
flags by ANDing.
This patch is in wireless-testing.git, commi
Some mainboards/CPUs don't allow DMA masks bigger than a certain limit.
Some VIA crap^h^h^h^hdevices have an upper limit of 0x. So in this
case a 64-bit b43 device would always fail to acquire the mask.
Implement a workaround to fallback to lower DMA mask, as we can always
also support a lo
10 matches
Mail list logo