On 11/18/2009 08:54 AM, Peter Stuge wrote:
Oncaphillis wrote:
So as far as I understand both the early kernel as well as lspci
think that the mmio area of the Broadcom chip is located at
5710 only ssb gets the wrong address. It gets set in ssbioremap
via pci_iomap.
After the
On Wed, Nov 18, 2009 at 6:15 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 11/18/2009 08:34 AM, Oncaphillis wrote:
The first ioread16 actually succeeds, only the second one fails.
My lspci -vnn tells me that the memory is:
Memory at 5710 (64-bit, non-prefetchable) [size=16K]
On 11/18/2009 06:15 PM, Larry Finger wrote:
On 11/18/2009 08:34 AM, Oncaphillis wrote:
The first ioread16 actually succeeds, only the second one fails.
My lspci -vnn tells me that the memory is:
Memory at 5710 (64-bit, non-prefetchable) [size=16K]
Could it be that one has to make a
On Wednesday 18 November 2009 18:36:12 Oncaphillis wrote:
Index: wireless-testing/drivers/ssb/pci.c
===
--- wireless-testing.orig/drivers/ssb/pci.c
+++ wireless-testing/drivers/ssb/pci.c
@@ -251,10 +251,16 @@ static int
On 11/18/2009 11:36 AM, Oncaphillis wrote:
I already tried something similar. Unfortunately I can not report in detail
right now since I've once again killed my kernel and my acer stands at
home.
I'll give more details in a couple of hours -- but the punch line is:
(1) if I transform the
Enforce all device constraints on the descriptor memory region.
There are several constraints on the descriptor memory, as documented
in the specification. The current code does not enforce them and/or
incorrectly enforces them.
Those constraints are:
- The address limitations on 30/32bit
On 11/18/2009 01:53 PM, Michael Buesch wrote:
Enforce all device constraints on the descriptor memory region.
There are several constraints on the descriptor memory, as documented
in the specification. The current code does not enforce them and/or
incorrectly enforces them.
Those
On 11/18/2009 06:51 PM, Larry Finger wrote:
After you get access to the machine, please try my patch. It has been tested
here. The first few lines from the output are:
ssb: Entering sprom_do_read
ssb: Read 0x2801 from SPROM
ssb: Read 0x103C137C from SPROM
ssb: Read 0x6DBE0078 from SPROM
On Wednesday 18 November 2009 23:07:29 Oncaphillis wrote:
On 11/18/2009 06:51 PM, Larry Finger wrote:
After you get access to the machine, please try my patch. It has been tested
here. The first few lines from the output are:
ssb: Entering sprom_do_read
ssb: Read 0x2801 from SPROM
On Wednesday 18 November 2009 23:53:42 Michael Buesch wrote:
On Wednesday 18 November 2009 23:07:29 Oncaphillis wrote:
On 11/18/2009 06:51 PM, Larry Finger wrote:
After you get access to the machine, please try my patch. It has been
tested
here. The first few lines from the output
Please keep it on-list. This is really important to get this debugged properly.
On Thursday 19 November 2009 00:23:18 Oncaphillis wrote:
On 11/18/2009 11:59 PM, Michael Buesch wrote:
What kind of device is that? Some laptop? I only knew about embedded
devices
using these wireless cards
On Thu, Nov 19, 2009 at 12:39 AM, Michael Buesch m...@bu3sch.de wrote:
Please keep it on-list. This is really important to get this debugged
properly.
On Thursday 19 November 2009 00:23:18 Oncaphillis wrote:
On 11/18/2009 11:59 PM, Michael Buesch wrote:
What kind of device is that? Some
On 11/18/2009 05:57 PM, Gábor Stefanik wrote:
Hmm... this kinda reminds me of when the SPROM died on my Asus 4318,
causing it to display as a 14e4:0008, and freeze immediately upon
any SPROM read/write attempt. Quite possibly we have something similar
here (there is an SPROM, but it's broken -
Is it this device?
http://hax0rpedia.com/index.php/Disassembeling_the_AAO_D250
Can you open the lower-right cover shown here:
http://hax0rpedia.com/index.php/File:Aao_d250_step2.jpg
and take a closeup picture of the wireless card?
Also probably a picture of the backside of the card.
On Thursday 19 November 2009 01:26:41 Oncaphillis wrote:
Is it this device?
http://hax0rpedia.com/index.php/Disassembeling_the_AAO_D250
Can you open the lower-right cover shown here:
http://hax0rpedia.com/index.php/File:Aao_d250_step2.jpg
and take a closeup picture of the wireless
Michael Buesch wrote:
Hmm, surprise surprise. The slot is empty. They seem to have moved
it onto the motherborad.
Whoa, sick man. :)
So I think there's a fair chance that there's no sprom at all, if
the device is on-board.
One idea is to look up the FCC ID of the laptop in the FCC
16 matches
Mail list logo
