On Apr 27, 2009, at 9:27 PM, Rog=E9rio Brito wrote:

Hi, Kumar.

On Apr 27 2009, Kumar Gala wrote:

quoted

On Apr 24, 2009, at 5:33 PM, Rog=E9rio Brito wrote:

quoted

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?

(...)

I'm pretty sure we need this for old initrd style ramdisks so I'd =20
prefer we leave it enabled.

quoted

quoted

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 =20
device
tree.

Thanks. The MTD & PHYMAP_COMPAT are the things that have been =20
bugging me
and my main reason to keep with the bleeding edge kernels is to get =20=

things
whey they were (regarding mtd) as in kernel 2.6.28.

As I have no experience with MTD devices, I would appreciate a =20
reference to
their workings... All that I know is that all my /dev/mtd* devices =20
are gone
if I boot a 2.6.29* kernel.

Of course, I can do a git bisect process (since the MTD subsystem =20
doesn't
work as it did in the past even if I enable PHYMAP_COMPAT and put =20
the same
settings there, quite unfortunately).

ok.. I killed my kurobox long ago so can't be much help here.

- k=