2.6.22 flash boot

With the release of the 2.6.22, our boards didn't boot anymore. I traced
the change back to 2.6.21-git10/2.6.21-git11. 

The reason they didn't boot was that the kernel  didn't detect the flash
where the root filesystem is stored on. The boards boot without an
initrd, directly from flash.

A file was removed (rom.c) and mentioned as obsolete in the ChangeLog.

att'd is the patch to restore the file against 2.6.22 since restoring
this file allow the boards to boot again (i.e. detect mtdblocks as
rootfilesystem).

Am I missing something here?

Judging by the dts files, a number of other boards seem to be using a
similar flash configuration as I do.

-- 
  greetz, marc
That's your plan? Wile E. Coyote would come up with a better plan
than that!
	Crichton - Throne for a Loss
chiana 2.6.18-4-ixp4xx #1 Tue Mar 27 18:01:56 BST 2007 GNU/Linux

Hello.

Marc Leeman wrote:

With the release of the 2.6.22, our boards didn't boot anymore. I traced
the change back to 2.6.21-git10/2.6.21-git11. 

The reason they didn't boot was that the kernel  didn't detect the flash
where the root filesystem is stored on. The boards boot without an
initrd, directly from flash.

A file was removed (rom.c) and mentioned as obsolete in the ChangeLog.

[...]

Am I missing something here?

    It's been removed as conflicting with the new of_device probing code.
You can either register the "rom" device explicitly in your platform code, or 
put it on some bus below the ones specified to of_platform_device_probe() -- 
by your platform code again...

WBR, Sergei