From: Kent Borg <kentborg@borg.org>
To: Linux Mtd <linux-mtd@lists.infradead.org>
Subject: infradead.org vs kernel.org sources
Date: Tue, 31 Jul 2001 17:54:42 -0400 [thread overview]
Message-ID: <20010731175442.I10857@borg.org> (raw)
Hello, a newbie here, and I thought I was making good progress
(debugging why I couldn't talk to our flash at all), and then I got
confused over sources.
I am working on an embedded PPC 405 controller. We started with 2.4.2
sources from mvista.com, which seem quite close to kernel.org. And
the main MTD web page <http://www.linux-mtd.infradead.org/> says "Very
occasionally, I make snapshot releases. Now that the MTD code is in
the 2.4 kernel, it's become even rarer. ", which I took to mean that
the kernel.org sources were up to date.
But now I had occasion to look at the stuff I grabbed from the
infradead cvs repository. It looks rather different.
For example, mtd/drivers/mtd in the infradead sources seems to have
files I find in linux/drivers/mtd in kernel.org sources, but the
infradead sources are more elaborate and have sub-directories.
I guess my next move is to drop that infradead sub-tree into the
linux/drivers/mtd directory and see what happens. (I think we need to
directly link, not be a loadable module, so the sources need to be
merged.)
Is this what I want?
Thanks,
-kb, the Kent who hopes to get JFFS working on top of MTD.
next reply other threads:[~2001-07-31 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 21:54 Kent Borg [this message]
2001-08-03 19:09 ` Building MTD with JFFS2 Kent Borg
2001-08-07 10:19 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-07-31 22:05 infradead.org vs kernel.org sources Vipin Malik
2001-07-31 22:28 ` Kent Borg
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=20010731175442.I10857@borg.org \
--to=kentborg@borg.org \
--cc=linux-mtd@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