On Sat, May 05, 2012 at 05:34:42PM -0700, Steven King wrote:
Hi Greg,
The qspi consolidation omitted support for device initialization when the qspi
is built as a module.
Signed-off-by: Steven King sfk...@fdwdc.com
---
arch/m68k/platform/520x/config.c |6 +++---
On Thu, Aug 11, 2011 at 02:39:25PM +1000, g...@snapgear.com wrote:
From: Greg Ungerer g...@uclinux.org
[This is a resend of this patch. If no-one has any objections then I
want to push this into linux-next, for eventual inclusion in the 3.2
merge window.]
Looks good.
Acked-by: Sam Ravnborg s
the mmu and non-mmu kernel/Makefiles can
easily be handled inside of a single Makefile. Merge the 2 back into
a single Makefile.
Looks good (except the typo that is nto a typo:-) )
Acked-by: Sam Ravnborg s...@ravnborg.org
___
uClinux-dev mailing list
uClinux
On Thu, Aug 11, 2011 at 03:10:21PM +1000, g...@snapgear.com wrote:
From: Greg Ungerer g...@uclinux.org
[This is a resend of this patch. Would like to hear what others think of
this change. It makes the top level configuration consistent for all m68k
type processors, and makes it much easier
Hi Greg.
+
+#if defined(__mc68020__) || defined(__mc68030__) || \
+defined(__mc68040__) || defined(__mc68060__)
Why use these to decide if this is MMU or not?
This code is not exposed to user-space so we can rely on CONFIG_* symbols.
IMO the CONIFG_* symbols is easier to read/maintain.
On Tue, Feb 22, 2011 at 08:40:53AM +0100, Geert Uytterhoeven wrote:
On Tue, Feb 22, 2011 at 08:29, Sam Ravnborg s...@ravnborg.org wrote:
Is there a plan to move m68k to the generic facilities as well ?
Moving m68k to genirq is (the next thing?) on my list...
If I succeed migrating
version of this script, and to
Sam Ravnborg for the m68k includes merge script this was based on).
Nothing outside of the arch/m68k and arch/m68knommu directories is
touched, and in the end there is no more arch/m68knommu. To apply you
simply run the script from the top of a current
Is there a plan to move m68k to the generic facilities as well ?
Moving m68k to genirq is (the next thing?) on my list...
If I succeed migrating sparc32 to genirq I hope to be of a little help here.
It looks like a bigger task to migrate m68k than it was/is to migrate sparc32.
It would
sfk...@fdwdc.com for the initial version of this script, and to
Sam Ravnborg for the m68k includes merge script this was based on).
Nothing outside of the arch/m68k and arch/m68knommu directories is
touched, and in the end there is no more arch/m68knommu. To apply you
simply run the script
On Fri, Jun 11, 2010 at 10:05:27AM -0400, Jate Sujjavanich wrote:
-Original Message-
From: uclinux-dev-boun...@uclinux.org
[mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Sam Ravnborg
Sent: Monday, June 07, 2010 12:09 PM
To: uClinux development list
Subject: Re: [uClinux
I used also a minimal configuration for the initramfs as described at
linux-2.6.33/Documentation/ramfs-rootfs-initramfs.txt.
-8-8-8-8-8
dir /dev 755 0 0
nod /dev/console 644 0 0 c 5 1
On Sat, Oct 17, 2009 at 06:02:58PM -0700, Steven King wrote:
This is a script and patch to merge the m68knommu arch into m68k.
The script was inspired by the script Sam Ravnborg used to merge the
includes from m68knommu. For those files common to both arches but
differing in content
On Sun, Feb 01, 2009 at 10:46:30PM +1000, Greg Ungerer wrote:
Hi Geert,
Geert Uytterhoeven wrote:
From b708bab9dbc93bc80bd06c9222ab34530736f737 Mon Sep 17 00:00:00 2001
From: Geert Uytterhoeven ge...@linux-m68k.org
Date: Thu, 29 Jan 2009 21:21:40 +0100
Subject: [PATCH] m68k: Unify
More review, testing, comments welcome...
Where to from here?
I'll pull from it and give it some m68k test builds.
After that, you can move it to for-next. If everything's well, it can go to
Linus.
Sounds like a plan.
Or should I amend and add my SoB and put it in m68k for-next?
On Sat, Dec 20, 2008 at 07:16:31AM -0700, Matt Waddel wrote:
This patch fixes a build error with the latest (4.3.2-45)
toolchain. .text.unlikely is required in the linker script.
Is this a general thing or specific to uclinux?
If it is general it belongs to:
include/asm-generic/vmlinux.lds.h
On Tue, Dec 09, 2008 at 12:26:05AM +0100, Arnd Bergmann wrote:
On Tuesday 09 December 2008, Geert Uytterhoeven wrote:
I have used the following include guard:
#ifdef __uClinux__
#include atomic_no.h
#else
#include atomic_mm.h
#endif
gcc -E -dM for the two compilers
I'm not sure if it's entirely correct, but I think you can use
#ifdef __KERNEL__
# ifdef CONFIG_MMU
# include atomic_mm.h
# else
# include atomic_no.h
# endif
#else
# ifndef __uClinux__
# include atomic_mm.h
# else
# include atomic_no.h
# endif
#endif
Can someone with a
On Mon, Dec 08, 2008 at 09:58:14PM +0100, Sam Ravnborg wrote:
[this mail is cross posted to uclinux mailing list which is subscriber only]
Following is a pseudo patch (a script + a patch) that merges
the include files for m68k and m68knommu in one place at:
I fixed the missing files so we
On Tue, Dec 09, 2008 at 12:02:46PM +0100, Arnd Bergmann wrote:
On Tuesday 09 December 2008, Geert Uytterhoeven wrote:
What are the other exported headers that differ?
byteorder.h, param.h, ptrace.h, setup.h, sigcontext.h, siginfo.h, signal.h
and unistd.h.
And diffing these files for the
With the above construct we do the right thing also for
headers exported to userspace.
But actually none of the headers using the above are
subject for export at the moment so we could use a
CONFIG_ symbol for the same.
One thing worth adding is that this patch fixes:
make
20 matches
Mail list logo
