On Wed, Dec 02, 2009 at 09:36:58AM +0100, Aurelien Jarno wrote:
> On Sun, Nov 15, 2009 at 08:53:55PM +0900, Magnus Damm wrote:
> > This is V2 of the QEMU sh4 host support patch.
> >
> > The code is of a somewhat experimental nature, which means that
> > only the bare essentials are in place. The s
This adds trivial support for the R2D-PLUS FPGA, mostly just for the
versioning information that the kernel uses for IRL mappings, in addition
to handling the heartbeat and poweroff writes.
Signed-off-by: Paul Mundt <[EMAIL PROTECTED]>
---
hw/r2d.c
btype specific registers like
MMU_PTEA and to set up feature bits in line with the kernel probing for
things like conditionalizing FPU/DSP context.
Signed-off-by: Paul Mundt <[EMAIL PROTECTED]>
---
hw/sh7750.c| 42 -
target-sh4/cpu.h
On Fri, Nov 30, 2007 at 05:15:21PM +, Paul Brook wrote:
> On Friday 30 November 2007, Carlo Marcelo Arenas Belon wrote:
> > On Fri, Nov 30, 2007 at 04:28:09PM +, Paul Brook wrote:
> > in the sh4 specific case, it doesn't make sense for sh4 to print an access
> > error to a physical address
On Thu, Nov 29, 2007 at 06:18:32PM +0900, Magnus Damm wrote:
> On Nov 29, 2007 2:55 PM, Paul Mundt <[EMAIL PROTECTED]> wrote:
> > The T-state check for bt/bf happens _prior_ to execution of the delay
> > slot instruction, while any delay-slot resident T-bit modifier is
> &
On Thu, Nov 29, 2007 at 02:43:03PM +0900, Magnus Damm wrote:
> On Nov 28, 2007 9:49 PM, Paul Mundt <[EMAIL PROTECTED]> wrote:
> I was mainly wondering if I really needed to save the state of SR_T,
> but I assumed so. So the code should be correct. And yes, I'm sure
>
On Wed, Nov 28, 2007 at 06:54:20PM +0900, Magnus Damm wrote:
> +#define DELAY_SLOT_TRUE(1 << 2)
> +#define DELAY_SLOT_CLEARME (1 << 3)
> +/* The dynamic value of the DELAY_SLOT_TRUE flag determines whether the jump
> + * after the delay slot should be taken or not. It is calculated from
On Wed, Nov 21, 2007 at 05:16:55PM +0900, Magnus Damm wrote:
> +#define MOVW(n) (0x9300|((n)-2)) /* Move mem word at PC+n to R3 */
> +#define TRAP_NOARG 0xc310 /* Syscall w/no args (NR in R3) SH3/4 */
> +#define OR_R0_R0 0x200b /* or r0,r0 (insert to avoid hardware bug)
> */
Thi
On Wed, Jul 04, 2007 at 01:19:07PM +0900, Magnus Damm wrote:
> On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
> >Can you also provide a regression test like some of the other targets
> >have? It would be very useful to detect breakage.
>
> Sure, what about the attached hello-sh4 test patch?
