Message-ID: <4D8B33A2.4090105@snapgear.com>
Date:	Thu, 24 Mar 2011 22:05:54 +1000
From:	Greg Ungerer <gerg@...pgear.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
CC:	<linux-m68k@...r.kernel.org>, <uclinux-dev@...inux.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/1] m68k: merge m68k and m68knommu arch directories

On 24/03/11 18:04, Geert Uytterhoeven wrote:
> On Thu, Mar 24, 2011 at 01:01, Greg Ungerer<gerg@...pgear.com>  wrote:
>> Hi Geert,
>>
>> On 24/03/11 08:14, Geert Uytterhoeven wrote:
>>>
>>> On Wed, Mar 23, 2011 at 23:07, Geert Uytterhoeven<geert@...ux-m68k.org>
>>> áwrote:
>>>>
>>>> On Tue, Mar 22, 2011 at 05:43, ├í<gerg@...pgear.com>  áwrote:
>>>>>
>>>>> The following patch merges the m68k and m68knommu arch directories.
>>>>> This patch has been trimmed for review purposes - the automated file
>>>>> moving and mergeing carried out by the script contained in this email
>>>>> has been removed. Only the manually required changes after running the
>>>>> script are shown as the patch. (So to end up with the final required
>>>>> change you need to run this script then apply the patch).
>>>>>
>>>>> This change is available as the only commit on the m68knommu git tree,
>>>>> for-linux branch:
>>>>>
>>>>> The following changes since commit
>>>>> a952baa034ae7c2e4a66932005cbc7ebbccfe28d:
>>>>> áLinus Torvalds (1):
>>>>> á á á áMerge branch 'for-linus' of
>>>>> git://git.kernel.org/.../dtor/input
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> ágit://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
>>>>> for-linus
>>>>>
>>>>> Greg Ungerer (1):
>>>>> á á ám68k: merge m68k and m68knommu arch directories
>>>>>
>>>>>
>>>>> It is also on the for-next branch in that tree, so will get some testing
>>>>> in the next tree for the next few days.
>>>>
>>>> defconfig is now a nommu-config, and it fails?
>>>
>>> BTW, haven't tried it myself yet. I'm busy bisecting an issue with
>>> initrds, which
>>> got introduced between 2.6.37 and 2.6.38.
>>>
>>> Init fails with "init: cannot open inittab", followed by
>>> "Kernel panic - not syncing: Attempted to kill init!".
>>>
>>> As I can't get ramdisks to work on ARAnyM, I need to use real hardware,
>>> which
>>> suffers a lot from long reboot/copy kernel/test cycles...
>>
>> As one data point (though not sure how useful this is to you... :-)
>> I can compile for an Atari target with the merge tree and load it
>> and run it on ARAnyM - using a ramdisk for root fs. Seems to work
>> ok.
>
> Strange. On ARAnyM I get:
>
>      Trying to unpack rootfs image as initramfs...
>      rootfs image is not initramfs (junk in compressed archive); looks
> like an initrd
>      Freeing initrd memory: 350k freed

I see that too.


> but later it fails with:
>
>      RAMDISK: Couldn't find valid RAM disk image starting at 0.

But later I get:

RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 4096KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem) readonly on device 1:0.


BTW the command boot args are:

Kernel command line: root=/dev/ram load_ramdisk=1 ramdisk_size=4096 
video=atafb:tthigh console=tty0 debug stram_swap=0 BOOT_IMAGE=vmlinux

> It "works" (i.e. mounts) on the Amiga, but later it fails with the
> inittab error.
> Will  bisect more tonight...

Good luck :-)

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@...pgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists