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 20:37:57 +0100	[thread overview]
Message-ID: <4F26F195.9050509@hauke-m.de> (raw)
In-Reply-To: <CACb-4KjixkVS5pe+mucyOaKeHAMb11m=YBZ47STZAiKDwRH2rQ@mail.gmail.com>

Hi William,

On 01/30/2012 04:39 PM, William R Agosto Padilla wrote:
> Mr. Hauke,
> 
> I am new to the reverse engineering process. However I am working on a
> project that
> requires me to use printk statements in the b43 device driver code, so I
> can see how it is
> really working during initialization, resetting, and suspension of the
> networking process. 
> 
> The first problem that I encountered was finding the b43 source code for
> download.
> I was only able to find the assembly code for the b43 firmware. Do you
> know of a specific download
> location where I can get the entire b43's ''C'' source code?
Just go to https://www.kernel.org/ and download the Linux kernel it has
b43 included in it in drivers/net/wireless/b43 or use
http://wireless.kernel.org/en/users/Download/stable/

>  Reading
> your email I realized that you
> have already done what I will be attempting to do. Mainly, using printk
> statements inside the b43 code.
> I have been at this for a couple of months without any luck. Would you
> mind if I ask a few questions 
> about the way you went about on doing so? Or advice on how to do it?
> 
> Did you added the printk statements into the b43 source code or the b43
> firmware code?
I do not have access to the source code of the broadcom firmware, but
there is an open source project developing an open Source firmware
http://www.ing.unibs.it/~openfwwf/
>I would like to try
> something similar. As I mentioned earlier, I was not able to see the
> b43's 'C' source code with my
> Linux Ubuntu 11.10 distribution. I found a copy of the firmware source
> code with the
> assembly language, etc. Is that the code that you used for the printk
> statements? 
I am just working on the driver and treating the firmware as a black box.
> I thought that since the b43 driver is included in the kernel that
> Ubuntu 11.10 has, it 
> would also include the source code--no luck with that.
> 
> Any insight that you can share would be very much appreciated.
> 
> Cheers
> 
> William

Hauke

  parent reply	other threads:[~2012-01-30 19:37 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
     [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 [this message]
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=4F26F195.9050509@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