Displaying 8 results from an estimated 8 matches for "archlinuxarm".
2012 Apr 15
3
[LLVMdev] About LLVM 3.1 ARM testing
> Ubuntu on ARM is softfp, right? How about testing hardfp with a
> distribution like ArchLinuxArm?
Yes, Ubuntu on ARM is softfp. But I already told Bill the platform I prepare
to test and the testing day begins *tomorrow*, I prefer what it likes now. BTW,
what if I use a cross compiler with hardfp enabled to compile LLVM first, then
run it on Ubuntu/ARM? Does it achieve your goal, too?
Rega...
2012 Apr 14
0
[LLVMdev] About LLVM 3.1 ARM testing
...d
> on the ML before, I plan to cross compile LLVM/Clang first, then run
> regression
> test and test suite on the pandaboards. Could someone help me check to see
> if I
> miss something? Thanks!
>
Ubuntu on ARM is softfp, right? How about testing hardfp with a
distribution like ArchLinuxArm?
> Here is the pandaboard configuration,
>
> ---
> $ uname -a
> Linux arm2 2.6.38-1208-omap4 #11-Ubuntu SMP PREEMPT Fri Apr 15 16:34:35
> UTC 2011 armv7l armv7l armv7l GNU/Linux
> $ gcc -v
> gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
> $ ld -v
> GNU ld (GNU Bi...
2012 Apr 15
0
[LLVMdev] About LLVM 3.1 ARM testing
On Sun, Apr 15, 2012 at 2:02 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote:
> > Ubuntu on ARM is softfp, right? How about testing hardfp with a
> > distribution like ArchLinuxArm?
>
> Yes, Ubuntu on ARM is softfp. But I already told Bill the platform I
> prepare
> to test and the testing day begins *tomorrow*, I prefer what it likes now.
> BTW,
> what if I use a cross compiler with hardfp enabled to compile LLVM first,
> then
> run it on Ubuntu/ARM...
2015 Jun 12
3
libusb_get_string: invalid argument (other usbhid-ups users, please test)
thanks - this has been fun.
There is one other thing I have been having trouble with - and i've tried it on
two archlinuxarm installs and gotten the same thing. i am not even sure if its
important for me. but if i try to configure and make with neon support - it cant
find the neon libraries. despite neon having been installed several
different ways (i tried pacman, as well as compiling and installign neon from
source...
2012 Apr 14
2
[LLVMdev] About LLVM 3.1 ARM testing
Hi all,
Since the 3.1 testing day is coming and be a ARM tester, I would like to make
sure everything is O.K. so that we don't waste the precious time. As discussed
on the ML before, I plan to cross compile LLVM/Clang first, then run regression
test and test suite on the pandaboards. Could someone help me check to see if I
miss something? Thanks!
Here is the pandaboard configuration,
2015 Jun 13
0
neon (was libusb_get_string: invalid argument (other usbhid-ups users, please test))
On Jun 12, 2015, at 10:33 AM, Greg Hersch <hersch.greg at gmail.com> wrote:
> thanks - this has been fun.
>
> There is one other thing I have been having trouble with - and i've tried it on two archlinuxarm installs and gotten the same thing. i am not even sure if its important for me. but if i try to configure and make with neon support - it cant find the neon libraries. despite neon having been installed several different ways (i tried pacman, as well as compiling and installign neon from source)
&g...
2019 Mar 02
1
[Bug 109812] New: tegra124: Display manager (sddm) not showing up after upgrade to mesa 18.3.3 DATA_ERROR INVALID OPERATION
...nouveau at lists.freedesktop.org
Reporter: tristan-c.bastian at gmx.de
QA Contact: nouveau at lists.freedesktop.org
Created attachment 143512
--> https://bugs.freedesktop.org/attachment.cgi?id=143512&action=edit
Output of dmesg
Since I upgraded mesa to version 18.3.3 on ArchlinuxARM I'm only getting a
black screen on bootup with my cursor on it..
I'm running kernel 4.20.4
I'm able to move my cursor and also see a different cursor if I move over the
place where the password input field would normally be.
If I downgrade mesa to version 18.3.2 I'm not seeing this...
2015 Jun 11
2
libusb_get_string: invalid argument
Greg,
I'm still not 100% on what is going on, but after comparing the call stack with a debug session here, I think I have at least identified why I wasn't seeing similar behavior.
There are two ways that the driver can get information from the UPS: asking the UPS for a specific report (which returns one or more values), and checking the interrupt pipe (which the UPS can fill with