-32bit,
Signed-off-by: Anup Patel
---
arch/arm64/kernel/early_printk.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm64/kernel/early_printk.c b/arch/arm64/kernel/early_printk.c
index 7e320a2..c39e90b 100644
--- a/arch/arm64/kernel/early_printk.c
+++ b/arch
On 1 March 2013 13:47, Marc Zyngier wrote:
>
> On Fri, 1 Mar 2013 11:30:26 +0530, Anup Patel
> wrote:
> > This patch adds support for using earlyprintk with 8250/16550 UART
> ports.
> >
> > The 8250/16550 UART can either have 8-bit or 32-bit aligned registers
&g
-16bit,
Signed-off-by: Anup Patel
---
arch/arm64/kernel/early_printk.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm64/kernel/early_printk.c b/arch/arm64/kernel/early_printk.c
index 7e320a2..d57f300 100644
--- a/arch/arm64/kernel/early_printk.c
+++ b/arch
On Thu, Jan 24, 2013 at 8:08 PM, Alexander Graf wrote:
>
> On 24.01.2013, at 10:25, Stefan Hajnoczi wrote:
>
> > On Thu, Jan 24, 2013 at 11:40:24AM +0530, Anup Patel wrote:
> >> IMHO, If we have something like Virtio-desktop specification then all
> >> possible g
On 24 January 2013 14:55, Stefan Hajnoczi wrote:
> On Thu, Jan 24, 2013 at 11:40:24AM +0530, Anup Patel wrote:
> > IMHO, If we have something like Virtio-desktop specification then all
> > possible guest OSes can have support for it and different hypervisor can
> > emulat
Hi All,
How about having a generic Virtio-based machine for emulating a virtual
desktop ?
I know folks have already thought about this and probably also tried
something or other on this front but, it will be good to know the downsides.
Virtio-desktop can be a separate specification describing a
name (ie what comes out in the
qemu-foo and qemu-system-foo binary names) we generally use
the same name that 'uname -m' produces on those machines. In
this case that would be "aarch64".
Signed-off-by: Anup Patel
---
configure |5 +
1 file changed, 5 insertions(+)
diff
On 8 January 2013 17:38, Peter Maydell wrote:
> On 8 January 2013 11:05, Anup Patel wrote:
> > diff --git a/configure b/configure
> > index fe18ed2..0bfb8bb 100755
> > --- a/configure
> > +++ b/configure
> > @@ -366,6 +366,8 @@ elif check_define __s390__ ; then
We should be able to cross compile QEMU for ARM64 host.
This is required for trying out ARM 32-bit guest on ARM64 host using QEMU + KVM
ARM64.
Signed-off-by: Anup Patel
---
configure |5 +
1 file changed, 5 insertions(+)
diff --git a/configure b/configure
index fe18ed2..0bfb8bb
Hi Marc,
We tried kvm-arm64/soc-armv8-kvm branch from your git tree on v8 Foundation
Model but we dont get any prints on serial terminal.
We followed the step mentioned in
https://wiki.linaro.org/HowTo/BuildArm64Kernel except:
1. We used kernel compiled from kvm-arm64/soc-armv8-kvm branche from y
Hi all,
I wanted to know how Xen-ARM for A15 will address following concerns:
- How will Xen-ARM for A15 support legacy guest environment like ARMv5 or
ARMv6 ?
- What if my Cortex-A15 board does not have a GIC with virtualization
support ?
Best Regards,
Anup Patel
On Wed, Nov 30, 2011 at 2:59
11 matches
Mail list logo