From: "Ming Chow 周明" <chow.ming@linuxbj.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch for compcache recipe
Date: Fri, 14 Aug 2009 14:29:04 +0800 [thread overview]
Message-ID: <4A850430.6060809@linuxbj.com> (raw)
In-Reply-To: <200908140406.00714.holger+oe@freyther.de>
Holger Hans Peter Freyther wrote:
> On Thursday 13 August 2009 21:10:07 Ming Chow 周明 wrote:
>
>> Hi,
>>
>> I have tried compcache from code.google.com on beagleboard rev B5 and
>> n800 for a couple of weeks. It seems helping me getting more usable memory.
>> The patch will add compcache stuff which provides both compcache kernel
>> modules and managing tool.
>> Tested with recent oe repo on my boards, more evaluation on various real
>> hardware platforms needed though.
>> BTW not touched checksum.ini for the tarball yet.
>>
>
> Hi,
>
> the patch looks nice. I have three minor comments.
>
thanks for your kind advices.
> Would you please add the checksums.ini entry and send the mail with a Signed-
> off-by: line?
>
Sure. I added the checksum entry.
BTW. I had experienced some checksum mismatch before. A few packages
which just work can not pass checksum matching. I guess it may be caused
by hosting or tarball changing without notice. For I am not very clear
how the global checksum.ini is maintained. I lazily set
OE_ALLOW_INSECURE_DOWNLOADS.
> I think sending the last two patches (modules_instal target) and not using gcc
> directly upstream would make sense? Did you already do that?
>
>
The modules_install patch is for enable "make modules_install" work when
use the Kernel kbuild system which make it kernel independent.
Originally, people have to use a load_modules.sh script instead install
.kos to lib/modules directory. I think a startup script in /etc/init.d
and a setting file in /etc is a next step work, after find out some
optimal settings on certain platform/distro combination.
The rzscontrol is compiled to native binary with hardcoded in stock tar
ball, change to use ${CCLD} make it work arch independent.
> This one is on naming. The exmap kernel module is called "kernel-module-
> exmap", for the sake of consistency you should consider renaming "compach-
> modules" to "kernel-module-compcache"? And maybe install rzscontrol into the
> compache package too. The reason is that it is not easy to spot the
> relationship from compache to the rzscontrol package.
>
> z.
>
Good point. I am sorry for mis-naming the module package. Agree with you.
And which is better do you think:
mix rzscontrol and kernel modules
or
put modules in kernel-module-compcache
put rzscontrol in kernel-module-compcache-utils (or compcache-utils)
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-08-14 6:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 19:10 patch for compcache recipe Ming Chow 周明
2009-08-14 2:06 ` Holger Hans Peter Freyther
2009-08-14 6:29 ` Ming Chow 周明 [this message]
2009-08-14 14:39 ` Rolf Leggewie
2009-08-14 14:55 ` Ming Chow 周明
2009-08-14 15:05 ` Ming Chow 周明
2009-08-14 15:19 ` Koen Kooi
2009-08-14 15:33 ` Rolf Leggewie
2009-08-19 16:32 ` Ming Chow 周明
2009-08-19 16:50 ` Koen Kooi
2009-08-20 1:36 ` Ming Chow 周明
2009-08-20 2:09 ` Holger Hans Peter Freyther
2009-08-20 17:20 ` Ming Chow 周明
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=4A850430.6060809@linuxbj.com \
--to=chow.ming@linuxbj.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.