* RE: infradead.org vs kernel.org sources
@ 2001-07-31 22:05 Vipin Malik
2001-07-31 22:28 ` Kent Borg
0 siblings, 1 reply; 3+ messages in thread
From: Vipin Malik @ 2001-07-31 22:05 UTC (permalink / raw)
To: 'Kent Borg', Linux Mtd
>But now I had occasion to look at the stuff I grabbed from the
>infradead cvs repository. It looks rather different.
AFAIK latest stuff is in the CVS repo. IF you are comparing with the stuff
in the release kernels (is that what you meant by kernel.org?) then you
should be working off the CVS.
>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.)
There is no diff in doing modules vs "merged in" as far as how you link in
the CVS code into the kernel. You can do both (rather either).
>Is this what I want?
Sounds like it. Is it? :)
>-kb, the Kent who hopes to get JFFS working on top of MTD.
Why? Why not JFFS2? It's more stable and full featured (and not to mention
next gen from JFFS). As long as you are using 2.4.x as JFFS2 does not yet
work with 2.2.x
Vipin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: infradead.org vs kernel.org sources
2001-07-31 22:05 infradead.org vs kernel.org sources Vipin Malik
@ 2001-07-31 22:28 ` Kent Borg
0 siblings, 0 replies; 3+ messages in thread
From: Kent Borg @ 2001-07-31 22:28 UTC (permalink / raw)
To: Vipin Malik; +Cc: Linux Mtd
On Tue, Jul 31, 2001 at 05:05:33PM -0500, Vipin Malik wrote:
> AFAIK latest stuff is in the CVS repo. IF you are comparing with the stuff
> in the release kernels (is that what you meant by kernel.org?) then you
> should be working off the CVS.
Cool.
> >-kb, the Kent who hopes to get JFFS working on top of MTD.
> Why? Why not JFFS2? It's more stable and full featured (and not to mention
> next gen from JFFS). As long as you are using 2.4.x as JFFS2 does not yet
> work with 2.2.x
Oops. I was being sloppy and using "JFFS" as a kinda generic term.
Certainly I expect to go for JFFS2.
Thanks a bunch,
-kb, the Kent who has hacked at flash before, but who is new at these
specifics.
^ permalink raw reply [flat|nested] 3+ messages in thread
* infradead.org vs kernel.org sources
@ 2001-07-31 21:54 Kent Borg
0 siblings, 0 replies; 3+ messages in thread
From: Kent Borg @ 2001-07-31 21:54 UTC (permalink / raw)
To: Linux Mtd
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-07-31 22:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-07-31 22:05 infradead.org vs kernel.org sources Vipin Malik
2001-07-31 22:28 ` Kent Borg
-- strict thread matches above, loose matches on Subject: below --
2001-07-31 21:54 Kent Borg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox