From: "Bob Zhang" <zhanglinbao@gmail.com>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does anyone run AXFS in 2.4 version of kernel ? I am trying my best to apply AXFS patches into 2.4.18
Date: Mon, 16 Jun 2008 22:55:26 +0800 [thread overview]
Message-ID: <85e7c2fc0806160755h10d90d12l1519618de55a644d@mail.gmail.com> (raw)
In-Reply-To: <6934efce0805131801s633a1692ha8914a76173c2c80@mail.gmail.com>
Hi Jared Hulbert ,
What a pity that I found few document execept axfs code.
Although we can read the source code to get all things that we want to
know as a programmer, a good document is helpfull for understanding
the source code.
I am debugging the AXFS code and researching its implement , I think a
good document is very precious ,but there is no such .
Could you mind please introuducing your architecture design ? Detailed
info will be welcomed .
For example , ext2 file system , we will get a ext2 file system
specification, such as super block , and how to organize the
structures of ext2 , Would you mind please introducing these related
info ?
By the way , have you managed the AXFS specification ? if yes ,many
programmer will join the AXFS group .
Best Regards,
Bob
2008/5/14 Jared Hulbert <jaredeh@gmail.com>:
>> thanks for your work . we look forward your paches for 2.4.21 or
>> 2.4.18 or other 2.4.x . thanks again .
>> In the meantime , I am compiling axfs patches in 2.4.18 .My policy is
>> that I basicly don't changed the AXFS code , and only add some
>> functions existed in 2.6.x into 2.4 kernel ,if necessary , I will
>> modify it . Thus , I think such working is not rather difficult ,
>> anyway , I am
>> analysing the implement of AXFS code , if necessary , I will modify
>> some functions of axfs.
>>
>> Till now , AXFS_super.c has been almost ok . Next ,I will compile
>> other axfs code and check some errors and warnning , and run the
>> kernel in the skyeye which supported smdk2410 .
>
> You're free to mess around with that if you want, but what I'm going
> to release will make that a waste of time. It's significantly
> updated.
>
prev parent reply other threads:[~2008-06-16 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:19 Bob Zhang
2008-05-12 16:23 ` Jared Hulbert
2008-05-14 0:46 ` Bob Zhang
2008-05-14 1:01 ` Jared Hulbert
[not found] ` <85e7c2fc0805190842v6ee5f4f3jef7790b0fa459a21@mail.gmail.com>
2008-06-16 14:20 ` Bob Zhang
2008-06-17 14:57 ` Bob Zhang
2008-06-17 15:26 ` Bob Zhang
2008-06-18 14:43 ` Bob Zhang
2008-06-16 14:55 ` Bob Zhang [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=85e7c2fc0806160755h10d90d12l1519618de55a644d@mail.gmail.com \
--to=zhanglinbao@gmail.com \
--cc=jaredeh@gmail.com \
--cc=linux-kernel@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
Powered by JetHome