From: Pavel Roskin <proski@gnu.org>
To: Maya it <maya1625it@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] dev_base list head in the linux kernel code
Date: Thu, 23 Jun 2011 11:44:49 -0400 [thread overview]
Message-ID: <4E035F71.20602@gnu.org> (raw)
In-Reply-To: <BANLkTinvscyX=xh_auh96nf2UPV=njkYXg@mail.gmail.com>
On 06/22/2011 10:12 PM, Maya it wrote:
> Hi all,
>
> I have two wireless cards (wlan0 and wlan1) and want to access them
> separately. I plan to keep both in adhoc mode and communicate with wlan0 and
> wlan1 respectively at the other end of this communication. But since I am
> working at the kernel level, and I want to access these devices from the
> dev_base list. As far as I know, dev_base saves the net_devices which are
> initialized at boot up time. So I want to open the device and change its
> configuration after the kernel has loaded.
>
> Please guide and let me know if I am wrong in understanding the basics of
> the dev_base list.
Please don't cross-post. Cross-posting should be reserved for really
important topics, such as announcements by lead developers. I'm
trimming the cc list. Actually, your question would be suitable for the
netdev list, as there it nothing specific in your question about
wireless devices, let alone ath9k. Or better yet, maybe you could find
some forum or list for the newbies in kernel programming?
I suggest that you check the latest kernel source for examples before
asking questions. You can easily find that access to dev_base is
encapsulated by macros defined in netdevice.h, such as for_each_netdev.
Now you can look for examples of for_each_netdev in the code and see if
they do what you need.
--
Regards,
Pavel Roskin
parent reply other threads:[~2011-06-23 15:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BANLkTinvscyX=xh_auh96nf2UPV=njkYXg@mail.gmail.com>]
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=4E035F71.20602@gnu.org \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maya1625it@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).