Linaro container hub
Hi, Anyone knows the process of getting containers into https://hub.docker.com/u/linaro -- cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: OpenGL vs OpenGlES on arm64
On Mon, 26 Nov 2018 at 14:46, Steve McIntyre wrote: > Is it true that most PCIe graphics cards (and drivers) will also > support GLES as well as GL? I've seen that asserted. Supporting GLES doesn't mean applications will use GLES. Desktop applications use GL/DX (via Wine)/Vulkan. I'm no expert in GL/GLES, but I think they're quite different standards. I can attest quite strongly that the DX-to-GL bridge done by Wine, while commendable, is not how we want to present ourselves in desktop environments. Vulkan is being pushed hard by some studios because it happens to consistently outperform DX on Windows and it's much easier to work with (sane standard). Valve is pushing Vulkan even harder, so that it can work on Linux, too. Any GL-to-GLES (or vice-versa) work will be thrown away. Moving ARMv8 towards GLES is a huge mistake, IMHO, and one which history will not be too kind to. I can almost hear Linus saying something about video quality on Arm. -- cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Austin colo offline?
On 17 September 2016 at 19:16, Andy Doan wrote: > The collocation facility hosting our servers suffered a major HVAC > failure. To compound matters, their monitoring network failed to notice > and temperatures got pretty hot for about 3 rows of racks (of which we > were one). Ouch! Mr. Robot strikes again? > At this point, I think everything is back online but please let me know > if something isn't working properly. From what I can tell our servers > never got too hot or crashed (uptime seems to confirm this). It seems > like an upstream switch may have overheated and shut down. All good on our side, thanks! --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: GSOC results example
Hi Mark, We did, not enough and just a bit too late. ;) A few people started the trend (including me), but we didn't have enough organization to propose a good number of interesting projects in time. Most of the comments was about the quality of the work and the time spent on mentoring being too much. This year, I followed the work of some students on the LLVMLinux group and the mentoring time spent was very little. The results of other LLVM projects (ex. Flang) speak for themselves. I wanted to reiterate that the benefits of the GSOC almost always outweigh the costs, even if the project is not successful, but most are. It's good to have corporate backing (ie. you ;), and I think we should start planning for the next year much sooner (maybe even during the US Connect) and have some incentive plan to foster mentors inside Linaro. It's a great way to involve the community in working with Linaro towards the common goal, and to recruit candidates in subsequent years with proven track with Open Source *and* Linaro. cheers, --renato On 23 September 2013 13:57, Mark Orvek wrote: > Renato, > > We did apply to GSOC this year but our proposal was not selected. I > agree, we should apply again next year. > > Mark > > > On Mon, Sep 23, 2013 at 5:38 AM, Renato Golin wrote: > >> One example of the kind of results that come from a GSOC project: >> >> http://flang-gsoc.blogspot.ie/2013/09/end-of-gsoc-report.html >> >> Might be worth thinking about it next year? >> >> cheers, >> --renato >> >> ___ >> linaro-dev mailing list >> linaro-dev@lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-dev >> >> > > > -- > Mark Orvek > > mark.or...@linaro.org > > EVP, Engineering > > *M*: +1.408.313.6988 *IRC:* morvek *Skype:* morvek > linaro.org │ Open source software for ARM SoCs > > > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
GSOC results example
One example of the kind of results that come from a GSOC project: http://flang-gsoc.blogspot.ie/2013/09/end-of-gsoc-report.html Might be worth thinking about it next year? cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: dev boards
On 8 May 2013 18:21, Jonathan Aquilina wrote: > I have a quick question can the development boards be used in production > environments? > Depends on what you consider "production" environment. I have a couple of "production" buildbots using Pandas which is public and a crucial part of continuous integration for LLVM, though I'd never use a Panda to drive robots on a factory floor. ;) cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Question relating to arm
On 15 April 2013 15:36, Jonathan Aquilina wrote: > My goal is to provide affordable point of sales systems. I was also > considering some of the linaro dev boards that are available. > Hi Jonathan, It seems you won't be using fancy 3D graphics, so the video card is near irrelevant, here. You should be able to get accelerated 2D graphics with most SoCs, even if not using open source drivers. Wookie might know some boards that have decent OSS video drivers, but if you don't care (most people don't), you should be fine. There are a number of v7 that you might consider. I would go for anything that is equal or higher than a dual/quad-core A9 (Pandaboard ES, Odroid, Tegra3), but there are also newer dual-core A15 (which is at least 2x faster than dual-A9), on several flavours (Arndale, Chromebook, Odroid, Tegra4). You might also try the very cheap "AllWinner A10" which is essentially a Beagleboard (dual-core A8). You can find several cheap platforms on the market with that configuration (including tablets running Android) that you might be lucky putting Linux on it. Though, I'd have a look at how your software behaves on a Beagleboard before trying the hard way. Mans suggestion (Beaglebone) is smaller than the Beagleboard, but faster than the Raspbery Pi. It's also extremely cheap and very customizable. The Pi is not a bad choice per se, IMO, but Wookie is right regarding what pre-compiled systems are in offer, you just won't get the best experience unless you opt for specialized Linux distros (Raspbian?). Given that they're really (really) cheap, it might be worth a try. Hope that helps, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Quantal developer rootfs issue
Oh, one more thing, and that's not specific to this image, but to many Linaro images I tried. The ports.ubuntu.com/ubuntu-ports Apt source is on both sources.list and sources.list.d, yielding an error of duplicated entries. I just removed the sources.list (since it was the only entry) and all went well. cheers, --renato On 29 March 2013 14:14, Fathi Boudra wrote: > Hi Renato, > > On 29 March 2013 15:28, Renato Golin wrote: > > > > Hi folks, > > > > I installed the panda-quantal_developer_20130128-58.img.gz on an old > Pandaboard A1 and apt-get update got a new kernel and have overwritten the > preEnv.txt boot=UUID=...hash... into boot=UUID=rootfs, only that rootfs is > not a device. > > > > It fell back to busybox saying couldn't find root, so I re-wrote the > file to have the correct UUID and it booted correctly. > > > > Not sure anyone has seen this, but seems like a simple bug to fix... > > I haven't seen that before but it should be easy to reproduce. > > btw, we don't ship images with preEnv.txt but boot.txt/scr instead. > When the kernel is updated, flash-kernel is called and should update the > UUID. > The rootfs is mounted by default using UUID but you can mount by > label: root=LABEL=rootfs > > It seems something wrong is happening with flash-kernel... > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Quantal developer rootfs issue
Hi folks, I installed the panda-quantal_developer_20130128-58.img.gz on an old Pandaboard A1 and apt-get update got a new kernel and have overwritten the preEnv.txt boot=UUID=...hash... into boot=UUID=rootfs, only that rootfs is not a device. It fell back to busybox saying couldn't find root, so I re-wrote the file to have the correct UUID and it booted correctly. Not sure anyone has seen this, but seems like a simple bug to fix... cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: kernel NULL pointer dereference
On 28 January 2013 14:17, Andy Green wrote: > No, "blowing chunks" (slang for vomiting) is different than "blowing > up"... the 4460 has a separate comparator that is able to reset the SoC if > it gets really too hot. > Ah, another term for my collection of disgusting things to talk about during lunch. ;) It will crash colourfully before then is what I mean, unless one of these > thermal mechanisms is helping. It varies by chip actually, some can idle > at 1.2GHz for a long time before choking others crash in a few seconds. > Not sure it adds anything, but I had a Panda here at home (room temperature between 18 and 21 Celsius) running Ubuntu 12.04 desktop version referred from the Panda wiki (with GUI and everything) for 6 days building LLVM 24/7 without a single glitch. The moment I put on the LAVA rack, it failed before the end of the first build. I then remove all GUI packages, useless services, kernel modules (left only the LED driver) and it went back to almost-normal. It failed only once since then. The failure is simple: it freezes. I haven't seen anything on the screen (it blacks out), or over serial and the machine stops responding to ping. Dead. But on. And hot. It looks as though it hit an area outside the system and is running the same NOPs over and over. Some say there was an Indian cemetery in that land before The Quorum was built, it could be a curse, ghosts or even leprechauns. Scratch that, there isn't a single pub nearby, probably ghosts, then. cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: kernel NULL pointer dereference
On 28 January 2013 12:43, Andy Green wrote: > Without this or something doing a similar deal, a Panda ES will blow > chunks after a short period at 1.2GHz. Hi Andy, I agree kernel panic is better than blowing up the board, but that might indicate the scaling is not working very well. Also, does that mean I should not use the 12.02 image because the risk of blowing up my board? cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: kernel NULL pointer dereference
On 27 January 2013 23:30, Michael Hudson-Doyle wrote: > In the past hasn't this sort of problem usually turned out to be heat > related? Or is this something else? > Hi Michael, It could very well be, I don't know how the heating problem used to manifest before... However, the original kernel I was using (12.02) had no problem whatsoever, and I ran it many many times on the same set of boards, without an issue. "rootfs": " http://releases.linaro.org/12.02/ubuntu/oneiric-images/nano/linaro-o-nano-tar-20120221-0.tar.gz ", "hwpack": " http://releases.linaro.org/12.02/ubuntu/oneiric-images/nano/hwpack_linaro-lt-panda_20120221-1_armel_supported.tar.gz " Maybe it's the conjunction of heating up + some change with newer kernels... I'll keep downgrading until it starts working again and will let you know. cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: kernel NULL pointer dereference
Another kernel error: "Unable to handle kernel paging request at virtual address 2e32" https://validation.linaro.org/lava-server/scheduler/job/46082/log_file With: "rootfs": " http://releases.linaro.org/12.11/ubuntu/precise-images/nano/linaro-precise-nano-20121124-538.tar.gz ", "hwpack": " http://releases.linaro.org/12.11/ubuntu/precise-hwpacks/hwpack_linaro-lt-panda_20121125-552_armhf_supported.tar.gz " cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
kernel NULL pointer dereference
Hi folks, I'm testing different kernels with the LLVM LAVA job and the latest one segfaulted. If you search for the phrase on the subject on the URL below: https://validation.linaro.org/lava-server/scheduler/job/46067/log_file You'll see the stack trace and memory dump. These are the tar balls I used: "rootfs": " http://releases.linaro.org/12.12/ubuntu/quantal-images/nano/linaro-quantal-nano-20121217-210.tar.gz ", "hwpack": " http://releases.linaro.org/12.12/ubuntu/quantal-hwpacks/hwpack_linaro-panda_20121217-20_armhf_supported.tar.gz " Is this the right place to report this kind of stuff? cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Cheap Quad-A9 board
Anyone seen this? http://www.hardkernel.com/renewal_2011/products/prdt_info.php It's cheaper than a Pandaboard with a quad-core and 2GB or RAM and ridiculously small. That would probably get my LLVM builds under 1h... But it seems too good to be true, does any one have experience with it? cheers, --renato ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
