From: jiangtao.jit@gmail.com (Tao Jiang (姜涛))
To: kernelnewbies@lists.kernelnewbies.org
Subject: Need help on understanding hardware detection
Date: Tue, 20 Aug 2013 09:46:54 +0800 [thread overview]
Message-ID: <5212CA85.1000107@gmail.com> (raw)
In-Reply-To: <CAKQ1VnTwv81ZzE+MLM1k0iD3-fR17ydEV3wToBm_GFMP+LPRJg@mail.gmail.com>
Saqlain:
Thanks for your reply.
The article really opened my eyes.
But in that article wrote as
1. " Linux kernel constantly scans all your computer bus?es for any changes and new hardware. Once any change on any bus is detected magic begins "
And in the comments at the bottom,
2. "a bus controller notifies the CPU through an interrupt which allows the kernel to query the controller back for information"
So my question is which one is right?
And can you show me more details on Linux kernel's implementation about "constantly scans" or "notifies the CPU through an interrupt"?
------------------
Tao Jiang (??)
2013-08-20
-------------------------------------------------------------
????Saqlain Abbas <saqlain.abbas.7@gmail.com>
?????2013-08-19 19:53
????Tao Jiang (??)
???kernelnewbies
???Re: Need help on understanding hardware detection
have a look at http://blogas.sysadmin.lt/?p=141 will give you a nice idea...
Cheers,
Saqlain.
On Mon, Aug 19, 2013 at 4:47 PM, Tao Jiang (??) <jiangtao.jit@gmail.com>wrote:
> Hi All:
> I did some search on "how does linux kernel detect hardware?" and
> got what udev is.
> I konw Linux kernel will send a netlink message to udevd.
> But I still do not understand how the kernel can decide to send a
> netlink message.
> What happend before the netlink message?
> Take an usb stick for example, what will happen and what the
> kernel do from the very beginning of it been plugged in?
> Thank you for advance. Any references will be appreciated.
>
> --------------
> Tao Jiang (??)
> 2013-08-19
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Kind Regards,
Saqlain Abbas.
next prev parent reply other threads:[~2013-08-20 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 11:47 Need help on understanding hardware detection Tao Jiang (姜涛)
2013-08-19 11:53 ` Saqlain Abbas
2013-08-20 1:46 ` Tao Jiang (姜涛) [this message]
2013-08-20 3:28 ` Saqlain Abbas
2013-08-20 4:53 ` Tao Jiang (姜涛)
2013-08-19 22:41 ` /dev/sda to ata_host Com Developer
2013-08-20 6:09 ` Valdis.Kletnieks at vt.edu
2013-08-20 7:25 ` Com Developer
2013-08-20 12:28 ` Valdis.Kletnieks at vt.edu
2013-08-20 12:39 ` Greg Freemyer
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=5212CA85.1000107@gmail.com \
--to=jiangtao.jit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).