From: "Rogério Brito" <rbrito@ime.usp.br>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: minimizing the configuration of linkstation_defconfig
Date: Mon, 27 Apr 2009 23:27:11 -0300 [thread overview]
Message-ID: <20090428022711.GA30538@ime.usp.br> (raw)
In-Reply-To: <2CE2BC61-1C6B-4D01-870B-BC460730AD79@kernel.crashing.org>
Hi, Kumar.
On Apr 27 2009, Kumar Gala wrote:
>
> On Apr 24, 2009, at 5:33 PM, Rogério Brito wrote:
>> 04. disable CONFIG_BLK_DEV_RAM.
>
> do we not allow booting a ramdisk?
Well, do we need a block device in ram to use initramfs?
(...)
>> Dear Kumar, please, apply this one.
>>
>> I have another patch regarding one regression regarding MTD &
>> PHYSMAP_COMPAT that I plan to send on top of this one.
>
> Ok, can we look at just specifying such info in the linkstation device
> tree.
Thanks. The MTD & PHYMAP_COMPAT are the things that have been bugging me
and my main reason to keep with the bleeding edge kernels is to get things
whey they were (regarding mtd) as in kernel 2.6.28.
As I have no experience with MTD devices, I would appreciate a reference to
their workings... All that I know is that all my /dev/mtd* devices are gone
if I boot a 2.6.29* kernel.
Of course, I can do a git bisect process (since the MTD subsystem doesn't
work as it did in the past even if I enable PHYMAP_COMPAT and put the same
settings there, quite unfortunately).
> Also, can you break this defconfig update into two patches. 1. that
> just updates to 2.6.30-rc3 (or latest) and 2. that makes the various
> changes you've listed above.
No problems with that. I will do that ASAP. Thanks for your kind comments.
Regards, Rogério Brito.
P.S.: Guennadi, did you see any regressions with your linkstation/kurobox
HG or whatever device you have?
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2009-04-28 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 6:58 Regarding the linkstation defconfig Rogério Brito
2009-04-24 20:05 ` Guennadi Liakhovetski
2009-04-24 21:23 ` Rogério Brito
2009-04-24 22:33 ` [PATCH] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-04-27 19:29 ` Kumar Gala
2009-04-28 2:27 ` Rogério Brito [this message]
2009-04-28 13:16 ` Kumar Gala
2009-04-28 14:48 ` Rogério Brito
2009-04-28 14:54 ` Kumar Gala
2009-04-28 13:03 ` [PATCH 1/2] powerpc: updating the linkstation_defconfig Rogério Brito
2009-04-28 13:32 ` [PATCH 2/2] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-05-16 16:04 ` [PATCH] " Rogério Brito
2009-06-11 2:46 ` Kumar Gala
2009-04-28 16:44 ` [PATCH 2/2] " Rogério Brito
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=20090428022711.GA30538@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=g.liakhovetski@gmx.de \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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).