On 02/06/13 13:58, James Hogan wrote:
Remove the SYMBOL_PREFIX Kconfig symbol as it's empty anyway.
Signed-off-by: James Hogan
Cc: Jonas Bonn
Cc: li...@lists.openrisc.net
Cc: Mike Frysinger
---
arch/openrisc/Kconfig |4
1 files changed, 0 insertions(+), 4 deletions(-)
T
On 02/10/13 06:58, Len Brown wrote:
From: Len Brown
pm_idle() on openrisc was dead code.
Signed-off-by: Len Brown
Cc: li...@lists.openrisc.net
---
arch/openrisc/kernel/idle.c | 5 -
1 file changed, 5 deletions(-)
Thanks, Len. Will apply.
/Jonas
diff --git a/arch/openrisc/kernel/id
On 11 February 2013 08:26, Vineet Gupta wrote:
>
> The only downside of this patch is that userspace signal stack grows in size,
> since signal frame only cares about scratch regs (pt_regs), but has to
> accommodate
> unused placeholder for callee regs too by virtue of using user_regs_struct.
I
On 11 February 2013 11:13, Vineet Gupta wrote:
> On Monday 11 February 2013 03:06 PM, Jonas Bonn wrote:
>> On 11 February 2013 08:26, Vineet Gupta wrote:
>>
>>> The only downside of this patch is that userspace signal stack grows in
>>> size,
>>> since
On 11 February 2013 11:28, James Hogan wrote:
> On 11/02/13 10:13, Vineet Gupta wrote:
>> On Monday 11 February 2013 03:06 PM, Jonas Bonn wrote:
>>> On 11 February 2013 08:26, Vineet Gupta wrote:
>>>
>>>> The only downside of this patch is that use
On 11 February 2013 12:22, Vineet Gupta wrote:
> On Monday 11 February 2013 04:23 PM, Jonas Bonn wrote:
>> On 11 February 2013 11:28, James Hogan wrote:
>>> On 11/02/13 10:13, Vineet Gupta wrote:
>>>> On Monday 11 February 2013 03:06 PM, Jonas Bonn wrote:
>>&
On 11 February 2013 13:37, Vineet Gupta wrote:
>
> Anyhow going back to my orig patch - if we park the
> callee-regs-in-sigcontext-or-not, other bits look OK ?
>
Aside from the callee-regs question (which I hope somebody more
knowledgeable can chime in on): Acked-by: Jonas
fixes.
* Four trivial cleanups.
James Hogan (1):
openrisc: remove CONFIG_SYMBOL_PREFIX
Jonas Bonn (4):
openrisc: remove unused current_regs
openrisc: fix up vmalloc page table loading
openrisc: update DTLB-miss
inclusion
asm/cmpxchg.h into linux/llist.h.
CC: David Howells
Signed-off-by: Jonas Bonn
---
include/asm-generic/atomic.h |6 --
include/asm-generic/cmpxchg.h | 10 ++
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/include/asm-generic/atomic.h b/include/asm
chg.h
standalone.
Thanks,
Jonas
On 02/28/2013 06:54 AM, Jonas Bonn wrote:
asm/cmpxchg.h can be included on its own and needs to be self-consistent.
The definitions for the cmpxchg*_local macros, as such, need to be part
of this file.
This fixes a build issue on OpenRISC since the system.h smashing
On 03/12/13 11:12, Alexandre Courbot wrote:
This is one step towards the removal of the GENERIC_GPIO option.
OpenRISC mandates the use of GPIOLIB, which enables GENERIC_GPIO anyway,
so this patch should be a no-op.
Acked-by: Jonas Bonn
Signed-off-by: Alexandre Courbot
---
arch/openrisc
hould.
* The VIRT_TO_BUS selector was added for OpenRISC, but OpenRISC does
not have the virt_to_bus methods, so there's a patch to remove it
again.
--------
Jonas Bonn (3):
openrisc: require gpiolib
asm-generic: move cmpx
On Thu, 2012-10-11 at 10:03 +0100, James Hogan wrote:
> This is modelled on commits such as the one below:
>
> Commit fc1c3a003edb8a6778e64e10ef671a38c76c969e ("sh: use kbuild.h
> instead of defining macros in asm-offsets.c") introduced in v2.6.26.
>
> Signed-off-by: James Hogan
Thanks, looks g
; and looking at their io.h I don't see any obvious problems.
Acked-by: Jonas Bonn for OpenRISC
Who's tree should this go via. I can take it via the openrisc tree, but
it would be good to get some Ack's that this isn't going to break things
for the other arch's (in parti
Hi Al,
A couple of patches here that continue the cleanup outlined in the
kernel_thread discussion. Feel free to take these via your tree if
you feel that's appropriate; otherwise let me know and I'll throw
these into the openrisc tree.
/Jonas
Jonas Bonn (2):
openrisc: move sys_clo
The plan seems to be to eventually drop the
regs argument to do_fork altogether.
Signed-off-by: Jonas Bonn
---
arch/openrisc/kernel/entry.S|6 ++
arch/openrisc/kernel/process.c |3 ++-
arch/openrisc/kernel/sys_or32.c |9 -
3 files changed, 8 insertions(+), 10 deletion
Signed-off-by: Jonas Bonn
---
arch/openrisc/kernel/process.c |6 +-
arch/openrisc/kernel/sys_or32.c |8 +---
2 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/arch/openrisc/kernel/process.c b/arch/openrisc/kernel/process.c
index e0874b8..efbe4f8 100644
--- a/arch
On Thu, 2012-10-25 at 16:55 +0100, Al Viro wrote:
> On Thu, Oct 25, 2012 at 05:46:38PM +0200, Jonas Bonn wrote:
> > + else
> > + userregs->sp = regs->sp;/* fork/clone */
>
> What for? userregs->sp will be equal to regs->sp at t
I've done some work on cleaning up the definitions of pci_device_id to
make them "static const" (where possible) and to make sure they go into
__devinitconst. There are about 350 changes of the type shown in the
diff at the end of this mail.
All these changes are in my public GIT tree at:
git:/
On 09/21/2012 12:46 AM, Kees Cook wrote:
When using audit on OpenRISC, an audit arch is needed. This defines
it and fixes a compile-time bug uncovered in linux-next, likely from a
cut/paste from an arch with 64/32-bit modes that defined arch_arch():
arch/openrisc/kernel/ptrace.c:190:2: error: im
Hi David,
On Thu, 2012-10-04 at 20:51 +0100, David Howells wrote:
> Can you merge the following branch into the openrisc tree please.
>
> This is to complete part of the UAPI disintegration for which the preparatory
> patches were pulled recently.
>
> Note that there are some fixup patches which
On 17 October 2012 00:35, Al Viro wrote:
>
> Not even a tentative patchset: hexagon, openrisc, tile, xtensa.
>
I did most of the OpenRISC conversion last weekend... the
kernel_thread bits work fine but I end up with the init thread dying
with what I've got now for kernel_execve. Once I've got th
On 13 November 2012 12:41, James Hogan wrote:
> The uClibc patches I mentioned have been posted, see here:
>
> http://lists.busybox.net/pipermail/uclibc/2012-November/047110.html
>
> Please do try them out and provide any feedback.
>
Hi James,
Many thanks for picking this up...
This is the thir
On 7 November 2012 10:47, Vineet Gupta wrote:
> diff --git a/arch/arc/include/asm/ptrace.h b/arch/arc/include/asm/ptrace.h
> new file mode 100644
> index 000..c178357
> --- /dev/null
> +++ b/arch/arc/include/asm/ptrace.h
> @@ -0,0 +1,120 @@
> +/* THE pt_regs: Defines how regs are saved during
On 8 November 2012 19:52, Vineet Gupta wrote:
> On 7 November 2012 10:47, Vineet Gupta wrote:
>> I'd recommend not exporting the pt_regs structure to userspace. This
>> struct is used heavily within the kernel and it's nice to have the
>> leeway to be able to modify it as things evolve. GDB doe
The following changes since commit
6f0c0580b70c89094b3422ba81118c7b959c7556:
Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
are available in the git repository at:
git://openrisc.net/~jonas/linux tags/for-3.8
for you to fetch changes up to 634bd40a894d64df09ba36c12bb6e70787989ba9:
openrisc: u
On Thu, 2012-11-15 at 11:00 -0700, Shuah Khan wrote:
> On Fri, 2012-10-26 at 10:05 -0600, Shuah Khan wrote:
> > Add support for debug_dma_mapping_error() call to avoid warning from
> > debug_dma_unmap() interface when it checks for mapping error checked
> > status. Without this patch, device driver
On 04/27/2013 08:02 PM, Stefan Kristiansson wrote:
Motivation for this is to be able to print the way information
properly in print_cpuinfo(), instead of hardcoding it to one.
Signed-off-by: Stefan Kristiansson
Applied. Thanks.
/Jonas
---
arch/openrisc/include/asm/cpuinfo.h | 2 ++
arc
On 07/31/2013 05:34 AM, Chen Gang wrote:
Need append "_D__linux__" to KBUILD_CFLAGS, just like some of another
architectures have done, or 'allmodconfig' can not pass compiling.
The related error:
CC [M] fs/coda/psdev.o
In file included from include/linux/coda.h:65:0,
from PPC to DT common code.
Again it could be there as it was originally copied from powerpc.
Signed-off-by: Sudeep KarkadaNagesha
Cc: Jonas Bonn
Hi Jonas,
Since both microblaze and openrisc have moderated lists which I am not
member of, these patches were blocked. Michal Simek agreed to
Hi Geert,
On 05/14/2013 09:32 AM, Geert Uytterhoeven wrote:
crypto/xor.c:25:21: error: asm/xor.h: No such file or directory
Signed-off-by: Geert Uytterhoeven
Cc: Jonas Bonn
Acked-by: Jonas Bonn
Feel free to take it via your tree for -rc5, as per your "exotic fixes"
email
CC: Mikael Starvik
CC: Jesper Nilsson
CC: linux-cris-ker...@axis.com
Signed-off-by: Jonas Bonn
---
Hi Geert,
As your 'exotic' branch seems to show you're doing some work on CRIS, how
about taking this rather trivial patch into your branch as well. I sent
this to the CRIS main
Ack would be nice.
Go ahead and take this patch via your tree.
Just in case:
Acked-by: Richard Kuo
Acked-by: Jonas Bonn
Thanks,
Jonas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordom
On 10 March 2013 07:26, Jiang Liu wrote:
> Use common help functions to free reserved pages.
> Also include to avoid local declarations.
>
> Signed-off-by: Jiang Liu
> Cc: Jonas Bonn
Tested and works fine on OpenRISC.
Acked-by: Jonas Bonn
/Jonas
> ---
> arch/open
On 03/26/2013 04:54 PM, Jiang Liu wrote:
Prepare for removing num_physpages and simplify mem_init().
Signed-off-by: Jiang Liu
Cc: Jonas Bonn
Cc: David Howells
Cc: Arnd Bergmann
Cc: li...@lists.openrisc.net
Cc: linux-kernel@vger.kernel.org
Tested and works fine on OpenRISC.
Acked-by
The definitions of struct pci_device_id arrays should generally follow
the same pattern across the entire kernel. This macro defines this
array as static const and puts it into the __devinitconst section.
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
include/linux/pci.h |8 +
at 13:10 +0100, Jonas Bonn wrote:
> The definitions of struct pci_device_id arrays should generally follow
> the same pattern across the entire kernel. This macro defines this
> array as static const and puts it into the __devinitconst section.
>
> Signed-off-by: Jonas Bonn <[EMAIL P
And again, what does this buy us?
Clarity and simplicity, I hope... there are a bunch of definitions
scattered about the kernel that omit the __devinitdata modifier despite
the documentation stating that it should always be there. The
definition really should have been const, which wasn't
The definitions of struct pci_device_id arrays should generally follow
the same pattern across the entire kernel. This macro defines this
array as const and puts it into the __devinitconst section.
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
include/linux/pci.h |9 +
1
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/amd8111e.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/amd8111e.c b/drivers/net/amd8111e.c
index 85f7276..a4ad2fb 100644
--- a/drivers/net/amd8111e.c
+++ b/drivers/net/amd8111e.c
@@
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/tlan.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/tlan.c b/drivers/net/tlan.c
index 3af5b92..bea59c6 100644
--- a/drivers/net/tlan.c
+++ b/drivers/net/tlan.c
@@ -253,7 +253,7 @@ static
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/wan/dscc4.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wan/dscc4.c b/drivers/net/wan/dscc4.c
index c6f26e2..16d3a4c 100644
--- a/drivers/net/wan/dscc4.c
+++ b/drivers/net/wan/d
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/arcnet/com20020-pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/arcnet/com20020-pci.c
b/drivers/net/arcnet/com20020-pci.c
index b8c0fa6..87ee0db 100644
--- a/drivers/net/arcnet/co
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/defxx.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/defxx.c b/drivers/net/defxx.c
index ddc30c4..84a3ce5 100644
--- a/drivers/net/defxx.c
+++ b/drivers/net/defxx.c
@@ -3630,7 +3630,7 @@
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/hamachi.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/hamachi.c b/drivers/net/hamachi.c
index b53f6b6..d8056e9 100644
--- a/drivers/net/hamachi.c
+++ b/drivers/net/hamachi.c
@@ -1987,7 +
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/pasemi_mac.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/pasemi_mac.c b/drivers/net/pasemi_mac.c
index 2e39e02..069fa7c 100644
--- a/drivers/net/pasemi_mac.c
+++ b/drivers/net/pasemi
The PCI_DEVICE_TABLE patch I sent earlier doesn't necessarily make much sense
by itself... here is a set of patches that apply this macro, in turn moving a
lot of this data into __devinitconst which is discardable in certain
situations. Hopefully the benefit of this approach is a bit clearer n
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/wan/lmc/lmc_main.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wan/lmc/lmc_main.c b/drivers/net/wan/lmc/lmc_main.c
index 6635ece..e85cfe7 100644
--- a/drivers/net/wan/lmc/lmc_main.c
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/niu.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/niu.c b/drivers/net/niu.c
index e98ce1e..ab8148a 100644
--- a/drivers/net/niu.c
+++ b/drivers/net/niu.c
@@ -62,7 +62,7 @@ static void
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/sk98lin/skge.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/sk98lin/skge.c b/drivers/net/sk98lin/skge.c
index 20890e4..eedcbeb 100644
--- a/drivers/net/sk98lin/skge.c
+++ b/drivers/net/s
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/starfire.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/starfire.c b/drivers/net/starfire.c
index c49214f..a67bac5 100644
--- a/drivers/net/starfire.c
+++ b/drivers/net/starfire.c
@@
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/sunhme.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/sunhme.c b/drivers/net/sunhme.c
index b4e7f30..beb0d27 100644
--- a/drivers/net/sunhme.c
+++ b/drivers/net/sunhme.c
@@ -3247,7 +
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/skfp/skfddi.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/skfp/skfddi.c b/drivers/net/skfp/skfddi.c
index 7cf9b9f..2a8386b 100644
--- a/drivers/net/skfp/skfddi.c
+++ b/drivers/net/skfp/sk
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
drivers/net/3c59x.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c
index 6f8e7d4..d2045d4 100644
--- a/drivers/net/3c59x.c
+++ b/drivers/net/3c59x.c
@@ -372,7 +372,7 @@
The definitions of struct pci_device_id arrays should generally follow
the same pattern across the entire kernel. This macro defines this
array as const and puts it into the __devinitconst section.
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
include/linux/pci.h |9 +
1
Sam Ravnborg wrote:
On Wed, Feb 20, 2008 at 01:53:36PM +0100, Jonas Bonn wrote:
The PCI_DEVICE_TABLE patch I sent earlier doesn't necessarily make
much sense by itself... here is a set of patches that apply
this macro, in turn moving a lot of this data into __devinitconst
which is discar
Sam Ravnborg wrote:
On Wed, Feb 20, 2008 at 02:27:19PM +0100, Jonas Bonn wrote:
Sam Ravnborg wrote:
On Wed, Feb 20, 2008 at 01:53:36PM +0100, Jonas Bonn wrote:
The PCI_DEVICE_TABLE patch I sent earlier doesn't necessarily make
much sense by itself... here is a set of patches that apply
to get this definition wrong in
the future...
Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
---
Documentation/pci.txt |6 --
include/linux/pci.h |9 +
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/Documentation/pci.txt b/Documentation/pci.txt
index 72
On 11 February 2013 15:07, Al Viro wrote:
> I'd suggest asking itanic folks; they do *not* put callee-saved stuff into
> sigcontext. AFAICS, they don't have setcontext() implemented as a syscall
> at all - it's done as sigprocmask() + doing to callee-saved registers what
> longjmp() does.
Just
ith a branch, it's in no-rebase mode as well. Branch
names are of form arch-, same as the last time around.
I tested the arch-openrisc branch and it looks good.
Acked-by: Jonas Bonn
/Jonas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
.
Gong Tao (1):
openrisc: mask interrupts in irq_mask_ack function
Jonas Bonn (2):
openrisc: PIC should act on domain-local irqs
openrisc: fix typos in comments and warnings
Kees Cook (1):
audit: define AUDIT_ARCH_OPENRISC
Vladimir Murzin (1
(2012-10-13
07:38:37 +0200)
OpenRISC UAPI disintegration work from David Howells.
David Howells (1):
UAPI: (Scripted) Disintegrate arch/openrisc/include/asm
Jonas B
On 13 October 2012 04:26, Steven Rostedt wrote:
> From: Steven Rostedt
>
> All the headers but kvm_para.h use the Kbuild infrastructure to
> get to the asm-generic headers.
>
> Cc: linux-kbu...@vger.kernel.org
> Cc: li...@lists.openrisc.net
> Cc: Jonas Bonn
> Si
On 13 October 2012 15:55, Steven Rostedt wrote:
> On Sat, 2012-10-13 at 08:32 +0200, Jonas Bonn wrote:
>> On 13 October 2012 04:26, Steven Rostedt wrote:
>> > Signed-off-by: Steven Rostedt
>>
>> Acked-by: Jonas Bonn
>
> Thanks Jonas,
>
> Would you
On 8 December 2012 08:44, Al Viro wrote:
> On Thu, Dec 06, 2012 at 10:09:55PM +, Al Viro wrote:
>> What we need to guarantee is
>> * restarts do not happen on signals caught in interrupts or exceptions
>> * restarts do not happen on signals caught in sigreturn()
>> * restart should happe
This fixes build error as gcc complains about a "section type conflict"
due to the const __devinitdata in sis190_get_mac_addr_from_apc().
---
drivers/net/sis190.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/sis190.c b/drivers/net/sis190.c
index b570402..e4
instead? Because AFAIK, const *and* __sectionmarker does not mix.
>
You're right... it's documented in linux/init.h that const and
__sectionmarker do not mix. The compile error is due to the use of
const and __section marker in the function sis190_get_mac_addr_from_apc().
--
To unsubscribe
This fixes build error as gcc complains about a "section type conflict"
due to the mixing of const and non-const data in same section.
---
drivers/net/sis190.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/sis190.c b/drivers/net/sis190.c
index b570402..f84
Mixing const and __section was previously not allowed. New __devinitconst tag
allows this.
This fixes a gcc "section type mismatch" build error.
---
drivers/net/sis190.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/sis190.c b/drivers/net/sis190.c
index
On 09/16/2016 04:43 PM, Stafford Horne wrote:
From: Stefan Kristiansson
OpenRISC was not an SMP architecture last I looked... did the relevant
spec updates get made? If not, NAK.
The issue is, the OpenRISC architecture shouldn't be a moving target
defined by what the kernel supports... th
. The default version will also descend nodes in the
match table such as "simple-bus" which should be fine as openrisc
doesn't have any of these (though it is preferred that memory-mapped
peripherals be grouped under a bus node(s)).
Signed-off-by: Rob Herring
Cc: Jonas Bonn
Signed-o
ich, for
all > practical purpose,
> would be the correct state right now.
+CC The openrisc list
Understood, I don't think we would want that to happen.
Look at the entry today:
OPENRISC ARCHITECTURE
M: Jonas Bonn
W: http://openrisc.net
S: Maintained
T: git
On 09/18/2016 05:22 PM, Guenter Roeck wrote:
On Wed, Apr 06, 2016 at 07:08:41PM +0900, Stafford Horne wrote:
Clearing out one todo item. This simplifies the boot process by using
the memblock api throughout the init process.
The old logic bootstrapped from memblock -> bootmem -> buddy allocator
On 09/16/2016 04:43 PM, Stafford Horne wrote:
From: Jonas Bonn
Return to userspace via _resume_userspace instead of via syscall return
path for the rt_sigreturn syscall.
I'll rework this comment more later, but this patch needs testing.
This whole patch was reworked later... what hap
NAK... this breaks other architectures.
The OpenRISC toolchain is broken with regard to this issue. Five years
ago (last I looked) nobody seemed interesting in fixing it. Has anything
changed here?
/Jonas
On 09/16/2016 04:42 PM, Stafford Horne wrote:
..From: Jonas Bonn
The syscall
define unveiled a bug in map_ram(),
where PTRS_PER_PGD was used when the intent was to iterate
over a set of page table entries.
This patch corrects that issue as well.
Signed-off-by: Stefan Kristiansson
Signed-off-by: Stafford Horne
Acked-by: Jonas Bonn
---
arch/openrisc/include/asm/pgtable
On 09/16/2016 04:43 PM, Stafford Horne wrote:
From: Christian Svensson
Historically OpenRISC GCC has reserved r10 which we now use to hold
the thread pointer for thread-local storage (TLS).
I know this was proposed by way of this patch, but we deferred accepting
this until the OpenRISC spec co
On 01/17/2018 08:59 AM, Daniel Wagner wrote:
Hi Neil,
On 01/16/2018 07:51 PM, Neil MacLeod wrote:
Since this commit in 4.15-rc8:
https://github.com/torvalds/linux/commit/6926e041a8920c8ec27e4e155efa760aa01551fd
building connman 1.35 with glibc 2.26 now fails as follows:
http://ix.io/EbP
On 01/17/2018 11:34 PM, Daniel Wagner wrote:
On 01/17/2018 11:20 PM, Hauke Mehrtens wrote:
Do we want to do any changes to the kernel header files? I do not know
of any clean workaround to make this work, we can probably hack
something for connman, but I think it is not worth the trouble.
Hi,
I have a question about the ordering of uevents, specifically concerning
complex USB devices that present multiple interfaces/functions.
Before KOBJ_BIND, a USB device would typically present itself as:
add usb_device
add usb_interface-1
add subsystem-device-1.0
add subsystem-device-1.1
a
Hi,
On 05/11/2018 14:21, Greg KH wrote:
On Mon, Nov 05, 2018 at 11:35:57AM +0100, Jonas Bonn wrote:
Hi,
I have a question about the ordering of uevents, specifically concerning
complex USB devices that present multiple interfaces/functions.
Before KOBJ_BIND, a USB device would typically
slave is unable to feed the SPI bus
fast enough even the SPI master runs at the lowest possible clock speed.
Jonas Bonn (2):
spi: support inter-word delay requirement for devices
spi-atmel: support inter-word delay
Documentation/devicetree/bindings/spi/spi-bus.txt | 1 +
drivers/spi/spi-at
If the SPI slave requires an inter-word delay, configure the DLYBCT
register accordingly.
Tested on a SAMA5D2 board (derived from SAMA5D2-Xplained reference
board).
Signed-off-by: Jonas Bonn
CC: Nicolas Ferre
CC: Mark Brown
CC: Alexandre Belloni
CC: Ludovic Desroches
CC: linux
fast enough to keep up with the SoC's SPI controller
even at the lowest bus speed.
This patch introduces the ability to specify a required inter-word
delay for SPI devices. It is up to the controller driver to configure
itself accordingly in order to introduce the requested delay.
Signed-off
On 25/01/2019 12:44, Jonas Bonn wrote:
If the SPI slave requires an inter-word delay, configure the DLYBCT
register accordingly.
Tested on a SAMA5D2 board (derived from SAMA5D2-Xplained reference
board).
Signed-off-by: Jonas Bonn
CC: Nicolas Ferre
CC: Mark Brown
CC: Alexandre Belloni
CC
Hi,
On 25/01/2019 12:53, Baolin Wang wrote:
Hi,
On Fri, 25 Jan 2019 at 19:44, Jonas Bonn wrote:
Some devices are slow and cannot keep up with the SPI bus and therefore
require a short delay between words of the SPI transfer.
The example of this that I'm looking at is a SAMA5D2 w
fast enough to keep up with the SoC's SPI controller
even at the lowest bus speed.
This patch introduces the ability to specify a required inter-word
delay for SPI devices. It is up to the controller driver to configure
itself accordingly in order to introduce the requested delay.
Signed-off
If the SPI slave requires an inter-word delay, configure the DLYBCT
register accordingly.
Tested on a SAMA5D2 board (derived from SAMA5D2-Xplained reference
board).
Signed-off-by: Jonas Bonn
CC: Nicolas Ferre
CC: Mark Brown
CC: Alexandre Belloni
CC: Ludovic Desroches
CC: linux
SPI slaves are so slow that they are unable to keep up even at the
SPI controller's lowest available clock frequency. I have such a
configuration where an AVR-based SPI slave is unable to feed the SPI bus
fast enough even the SPI master runs at the lowest possible clock speed.
Jonas Bonn (2):
rrevocable! Whether or not this actually belongs in the
mainline kernel is therefore up for debate...
Signed-off-by: Jonas Bonn
CC: Marek Vasut
CC: David Woodhouse
CC: Brian Norris
CC: Boris Brezillon
CC: Richard Weinberger
CC: linux-...@lists.infradead.org
---
drivers/mtd/mtdchar.c
On 25/01/2019 18:50, Mark Brown wrote:
On Fri, Jan 25, 2019 at 05:47:13PM +, Mark Brown wrote:
On Fri, Jan 25, 2019 at 01:06:45PM +0100, Jonas Bonn wrote:
Having this as device property rather than a transfer property allows this
to be configured one time in setup() rather than having
Hi Geert,
On 26/01/2019 11:25, Geert Uytterhoeven wrote:
Hi Jonas,
On Sat, Jan 26, 2019 at 8:53 AM Jonas Bonn wrote:
On 25/01/2019 18:50, Mark Brown wrote:
On Fri, Jan 25, 2019 at 05:47:13PM +, Mark Brown wrote:
On Fri, Jan 25, 2019 at 01:06:45PM +0100, Jonas Bonn wrote:
Having this
If the SPI slave requires an inter-word delay, configure the DLYBCT
register accordingly.
Tested on a SAMA5D2 board (derived from SAMA5D2-Xplained reference
board).
Signed-off-by: Jonas Bonn
CC: Nicolas Ferre
CC: Mark Brown
CC: Alexandre Belloni
CC: Ludovic Desroches
CC: linux
fast enough to keep up with the SoC's SPI controller
even at the lowest bus speed.
This patch introduces the ability to specify a required inter-word
delay for SPI devices. It is up to the controller driver to configure
itself accordingly in order to introduce the requested delay.
Signed-off
speed.
Jonas Bonn (2):
spi: support inter-word delay requirement for devices
spi-atmel: support inter-word delay
drivers/spi/spi-atmel.c | 18 +-
include/linux/spi/spi.h | 3 +++
2 files changed, 16 insertions(+), 5 deletions(-)
--
2.19.1
On 28/01/2019 12:47, Mark Brown wrote:
On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote:
On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn wrote:
spi-3wire: again, only set by MAXIM DS-1302 which always needs this
setting; driver could set this
For DS1302, this is probable
On 10/25/2013 04:37 PM, Geert Uytterhoeven wrote:
arch/openrisc/kernel/module.c: In function 'apply_relocate_add':
arch/openrisc/kernel/module.c:50:13: warning: assignment from incompatible
pointer type
arch/openrisc/kernel/module.c:54:13: warning: assignment from incompatible
pointer type
Mov
From: Richard Weinberger
Use the more generic functions get_signal() signal_setup_done()
for signal delivery.
Signed-off-by: Richard Weinberger
Signed-off-by: Jonas Bonn
---
Hi Richard,
What's the status of this patch series? Are these lined up for 3.13 already?
The changes look goo
On 11/06/2013 11:50 AM, Richard Weinberger wrote:
Am 06.11.2013 11:17, schrieb Jonas Bonn:
Patch looks good. :)
(But I didn't test it!)
OK, good. I'll take it via the OpenRISC tree then and you can drop it
from your V2 series.
Thanks,
Jonas
--
To unsubscribe from this list: sen
Hi Joe,
On 12/02/2013 06:48 AM, Joe Perches wrote:
(Adding Jonas Bonn to list as he added the macro in the first place...)
Thanks... ;)
Actually, I think I submitted an even uglier macro called
DECLARE_PCI_DEVICE_TABLE... might have been the first kernel patch I
ever sent? In any case, it
1 - 100 of 165 matches
Mail list logo
