From: "Constantine Shulyupin" <const@linuxdriver.co.il>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: conceptual map of the kernel source (Interactive Linux kernel map)
Date: Sat, 2 Aug 2008 01:28:01 +0300 [thread overview]
Message-ID: <8aa6b0650808011528x62268bc4l35ebb16cca9ae6c0@mail.gmail.com> (raw)
In-Reply-To: <63386a3d0808011507h28aa213mb27d32b2f855b9ac@mail.gmail.com>
Thank you for idea.
I wish to make map of embeedded Linux in future.
Now I focus on "generic" kernel.
On Sat, Aug 2, 2008 at 1:07 AM, Linus Walleij
<linus.ml.walleij@gmail.com> wrote:
> 2008/7/31 Constantine Shulyupin <const@linuxdriver.co.il>:
>
>> I am updating the kernel map: http://www.makelinux.net/kernel_map
>> It is conceptual map consisting of more than 200 most important kernel
>> functions.
>
> I was very impressed once I saw this map first, which was through
> your (?) contributions to the Linux entries in Wikipedia. Keep up the
> good work!
>
>> Could you please have a look and suggest fixes and updates.
>
> The embedded systems will be interested in most things not
> asm-i386 and arch-i386. For example you show a lot of PCI
> and such things in the lowest layers, I wonder if it'd be worth
> the effort to make arch-specific views of the lowermost parts
> (but probably not).
>
> Another this is that flash drivers MTD, doesn't fit into the picture,
> instead harddisk is uses as example.
>
> Linus
>
--
Constantine Shulyupin
Freelance Embedded Linux Engineer
054-4234440
http://www.linuxdriver.co.il/
prev parent reply other threads:[~2008-08-01 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 13:44 conceptual map of the kernel source (Interactive Linux kernel map) Constantine Shulyupin
2008-08-01 22:07 ` Linus Walleij
2008-08-01 22:28 ` Constantine Shulyupin [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=8aa6b0650808011528x62268bc4l35ebb16cca9ae6c0@mail.gmail.com \
--to=const@linuxdriver.co.il \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-embedded@vger.kernel.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).