On 28 April 2016 at 14:17, Arnd Bergmann wrote:
> One simple (from the kernel's perspective, not from the JIT) approach
> might be to always use MAP_FIXED whenever an allocation is made for
> memory that needs these special pointers, and then manage the available
> address space explicitly. Would
On 2 November 2014 13:34, Ben Gras wrote:
> A few months of work sounds like a bit much to take on as a side project at
> this point, and I have a few already, so no promises. But I am interested in
> hearing where the first thread is to start pulling at, so to speak.
The major problem is simply
On 1 November 2014 23:15, Ben Gras wrote:
> My question is: is Linaro planning to upstream the bbxm code to stock qemu?
>
> Having a single qemu would simplify life for us.
Upstreaming that code is something we would in theory like
to do, but it is quite a lot of work required to clean it
up to t
On 17 June 2014 15:07, Jon Medhurst (Tixy) wrote:
> Yes, it's damned annoying as we've found out in the past, but I believe
> it's a 'feature', a per subscriber option unless I've got mixed up...
>
> Avoid duplicate copies of messages?
>
> When you are listed explicitly in the To:
On 1 April 2014 01:35, Michael Casadevall wrote:
> Its a fairly major improvement, and I managed to use GdbSyms.dll to
> load ALL the symbol files in a single go, but I'm still having issues
> with the stack. At least now i can get the frame we're currently in
> reliably, but the backtrace remains
On 31 March 2014 23:07, Michael Casadevall
wrote:
> On 03/28/2014 07:40 PM, Peter Maydell wrote:
>> There's a bug in QEMU's AArch64 KVM support which means we don't
>> do the right thing with SP on syncing state to/from the kernel, so
>> don't trust that
On 28 March 2014 19:38, Michael Casadevall
wrote:
> On 03/28/2014 02:09 PM, Christoffer Dall wrote:
>> On Fri, Mar 28, 2014 at 04:26:59AM -0400, Michael Casadevall
>> wrote:
>>> Previous attempts to debug assets shows that EFI does "odd"
>>> things to the stack when we hit an exception, making wal
On 27 February 2014 13:20, Michael Matz wrote:
> On Wed, 26 Feb 2014, Dann Frazier wrote:
>> I've narrowed down the changes that seem to prevent both types of
>> segfaults to the following changes that introduce a wrapper around
>> sigprocmask:
>>
>> https://github.com/susematz/qemu/commit/f1542ae
On 10 March 2014 19:15, Daniel Lipsitt wrote:
>
> On Mar 10, 2014, at 10:28 AM, Rob Herring wrote:
>
> Well, highbank does not support SD, but that's not your issue. Where's
> your dtb and kernel?
>
>
> It's inside the pre-built image here:
> http://releases.linaro.org/14.01/ubuntu/highbank/
>
>
On 10 March 2014 11:28, Alex Bennée wrote:
>
> Peter Maydell writes:
>
>> On 9 March 2014 23:37, Dann Frazier wrote:
>>> Also - I've found an issue with running OpenJDK in the latest upstream git:
>>>
>>> root@server-75e0210e-4f99-4c86-
On 9 March 2014 23:37, Dann Frazier wrote:
> Also - I've found an issue with running OpenJDK in the latest upstream git:
>
> root@server-75e0210e-4f99-4c86-9277-3201ab7b6afd:/root# java
> #
> [thread 274902467056 also had an error]# A fatal error has been
> detected by the Java Runtime Environment
On 28 February 2014 17:08, Alex Bennée wrote:
>
> Peter Maydell writes:
>
>> On 28 February 2014 14:27, Alexander Graf wrote:
>>> Could we check the instruction at the sognaling pc and check
>>> if it's a known syscall instruction? No need to replace glib
On 28 February 2014 14:27, Alexander Graf wrote:
> Could we check the instruction at the sognaling pc and check
> if it's a known syscall instruction? No need to replace glibc
> wrappers then.
No, because the behaviour we want for "started handling
syscall in qemu" through to "PC anything up to b
On 28 February 2014 14:12, Alex Bennée wrote:
> Is this "simply" a case of having a precise state in/around syscalls?
No.
> AIUI we already have such a mechanism for dealing with faults in
> translated code so this is all aimed at when an asynchronous signal
> arrives somewhere in QEMU's own cod
On 25 February 2014 13:33, Michael Matz wrote
> The biggest road-block is that signal vs syscall handling is
> fundamentally broken in linux-user and it's unfixable without
> assembler implementations of the syscall caller.
I'm not entirely sure it's possible to fix even with
hand-rolled assembly
On 11 February 2014 16:24, Nicolas Dechesne wrote:
> Le 11 févr. 2014 09:18, "Wookey" a écrit :
>> Hangout audio and video is regularly broken for people which causes
>> general aggravation for people in meetings.
> What kind of problems do you observe?
I see a fair bit of "oops, my audio was m
On 6 January 2014 19:46, Ryan Harkin wrote:
> Hello,
>
> I'm trying to fire up an ARM fastmodel using a virtio block device rather
> than the emulated MMC block device.
>
> UEFI is reading the kernel & DTB off the virtio device, so I know the device
> is present.
> So far, I don't see any vda dev
On 28 November 2013 07:54, Ryan Harkin wrote:
> On 27 November 2013 19:13, Peter Maydell wrote:
>> Christopher is advocating that somebody should fix the boot
>> wrapper, so you have a single trivial .axf file which doesn't include
>> the kernel at all
>> I e
On 27 November 2013 18:27, Wookey wrote:
> +++ Christopher Covington [2013-11-27 11:17 -0500]:
>> In my opinion, the nicer solution is to port the semihosting boot wrapper to
>> 64-bit. We've done that internally, but don't currently have approval to
>> share
>> that work. It's not too difficult
On 27 November 2013 15:07, Christopher Covington wrote:
> Are there instructions for running this stuff on QEMU?
There's no 64 bit system emulation support in QEMU just yet, so
the first item in the instructions is "1. wait until end of Q1 2014" :-)
> By the way I find the terminology of "AXF" v
On 6 November 2013 13:05, Ard Biesheuvel wrote:
> Well, to be honest, my primary motivation for posting it to the list
> was so I could refer to it from the JIRA issue you told me about
> yesterday, but I would be happy to fix these minor issues and do a
> proper submission as well. However, consi
On 6 November 2013 11:22, Ard Biesheuvel wrote:
> This adds support for the AESE/AESD/AESMC/AESIMC instructions that
> are available on some v8 implementations of Aarch32.
Thanks for this patch. Please could you send QEMU patches to
qemu-de...@nongnu.org? (we do all our work on upstream qemu
and
On 8 August 2013 12:05, Andy Green wrote:
> I can see how to get it from the flat device tree by adding properties
> to chosen { } and riding on early_init_dt_scan_chosen() easily enough.
> From the results I have already I know on this platform that's ~500us
> after where we set it up at the mom
On 8 August 2013 11:23, Andy Green wrote:
> On 8 August 2013 17:35, Peter Maydell wrote
>> Can't you put the relevant information into the device tree
>> so that it works on multiplatform kernels? That's the way
>> the kernel's chosen to store its "this
On 8 August 2013 03:44, Andy Green wrote:
> These patches give accurate, monotonic timestamps from the very first log
> entry allowing insight into where the time is going during the whole of
> the boot process.
>
> It's a debug feature like DEBUG_LL, it does not cooperate with
> ARCH_MULTIPLATFOR
On 2 August 2013 01:14, Andy Green wrote:
> On 2 August 2013 07:38, Peter Maydell wrote:
>> x86 manages to do much better here because the "everything
>> looks like a PC" effect means it's much easier for the kernel
>> to produce output to serial or vide
On 2 August 2013 00:26, Andy Green wrote:
> On 2 August 2013 01:46, Jon Medhurst (Tixy) wrote:
>> with vexpress we have the added complication thrown into the mix that
>> people use it a lot with QEMU ;-)
>
> ...if there's something special needed for QEMU, maybe the fragments
> are the right ans
On 1 August 2013 09:30, Ryan Harkin wrote:
> The vexpress defconfig has always been broken.
...maybe we could fix it?
-- PMM
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On 23 July 2013 12:33, Grant Likely wrote:
> Historically each ARM SoC did its own thing for secondary CPU startup.
> New platforms are expected to use the PSCI spec (which unfortunately
> isn't an open document, but ARM partners can get access).
>
> http://infocenter.arm.com/help/index.jsp?topic=
On 20 June 2013 22:56, Deepak Saxena wrote:
> On 19 June 2013 20:32, Viresh Kumar wrote:
>> Please use linaro-kernel list for sending patches.
> I think linaro-kernel should be part of the cc, but I don't
> think that there is any policy in regards to not sending patches
> to linaro-dev.
We had
On 4 June 2013 16:54, David Long wrote:
> $ qemu-system-arm -version
> QEMU emulator version 1.4.0 (Debian 1.4.0+dfsg-1expubuntu4), Copyright (c)
> 2003-2008 Fabrice Bellard
>
>
> So my QEMU may be stale, and that may explain why now I get:
>
> clcd-pl11x: probe of 1002.clcd failed with error
On 4 June 2013 09:10, Jon Medhurst (Tixy) wrote:
> On Tue, 2013-06-04 at 00:07 -0400, David Long wrote:
>> I'm trying to build for versatile express to run under QEMU. When I
>> boot under QEMU I get errors regarding the SD voltage, and it fails.
> I've never really tried using QEMU so don't hav
On 17 May 2013 11:11, Wookey wrote:
> +++ Mian M. Hamayun [2013-05-16 14:25 +0200]:
>> I am reposting the following message to linaro-dev as I am using the
>> following linaro toolchain for ARM64 cross-compilation:
>> https://wiki.linaro.org/HowTo/BuildArm64Kernel
>>
>> In fact, I am trying to com
Hi; does anybody else think it would be a good idea to move all
the kernel patch email traffic off linaro-dev and onto a more
kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev
shows that something like 75% of it is kernel dev
On 24 January 2013 14:38, Alexander Graf wrote:
> But check out the QEMU e500 machine. We have a fully device tree
> based machine type in the kernel. QEMU drives it by generating a
> device tree for devices it actually exposes on the fly.
The ARM equivalent for that would be mach-virt, I think
(
On 8 January 2013 15:57, Richard Henderson wrote:
> On 01/08/2013 04:08 AM, Peter Maydell wrote:
>> The translator sources (as and when we implement a
>> TCG QEMU target for this) should live under the existing target-arm.
>
> Of this I'm not certain, given that A64 is
On 8 January 2013 12:24, Anup Patel wrote:
> On 8 January 2013 17:38, Peter Maydell wrote:
>> Also, I suspect this isn't the only thing that will be required.
> Yes. This patch only tries to make sure that the configure step falls
> through and at-least QEMU cross-compi
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
>fi
> elif check_define __arm__ ; then
>cpu="arm"
> +elif check_define __aarch64__ ;
On 7 January 2013 13:47, Dave Martin wrote:
> On Thu, Dec 20, 2012 at 12:23:48PM +, Jon Medhurst (Tixy) wrote:
>> Does anyone have any further outstanding concerns or comments about my
>> proposed patch?
>
> Since this doesn't seem to be merged yet, I'll just comment that this
> all looks sens
On 18 December 2012 16:42, Alexander Spyridakis
wrote:
> On 18 December 2012 12:10, Liviu Dudau wrote:
>> If you have BootMonitor, it is already capable of booting the kernel.
> The major difference is that BootMonitor doesn't initialize Hyp mode and
> without it we can't start KVM.
It would be
f-by: Jon Medhurst
Reviewed-by: Peter Maydell
I've applied this patch and the arch-timers fix to the linaro
boot-wrapper git repo.
-- PMM
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On 4 December 2012 16:01, Peter Maydell wrote:
> Er, this patch doesn't apply at all to the kvm bootwrapper.
Whoops, false alarm due to failure to drive git properly
(was on an ancient branch).
Reviewed-by: Peter Maydell
-- PMM
___
li
On 30 November 2012 15:30, Jon Medhurst (Tixy) wrote:
> From: Will Deacon
>
> We need to set the flags when checking the feature register.
>
> Signed-off-by: Will Deacon
> ---
>
> I found this patch in another fork of the bootwrapper and it looks like
> something we should have. On the A15 and b
On 9 October 2012 14:06, Dave Martin wrote:
> On Tue, Oct 09, 2012 at 01:31:55PM +0100, Peter Maydell wrote:
>> Patch 2 made git complain about trailing whitespace in one place
>> but I'll just zap that in passing when I apply these.
>
> Thanks
>
>> Dave,
ctor out parsing of fdt #address-cells
> [PATCH v2 3/3] bootwrapper: Initialise CCI device if found in the
All:
Reviewed-by: Peter Maydell
and tested that the KVM boot is still OK.
Patch 2 made git complain about trailing whitespace in one place
but I'll just zap that in passing when I apply th
On 26 September 2012 18:08, Jon Medhurst (Tixy) wrote:
> On Wed, 2012-09-26 at 16:01 +0100, Peter Maydell wrote:
>> The patch has added an 'enter_hyp'
>> call into the chunk of code which is relocated to some random
>> address, which means the code is now too long
On 26 September 2012 15:12, Peter Maydell wrote:
> On 26 September 2012 14:37, Peter Maydell wrote:
>> On 6 September 2012 18:12, Dave Martin wrote:
>>> Signed-off-by: Dave Martin
>>
>> This patch causes the kernel to get stuck at "Calibrating delay lo
On 26 September 2012 14:37, Peter Maydell wrote:
> On 6 September 2012 18:12, Dave Martin wrote:
>> Signed-off-by: Dave Martin
>
> This patch causes the kernel to get stuck at "Calibrating delay loop...".
>
> I'm not sure why this happens (investigating) but
On 6 September 2012 18:12, Dave Martin wrote:
> Signed-off-by: Dave Martin
This patch causes the kernel to get stuck at "Calibrating delay loop...".
I'm not sure why this happens (investigating) but if I move the
enter_hyp macro call back to where it used to be (leaving the rest of
the patch in
On 20 September 2012 10:33, Lei Wen wrote:
> However, the A15x4_A7x4 model is running quit slow for launching the kernel,
> about 1minute to showing the kernel booting screen. Whereas A15x1 model is
> launching quite fast, just in several seconds.
This is in general not very surprising, since the
On 4 September 2012 15:57, Jon Medhurst (Tixy) wrote:
> The semihosting and FDT code makes use of libc style string
> functions implemented in our string.c, however it relies of the system
> providing the string.h header file.
>
> This causes problems on toolchains that don't provide these headers
On 4 September 2012 16:10, Peter Maydell wrote:
> I guess to be fully consistent we should provide our own
> stddef.h and stdint.h, but if it's not causing problems it's
> not worth the effort.
Actually, I'm wrong there. We're using gcc's -ffreestanding so
it
onst *p2, size_t n);
> +extern int (strcmp)(char const *s1, char const *s2);
> +extern int (strncmp)(char const *s1, char const *s2, size_t n);
> +extern char *(strchr)(char const *s, int c);
> +
> +#endif
> --
> 1.7.10.4
Reviewed-by: Peter Maydell
-- PMM
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On 6 July 2012 20:26, Dave Martin wrote:
> On Fri, Jul 06, 2012 at 07:07:35PM +0100, Peter Maydell wrote:
>> On 6 July 2012 00:27, Rob Herring wrote:
>> > I would just change arm_add_memory to use phys_addr_t for the size
>> > param. This ultimately calls memblock func
On 6 July 2012 00:27, Rob Herring wrote:
> I would just change arm_add_memory to use phys_addr_t for the size
> param. This ultimately calls memblock functions which use phys_addr_t
> for sizes.
So I have a patch that does this which basically works. However
there is a bit I'm not sure about. arm
On 6 July 2012 00:27, Rob Herring wrote:
> On 07/05/2012 11:48 AM, Peter Maydell wrote:
>> void __init early_init_dt_add_memory_arch(u64 base, u64 size)
>> {
>> + while (size > 0x8000) {
>> + arm_add_memory(base, 0x8000);
>&
Device tree memory regions may have sizes larger than 4GB.
Instead of silently truncating a 64 bit size when we pass it
to arm_add_memory(), split large regions into 2GB chunks.
Signed-off-by: Peter Maydell
---
With this patch, I can take a device tree which has been tweaked
so its #address
On 24 June 2012 20:28, Marcin Juszkiewicz wrote:
> W dniu 22.06.2012 22:01, Arjan van de Ven pisze:
>> being arm or not is completely irrelevant in this regard.
>> (and there will undoubtedly ARM systems at some point that will have PCI
>> in them)
>
> Already there are ARM devices with PCI(e) sup
On 10 May 2012 23:34, Ricardo Salveti wrote:
> On Thu, May 10, 2012 at 3:30 PM, Alexander Sack wrote:
> Linaro-dev is used for development related discussion, and it's the
> first most folks first subscribe to. I don't have the current number
> of folks participating at this list, but I'd prefer
On 12 April 2012 16:22, Russell Keith Davis wrote:
> The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian
> rootfs & qemu-linaro is that i pulled a newer version than march 30th and i
> went from some expected errors http://pastebin.com/QTt8S9kT to
> http://pastebin.com/2SR
On 12 April 2012 17:08, Russell Keith Davis wrote:
> On 4/12/2012 11:47 AM, Peter Maydell wrote:
>> If you can provide me with an easy way to reproduce this on my machine
>> I can have a look at it.
>
>
> I don't actually use qemu on "real" hardware so not
On 12 April 2012 16:22, Russell Keith Davis wrote:
> The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian
> rootfs & qemu-linaro is that i pulled a newer version than march 30th and i
> went from some expected errors http://pastebin.com/QTt8S9kT to
> http://pastebin.com/2SR
On 9 April 2012 20:13, John Stultz wrote:
> So the Google Android team just posted this:
> http://feedproxy.google.com/~r/blogspot/hsDu/~3/OCt1AQzfyWI/faster-emulator-with-better-hardware.html
>
> Which shows their device emulator running w/ hardware acceleration. Since I
> know they started with
On 22 March 2012 19:31, Dave Martin wrote:
> Now I've had a chance to look into this, it seems that the plague of
> question marks actually seems to arise out of an interaction between
> Mutt and my unusual locale settings. Basically if your locale settings
> don't support the no-breaking space c
2012/3/15 周春华 :
> Dear Peter Maydell,
>
> Thank you for your help. I got an idea to log the guest physical address,
> would you mind help me to check it?
>
> Because the function tcg_out_qemu_ld() and tcg_out_qemu_st() know the guest
> virtual address should be accessed, we c
2012/3/15 周春华 :
> Peter Maydell wrote:
>> Note that there are other slow paths for memory access which don't
>> use the TLB and instead do go via physical addresses at the time
>> they need to do the load/store.
>
> I want to know how to use these slow path
2012/3/15 周春华 :
> Do you means that the QEMU TLB maps the guest virtual address to host
> virtual address,
Yes.
> and the begging and end virtual addresses of the memory
> allocated for RAM device emulating are the RAM physical begging and end
> address from guest view?
I don't know what you mea
On 14 March 2012 14:01, 周春华 wrote:
> I got a job that should log the RAM memory access in the QEMU. First, I
> should find out the code line in QEMU to trap all RAM memory access. After
> some efforts, I have some conclusions:
>
> 1. I have found the function dealing with the translation from the
On 29 February 2012 13:25, Vishal Bhoj wrote:
> On 29 February 2012 12:33, Guruswamy, Senthilvadivu wrote:
>> Which RTSM_EB are you using for this bring up?
>> FastModel comes with only RTSM_VE of A15,A7 pack which has only cores
>> simulated, not even uart in it.
>>
> I am starting with fastmode
On 27 February 2012 16:27, Ian Campbell wrote:
> R12 is not accessible from the 16 bit "T1" Thumb encoding of mov
> immediate (which can only target r0..r7).
>
> Since we support only ARMv7+ there are "T2" and "T3" encodings available
> which do allow direct mov of an immediate into R12, but are 3
Hi; I'm hoping somebody will be willing to run a test kernel
for me on some omap boards and send me the dmesg output.
(I'm trying to sort out QEMU's modelling of the OMAP ID
registers and the TRMs are rather unhelpful; in particular
the OMAP35x TRM claims that there are two overlapping registers
at
On 21 February 2012 20:55, John Rigby wrote:
> Forwarding to all after I realized my answer only went to Peter:
> That manifest entry points to the u-boot-tools package which is
> userland package containing mkimage so not really what you want.
>
> Your email reminds me we need to do this better l
Hi. I'm trying to track down the sources that made the U-Boot and
U-Boot SPL for the beagle 1201 release image:
http://releases.linaro.org/images/12.01/oneiric/nano/
sources.txt says that's this hwpack:
http://releases.linaro.org/12.01/ubuntu/oneiric-hwpacks/
but the manifest.txt there:
http://
On 20 February 2012 16:42, Zach Pfeffer wrote:
> During ELC a few people asked me if Linaro had something bigger than
> nano and smaller than Ubuntu that they could use to build stuff.
Nano and then install the packages you actually need on top of that?
-- PMM
__
On 9 February 2012 00:50, Fathi Boudra wrote:
> Same result.
>
> Debug info from gdb:
>
> qemu: Unsupported syscall: 26
> ptrace: Function not implemented.
> No threads.
This bit of the log is uninteresting, because it is mono attempting
to automatically capture a backtrace. As Alex says, this do
On 4 February 2012 02:39, Peter Maydell wrote:
> On 3 February 2012 22:19, Tom Gall wrote:
>> The last time I checked into it (last november, early december) it was
>> the post install scripts involving a number of different mono
>> packages. It's really easy to
On 3 February 2012 22:19, Tom Gall wrote:
> The last time I checked into it (last november, early december) it was
> the post install scripts involving a number of different mono
> packages. It's really easy to replicate. As Peter kindly suggested,
> time to revisit with the new version and author
On 3 February 2012 15:43, Tom Gall wrote:
> Thanks much for getting this fixed Peter. Perhaps at LC you might like
> to see another qemu issue that keeps us from being able to cross build
> the Linaro Ubuntu LEB.
Sure; or you can always reach me via the bug tracking system :-)
-- PMM
__
On 21 January 2012 12:04, Peter Maydell wrote:
> $0 here is the process name, and Perl is trying to set it using
> prctl(PR_SET_NAME, ...). [Google says it's done that only since
> Perl 5.14.] I think you're running under QEMU at this point, and
> QEMU doesn't suppor
On 2 February 2012 08:28, Mattias Backman wrote:
> On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti
> wrote:
>> 4 - Do you know if a similar page, but for a team, will also be available?
>
> There will be. Guilherme has circulated a mockup for that too, on the
> techleads list.
Is there going to
On 27 January 2012 10:30, Pawel Moll wrote:
> I'm planning to modify the boot.S to be able to create an AXF file from
> separate kernel and DTB (will happen next week, if anyone wants to try
> it let me know and I'll notify you when it's ready)
I would suggest you start out with the patches I did
On 26 January 2012 20:19, Zygmunt Krynicki wrote:
> About device trees, does the simulator need an explicitly provided
> device tree (in a way we currently provide the kernel image and
> ramdisk) or is the dt table built into the image?
The simulator doesn't care whether you're using device tree
On 26 January 2012 16:26, Zach Pfeffer wrote:
> Looks like getting a big cloud instance running may help. Is the
> simulator I/O or compute bound?
It is typically compute bound (unless you're short on RAM: 6GB
the figure I've been bandying around as a plausible minimum).
With rate limiting enable
On 21 January 2012 10:08, Zygmunt Krynicki wrote:
> On Fri, Jan 20, 2012 at 10:40 PM, Matt Waddel wrote:
>> I: create linaro user
>> Can't set $0 with prctl(): Bad address at /usr/sbin/adduser line 86.
>>
>> Here is the perl code around line 86 in adduser:
>>
>> my %config;
On 16 January 2012 18:43, Andrei Gherzan wrote:
> Is there any cortex a15 board emulated in linaro?
You don't say specifically but I'm going to assume you mean
"in qemu-linaro".
I'm working on a patchset for the Versatile Express A15 board.
This is currently in the "upstream review" stage. There
On 11 January 2012 15:12, Andrei Gherzan wrote:
> -M vexpress-a9 -hda
> /home/xxx/work/yyy/yocto/2012-01-08-14-57/tmp/deploy/images/image-qemuarmv7.ext3
vexpress-a9 does not support hard disks, so -hda won't work.
Use -drive if=sd,cache=writeback,filename=/path/to/disk.img
instead, to set up an
On 14 December 2011 14:46, Jon Medhurst (Tixy) wrote:
> On Wed, 2011-12-14 at 15:38 +0100, Danilo Šegan wrote:
>> We should be back up, with everything ready to go. Do note that the ssh
>> key has changed, so you will be prompted with warning notices about
>> that.
> So all peoples personal git
On 8 December 2011 01:22, Ricardo Salveti wrote:
> What I just didn't understand much is the relation with
> git.linaro.org, as now it sees we have 2 official git hosting places
> for projects. I know that technically using github is a lot easier, as
> setting up a git repository at git.linaro.org
On 6 December 2011 10:34, Jon Medhurst (Tixy) wrote:
> On Mon, 2011-12-05 at 17:47 +, Stephen Doel wrote:
>> ** Following feedback at previous Linaro Connect events, the registration
>> process now includes a) registration on Launchpad so you only have to go
>> through the registration process
e testing
Does that seem reasonable or would another approach be better?
(OMAP3/Beagle model maintenance is at a very low priority anyway
so it wouldn't be a major change to go to "officially not working
on it". Actually dropping the OMAP3 patchset from qemu-linaro
would be a
On 23 November 2011 09:05, Peter Maydell wrote:
> On 23 November 2011 00:48, Michael Hudson-Doyle
> wrote:
>> I've been working on testing images under QEMU with the lava-dispatcher
>> (mostly this is preparation for testing A15 using a fast model, but it's
>>
On 23 November 2011 00:48, Michael Hudson-Doyle
wrote:
> I've been working on testing images under QEMU with the lava-dispatcher
> (mostly this is preparation for testing A15 using a fast model, but it's
> interesting in its own right too).
Ah, this is cool, more automated testing of QEMU would d
On 22 November 2011 16:58, Fathi Boudra wrote:
> Since most people will be on holidays, we have a modified schedule for
> December
> "Christmas" release. The current plan is to release one week earlier:
>
> * 2011-12-08 Toolchain WG 2011.12 release
> * 2011-12-15 Components 2011.12 release
> * 20
On 7 October 2011 13:16, Fathi Boudra wrote:
> On 7 October 2011 15:06, Peter Maydell wrote:
>> On 7 October 2011 11:23, Alexander Sack wrote:
>>> Also, it strikes me that we only use snapshots.linaro.org for ubuntu
>>
>> Eh? snapshots has more than just the ubun
On 7 October 2011 11:23, Alexander Sack wrote:
> Also, it strikes me that we only use snapshots.linaro.org for ubuntu
Eh? snapshots has more than just the ubuntu desktop images -- it
has nano, alip, hwpacks and all the rest. I think calling it
"ubuntu-build" would be rather confusing...
> 1. mo
On 6 September 2011 16:09, Andy Doan wrote:
> On 09/05/2011 11:35 AM, Christian Robottom Reis wrote:
>> On Sat, Sep 03, 2011 at 09:10:58PM +0800, Jim Huang wrote:
>>> 2011/9/3 Tom Gall :
Is a method via the aux vectors to know at runtime if neon is or is
not present?
>>>
>>> hi Tom,
>>>
On 5 September 2011 10:52, Marcin Juszkiewicz
wrote:
> W dniu 05.09.2011 11:28, Andrew Stubbs pisze:
>> Next question ... is /proc/cpuinfo really the best way to detect this?
>>
>> I mean, is auxv a better approach? Or something else? What's the most
>> efficient, and most stable API to read the C
On 19 July 2011 15:40, James Westby wrote:
> On Tue, 19 Jul 2011 15:07:15 +0100, Peter Maydell
> wrote:
>> I ran into this again today. It looks like you're right and ppa kernel builds
>> don't have ddebs. Is it possible to fix this? Trying to debug something
>&g
On 9 June 2011 21:57, James Westby wrote:
> On Thu, 9 Jun 2011 11:24:38 +0100, Peter Maydell
> wrote:
>> [ddeb packages for linaro kernels]
> I wasn't even aware that our kernel ppa builds ddebs (or even could).
I ran into this again today. It looks like you're ri
On 11 July 2011 09:42, David Gilbert wrote:
> On 11 July 2011 09:36, Dave Martin wrote:
>> On Sat, Jul 09, 2011 at 12:29:01AM +0100, Peter Maydell wrote:
>>> QEMU supports calls into the fixed vector page (it just special cases
>>> attempts to execute at addresses >
1 - 100 of 152 matches
Mail list logo
