public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: b43-dev@lists.infradead.org
Subject: BCM5354 SoC with LP Phy Wifi
Date: Mon, 30 Jan 2012 21:48:22 +0100	[thread overview]
Message-ID: <4F270216.8000309@hauke-m.de> (raw)
In-Reply-To: <CACna6ry+DcJe5o4SPmn1=UuUNsPYFpkhXd4Nhw-HQ+Xn=d5_hQ@mail.gmail.com>

On 01/30/2012 09:37 PM, Rafa? Mi?ecki wrote:
> W dniu 30 stycznia 2012 20:45 u?ytkownik Hauke Mehrtens
> <hauke@hauke-m.de> napisa?:
>> On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
>>> While I'll try to implement/update LP-PHY code, I think it still would
>>> be nice to investigate this problem. Do we have some leak in b43? We
>>> should fix it if so.
>> I haven't found a leak in b43 yet, just one in an OpenWrt switch driver,
>> while searching in b43. ;-)
>> It's nice to hear that you will work on the LP-PHY part, to me it looks
>> like ~30% of the spec is not implemented. have you started implementing
>> the GMAC Ethernet driver?
> 
> I've started fighting with my router. I've tested it's working (on
> original firmware), I'm trying now to get root access to get
> partitions layout. I've already opened it (this required small Torx
> screwdriver) and built 3,3V console. I'm working on creating console
> pins (unfortunately they were removed from production==non-beta
> boards).
I had the same problem with my Netgear device on the pictures made by
the FCC there are nice pins on the board and ASUS just leaves them there
for the production devices, but my Netgear devices did not had them.
The pin layout is probably the same as for the WNR3500L here:
http://wiki.openwrt.org/toh/netgear/wnr3500l

>>> Could you check what exactly happens in b43_dma_tx please?
>> Yes I will look deeper into this.
>> Do you have a working LP-PHY device, so that I could give you some
>> patches and then compare the output?
> 
> My LP-PHY had some performance problems, probably some important
> calibration is missing.

I got ~4MBit/s when running my device in AP mode with old firmware over
~0.5 meters.

Hauke

  reply	other threads:[~2012-01-30 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 22:12 BCM5354 SoC with LP Phy Wifi Hauke Mehrtens
2012-01-29 23:33 ` Hauke Mehrtens
2012-01-30  6:29   ` Rafał Miłecki
2012-01-30 19:45     ` Hauke Mehrtens
2012-01-30 20:37       ` Rafał Miłecki
2012-01-30 20:48         ` Hauke Mehrtens [this message]
     [not found]     ` <CADu8HpLu-CzwOuWLhE5gJSykBGUOqx685wQPK2EQxhANF+aMAQ@mail.gmail.com>
2012-02-03 10:04       ` Rafał Miłecki
2012-02-04 12:53     ` Hauke Mehrtens
2012-02-04 16:40       ` Hauke Mehrtens
     [not found] ` <CACb-4KjixkVS5pe+mucyOaKeHAMb11m=YBZ47STZAiKDwRH2rQ@mail.gmail.com>
2012-01-30 19:37   ` Hauke Mehrtens
2012-01-30 20:39     ` Rafał Miłecki

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=4F270216.8000309@hauke-m.de \
    --to=hauke@hauke-m.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox