3 ms·

Hehe... the great thing of bringing up a requirement on Hacker News is that one will always find somebody whose instant reaction is “you don’t need that [becaus

by qubex 6y ago

Hehe... the great thing of bringing up a requirement on Hacker News is that one will always find somebody whose instant reaction is “you don’t need that [because I don’t need it]”. For various reasons it’s something I want. Do I need it? No, I don’t... but then again none of us really need anything beyond oxygen, hydration, and caloric sludge. Let’s put it this way: given my predicament (locked down in a building that only has WiFi) a wireless solution is pretty much required. As for the PCIe... the 8x slot clearly is required for a graphics card. I have several other peripherals (an SDR and an FPGA card) that would be homeless.

StillBored 6y ago
This! times 100. It seems common that these ARM boards vendors are like "here is your pcie slot" and then fail to provide all the basic peripherals onboard that make mITX work on x86. Or for that matter just provide a couple slots on a mATX board. AKA, if the board is missing something fundamental (like graphics, sata, or even USB!) then the board is useless for a lot of cases which require both the missing bits + some other PCIe board. Its the same thing with soldered on RAM, 4G should be enough for everyone! Its quite silly in many regards too, since adding a few $$ to the BOM for a graphics chip/usb/networking/whatever to bring it up to feature parity with $120 boards from asus/etc never seems to cross their minds.
- Klinky 6y ago
  I would suggest you go make your own board then. Adding DIMM slots is not trivial, and then you have to worry about compatibility with third-party RAM. There is something to be said about a wholly-integrated solution. It's more manageable from the manufacturer's point of view. Flexibility adds complexity and uncontrollable variables, which is not what you want in a product priced at the low end. It's not always the BOM that costs you, instead it's the additional testing, validation & support.
  - StillBored 6y ago
    Flexibility gives you a broader market. Its fine if your building 1 product, but if you want to sell into a market with users that have a dozen different requirements and insufficient volume to justify custom configurations your in trouble. OTOH if you can cover a few hundred different use cases with a single design without a lot of additional complexity then your better off. There isn't any way, that every chip+motherboard+ram combination possible on the x86 market is tested. What you test for is compliance to the spec, and a few really common cases to sanity check everything. Then the OEM/final integrator is on the hook for validating/supporting a design. And it works the majority of the time you can buy RAM, or pcie cards, or whatever and plug them in. That is the point of standards. Plus, on the bleeding edge the standards almost always have fallback modes which are considered easier to get right (lower clocks, well understood previous generation, whatever). So when something isn't fully conformant it still works, just at a degraded speed. The problem is most of the arm vendors can't built compliant parts to save their lives. From nonstandard usb, pci, ram and networking gear. It only tends to work because they hack it together in that one configuration that happens to work because its got a couple capacitors sprinked on the board, or a software quirk that bypasses the broken functionality. Just look at all the stuff wrong with the rpi.
    - Klinky 6y ago
      SBCs already are extremely flexible for their market segment. Their market segment just happens to NOT be "developer workstations". The developer workstation market is heavily dominated by x86 because the ecosystem and performance per $ offered by AMD/Intel/nVidia is due to trillions of dollars in development costs over the past decades. ARM is not directly compatible with that ecosystem, so has to re-invent a lot of wheels, and the capital is not there to go head-to-head in commodity PC market when you have a compatibility disadvantage, and your high-end performance is not comparable. Adding an actual system OEM/integrator means another person needs convincing there is a market and adds additional markup. The struggle to put together functional boards is just indicative of the complexity of the problem. Even some x86 boards are garbage.
      - StillBored 6y ago
        Except that "Developer workstation" is really "generic product that conforms to multiple targets". Drop a quad port NIC into one of them and you have a router, put a RAID controller in and you have a NAS. Attach a high speed A/D and you have an industrial controller, etc. None of those options really work for the majority of the arm SBC market which are repurposed phone SOCs. Yes, they are flexible as long as a large part of the target is touchscreen + wifi and attaching a USB SDR. Or they get misused as massively overspeced micro controllers that happen to need a network connection (aka IoT). So its really that latter case where they are successful because they are "generic" microcontrollers. Many of the uses cases would be far better/cheaper handled with a cortex-M and a custom board. But using a $35 rpi to read a GPIO and send a packet is the "generic" solution for someone not willing to spend $500k on a custom design to create 1k devices at $2 each.
guenthert 6y ago
One wireless solution is an AP with ethernet bridge, no?
eqvinox 6y ago
> “you don’t need that [because I don’t need it]” You got that response because your post sounded like the LX2K only has the M.2 slot and no other PCIe at all, when it in fact has a regular ×8 PCIe slot. > the 8x slot clearly is required for a graphics card. The HoneyComb LX2K is not a desktop or mITX replacement. It's a network/routing platform, as shown by the onboard 100GE QSFP28 port. The ×8 slot is clearly required for more networking :P > I have several other peripherals (an SDR and an FPGA card) that would be homeless. ... where are you putting those on an x86 Mini-ITX board with one PCIe slot?

by qubex 6y ago

StillBored 6y ago

This! times 100. It seems common that these ARM boards vendors are like "here is your pcie slot" and then fail to provide all the basic peripherals onboard that make mITX work on x86. Or for that matter just provide a couple slots on a mATX board. AKA, if the board is missing something fundamental (like graphics, sata, or even USB!) then the board is useless for a lot of cases which require both the missing bits + some other PCIe board. Its the same thing with soldered on RAM, 4G should be enough for everyone! Its quite silly in many regards too, since adding a few $$ to the BOM for a graphics chip/usb/networking/whatever to bring it up to feature parity with $120 boards from asus/etc never seems to cross their minds.

Klinky 6y ago
I would suggest you go make your own board then. Adding DIMM slots is not trivial, and then you have to worry about compatibility with third-party RAM. There is something to be said about a wholly-integrated solution. It's more manageable from the manufacturer's point of view. Flexibility adds complexity and uncontrollable variables, which is not what you want in a product priced at the low end. It's not always the BOM that costs you, instead it's the additional testing, validation & support.
- StillBored 6y ago
  Flexibility gives you a broader market. Its fine if your building 1 product, but if you want to sell into a market with users that have a dozen different requirements and insufficient volume to justify custom configurations your in trouble. OTOH if you can cover a few hundred different use cases with a single design without a lot of additional complexity then your better off. There isn't any way, that every chip+motherboard+ram combination possible on the x86 market is tested. What you test for is compliance to the spec, and a few really common cases to sanity check everything. Then the OEM/final integrator is on the hook for validating/supporting a design. And it works the majority of the time you can buy RAM, or pcie cards, or whatever and plug them in. That is the point of standards. Plus, on the bleeding edge the standards almost always have fallback modes which are considered easier to get right (lower clocks, well understood previous generation, whatever). So when something isn't fully conformant it still works, just at a degraded speed. The problem is most of the arm vendors can't built compliant parts to save their lives. From nonstandard usb, pci, ram and networking gear. It only tends to work because they hack it together in that one configuration that happens to work because its got a couple capacitors sprinked on the board, or a software quirk that bypasses the broken functionality. Just look at all the stuff wrong with the rpi.
  - Klinky 6y ago
    SBCs already are extremely flexible for their market segment. Their market segment just happens to NOT be "developer workstations". The developer workstation market is heavily dominated by x86 because the ecosystem and performance per $ offered by AMD/Intel/nVidia is due to trillions of dollars in development costs over the past decades. ARM is not directly compatible with that ecosystem, so has to re-invent a lot of wheels, and the capital is not there to go head-to-head in commodity PC market when you have a compatibility disadvantage, and your high-end performance is not comparable. Adding an actual system OEM/integrator means another person needs convincing there is a market and adds additional markup. The struggle to put together functional boards is just indicative of the complexity of the problem. Even some x86 boards are garbage.
    - StillBored 6y ago
      Except that "Developer workstation" is really "generic product that conforms to multiple targets". Drop a quad port NIC into one of them and you have a router, put a RAID controller in and you have a NAS. Attach a high speed A/D and you have an industrial controller, etc. None of those options really work for the majority of the arm SBC market which are repurposed phone SOCs. Yes, they are flexible as long as a large part of the target is touchscreen + wifi and attaching a USB SDR. Or they get misused as massively overspeced micro controllers that happen to need a network connection (aka IoT). So its really that latter case where they are successful because they are "generic" microcontrollers. Many of the uses cases would be far better/cheaper handled with a cortex-M and a custom board. But using a $35 rpi to read a GPIO and send a packet is the "generic" solution for someone not willing to spend $500k on a custom design to create 1k devices at $2 each.

guenthert 6y ago

One wireless solution is an AP with ethernet bridge, no?

eqvinox 6y ago

> “you don’t need that [because I don’t need it]” You got that response because your post sounded like the LX2K only has the M.2 slot and no other PCIe at all, when it in fact has a regular ×8 PCIe slot. > the 8x slot clearly is required for a graphics card. The HoneyComb LX2K is not a desktop or mITX replacement. It's a network/routing platform, as shown by the onboard 100GE QSFP28 port. The ×8 slot is clearly required for more networking :P > I have several other peripherals (an SDR and an FPGA card) that would be homeless. ... where are you putting those on an x86 Mini-ITX board with one PCIe slot?