public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ARM 64?
Date: Wed, 23 May 2018 10:58:00 +0100	[thread overview]
Message-ID: <4999de627aac305daac64b4e956a332e6d2edbc7.camel@ipfire.org> (raw)
In-Reply-To: <f74608c8-5007-3846-7f1b-2c0c9d421d57@traverse.com.au>

[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]

Hello Guy,

thank you very much for getting in touch.

Yes, we are working on an ARM 64 port, but so far we have not seen any hardware
that was worth doing the port for. All those small and cheap single-board
computers lack power, the bigger systems are basically unavailable and way too
expensive.

This board is way different though. CPU, Memory and especially the NICs are
something that are way better sized and make a nice small appliance for bigger
SOHOs or small to medium-sized offices.

Not entirely sure why there is only one 10G port. Usually where 10G goes in, it
has to go out somewhere else again...

The big question is what software support is like in the Linux kernel for this.
I have seen the patches linked on the product page and can only defer to Arne to
have a look at it.

My question would now be: What is the desired RRP for this or wholesale? I am
just curious to find out if it is competitive or if people would find it too
expensive and buy Intel again. Then we shouldn't really bother with putting the
time into a port. If you are not comfortable sharing prices on the list, please
feel free to email me in private about this.

About the sponsorship. Thank you very much for considering us. I would be happy
to have a closer look. Would you be able to ship this into the UK or Germany?

Best,
-Michael

On Wed, 2018-05-23 at 12:46 +1000, Guy Ellis wrote:
> Dear list,
> 
> Just wondering if there is any interest in supporting ARM 64 hardware 
> moving forward?
> 
> We can assist with donated hardware and support if there is interest.
> https://traverse.com.au/products/ls1043s-router-board/
> 
> Regards,
>   - Guy.
> 
> 

  reply	other threads:[~2018-05-23  9:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  2:46 Guy Ellis
2018-05-23  9:58 ` Michael Tremer [this message]
     [not found] <c51182f4-9958-4b76-83e0-9a8affa81038@traverse.com.au>
2018-05-24  1:32 ` Mathew McBride
2018-05-24 10:31   ` Michael Tremer
2018-05-24 11:02     ` Mathew McBride
2018-05-24 14:44       ` Michael Tremer
2018-05-25  2:45         ` Mathew McBride
2018-05-25 13:10           ` Michael Tremer
2018-05-28 10:32             ` Mathew McBride
2018-05-28 11:15               ` Michael Tremer
2018-06-14 17:08                 ` Peter Müller
2018-06-17 23:40                   ` Mathew McBride
2018-06-18 11:23                     ` Michael Tremer
2018-06-18 16:11                       ` Peter Müller
2018-07-26  9:50                         ` Michael Tremer
2018-08-04 18:31                           ` Peter Müller
2018-08-19  8:54                           ` Mathew McBride
2018-08-20 15:11                             ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4999de627aac305daac64b4e956a332e6d2edbc7.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox