[Mesa-users] chromebook compatibility
Bill Paxton
paxton at kitp.ucsb.edu
Mon Apr 29 12:46:48 EDT 2019
There may be problems with the exact behavior of the floating point on a different processor. This would show up as a the failure of the crlibm routines to give consistent results. The installation should pick this up and complain if it is in fact an issue. Then you will have to decide if getting it working on the new hardware is sufficient compensation for turning off the bit-for-bit compatibility. Or a brave soul could attempt to modify crlibm to work with the new hardware. Hopefully this won’t be an issue, but you should know about it as a possibility.
-b
> On Apr 29, 2019, at 9:39 AM, amber lauer via Mesa-users <mesa-users at lists.mesastar.org> wrote:
>
> Great point. I'm mostly thinking of the Chromebooks that have the Intel core i3-5-7 processors. Regardless of architecture, I think the rest are too under powered to run MESA. The basic Linux beta subsystem on these new tabs would probably be sufficient and compatible for ssh for those that are running MESA remotely. Though they probably won't have the capability to tunnel X-window. So no pgplot. I know the high end pixel books could be dual booted anyway. Not sure about these new ones.
>
> On Tue, Apr 23, 2019 at 11:51 PM Jon Brase <jon.brase at gmail.com <mailto:jon.brase at gmail.com>> wrote:
> Amber,
>
> I'm not so much an expert on MESA, but from a general computing perspective I have one question for you and one for the rest of the list that should help determine how likely you are to run into trouble.
>
> For you: What Chromebook model are you planning on using?
>
> For everybody else: MESA specifies that it requires a 64-bit processor, but are there any dependencies on x86 specifically? If there are no intentional dependencies, has MESA been tested on anything other than x86? Some Chromebooks (not all) use ARM processors, which may end up being an issue for Amber if MESA is (by design or because of a bug that hasn't been exposed in testing) not portable across architectures.
>
>
> -------- Original message --------
> From: amber lauer via Mesa-users <mesa-users at lists.mesastar.org <mailto:mesa-users at lists.mesastar.org>>
> Date: 4/23/2019 14:24 (GMT-06:00)
> To: MESA List <mesa-users at lists.mesastar.org <mailto:mesa-users at lists.mesastar.org>>
> Subject: [Mesa-users] chromebook compatibility
>
> I know this is a longshot but has anyone tried to get MESA working on the new chromebook beta linux (not clean install)? Most chromebooks are probaly too underpowered to run MESA, but some of the google branded ones are pretty high end.
>
> --
> Amber Lauer
> Postdoctoral Researcher
> Triangle Universities Nuclear Lab
> Duke University
> amber.lauer at tunl.duke.edu <mailto:amber.lauer at duke.edu>
>
> --
> Amber Lauer
> Postdoctoral Researcher
> Triangle Universities Nuclear Lab
> Duke University
> amber.lauer at tunl.duke.edu <mailto:amber.lauer at duke.edu>_______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190429/ac721132/attachment.html>
More information about the Mesa-users
mailing list