From: Ramesh <p.rameshbabu@globaledgesoft.com>
To: "Paul G. Allen" <pgallen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless-owner <linux-wireless-owner@vger.kernel.org>
Subject: Re: ath9k
Date: Fri, 1 Jan 2016 15:11:27 +0530 (IST) [thread overview]
Message-ID: <1282227479.2977961.1451641287034.JavaMail.zimbra@globaledgesoft.com> (raw)
In-Reply-To: <CAN4-gUH4NSfbGXQdWNwDG3YSCXR_f-Tn=nQzaWQ=knGJu4AU3Q@mail.gmail.com>
Thanks for your response. I didn't ask tool to analyse. I asked about call flow.
Like how they are communicating between User space to kernel, cfg80211 to mac80211,
mac80211 to driver and driver to hardware.
Thanks,
Ramesh
----- Original Message -----
From: "Paul G. Allen" <pgallen@gmail.com>
To: "Ramesh" <p.rameshbabu@globaledgesoft.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, "linux-wireless-owner" <linux-wireless-owner@vger.kernel.org>
Sent: Friday, January 1, 2016 3:35:59 AM
Subject: Re: ath9k
The best tool I've ever used (in over 30 years of software
development) is Understand:
https://scitools.com/
Thanks,
PGA
On Wed, Dec 30, 2015 at 9:41 PM, Ramesh <p.rameshbabu@globaledgesoft.com> wrote:
>
>
> Hi,
>
> can anyone please tell me how to analyse ath9k source code and call flow..?
>
>
>
>
> Thanks,
> Ramesh
> Disclaimer:- The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message (including the enclosure/(s) or attachment/(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of GlobalEdge. Before opening any mail and attachments please check them for viruses .GlobalEdge does not accept any liability for virus infected mails.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Paul G. Allen, BSIT/SE
Owner, Sr. Engineer
Random Logic Consulting
www.randomlogic.com
Disclaimer:- The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message (including the enclosure/(s) or attachment/(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of GlobalEdge. Before opening any mail and attachments please check them for viruses .GlobalEdge does not accept any liability for virus infected mails.
prev parent reply other threads:[~2016-01-01 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 5:41 ath9k Ramesh
2015-12-31 22:05 ` ath9k Paul G. Allen
2016-01-01 9:41 ` Ramesh [this message]
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=1282227479.2977961.1451641287034.JavaMail.zimbra@globaledgesoft.com \
--to=p.rameshbabu@globaledgesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=pgallen@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).