All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Interesting 14e4:4321
Date: Sat, 7 May 2011 00:14:43 +0200	[thread overview]
Message-ID: <BANLkTi=5C5VaJ0rJhJu50PLyP0ssjmozrw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikoDzeujFhBYOeH4_1_d7X0B4pjBw@mail.gmail.com>

W dniu 6 maja 2011 23:56 u?ytkownik Jonas Gorski
<jonas.gorski@gmail.com> napisa?:
> 2011/5/6 Hauke Mehrtens <hauke@hauke-m.de>:
>> On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
>>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>>> rare and interesting so I wanted to post all info about it :)
>
> I didn't know BCM4321s identifying as 14e4:4321 are that seldom - the
> mini-PCI card in my D-Link DSL-2741B (which is a BCM6358) also does
> that.

Well, maybe they are well-known in OpeWRT community :) I believe we
didn't have any reporters here. Unfortunately OpenWRT guys don't
report their problems, fixes too often.


>>> Unfortunately this is one another BCM4321 with DMA not working. I
>>> really need to focus on this after fixing LP-PHY and adding BCMA.
>
> Same here, dma is a no go (I have to use pio).
>
>> The SPROM is not stored on the pci card but in the nvram on the flash
>> chip of the device. This is now correctly read out in OpenWrt and we
>> will send some patches to mainline soon. [1] [2]
>
> Same for the one in my BCM6358 - perhaps SPROM-less devices default to
> their chip-id as the PCI device id (just wildly guessing)? I also have
> a second BCM6358 with a BCM4322; same there (no SPROM, DMA doesn't
> work, and it identifies as 14e4:4322).

Ouch, I didn't know DMA errors also happen for BCM4322. My 14e4:432b
one was working fine. Maybe this is Mini PCI vs. Mini PCIe? Do you
know if your cards are PCI or PCIe?

-- 
Rafa?

  reply	other threads:[~2011-05-06 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 20:40 Interesting 14e4:4321 Rafał Miłecki
2011-05-06 21:28 ` Larry Finger
2011-05-06 21:48   ` Rafał Miłecki
2011-05-06 22:25     ` Larry Finger
2011-05-06 21:36 ` Hauke Mehrtens
2011-05-06 21:51   ` Rafał Miłecki
     [not found]     ` <479014597.20110507002540@googlemail.com>
     [not found]       ` <BANLkTi=n6gjDxGX0buUamNQAydPCMqEpjg@mail.gmail.com>
     [not found]         ` <274308290.20110507111432@googlemail.com>
2011-05-07  9:41           ` Rafał Miłecki
2011-05-06 21:56   ` Jonas Gorski
2011-05-06 22:14     ` Rafał Miłecki [this message]
2011-05-06 22:32       ` Jonas Gorski
2011-05-07 15:17       ` Michael Büsch

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='BANLkTi=5C5VaJ0rJhJu50PLyP0ssjmozrw@mail.gmail.com' \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.