lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 248 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 252 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 264 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 264 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 250 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 252 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 264 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 264 seconds]
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <b​albes150> Availability M2 (NVMe\SATA), LAN , USB 3.0 ?
tkaiser has quit [Ping timeout: 260 seconds]
<Armbian-Discord> <T​onymac32> If it's Pi form factor, it can't have it on-board really, unless it uses a ridiculous add-on board or a strange flex cable 😆
<Armbian-Discord> <b​albes150> in addition to 2280, there are other formats (2240, etc.) and they easily fit into this format. And if desired, and a competent layout, you can even squeeze 2280 into this format without any additional boards \ cables ... 🙂
<Armbian-Discord> <T​onymac32> Well, the other formats are not common so don't make a lot of sense here. As for competent layout, well, perhaps it says a lot about the vendors 👀😆. I've never tried to lay out anything that complex, so I won't judge. 🙂
<Armbian-Discord> <T​onymac32> I don't actually know how limited the IO is on the "s" version of the RK3588. 🤔
<Armbian-Discord> <c​ats> Orange Pi 800 is weird. Why did they even bother putting VGA on it? :|
<Armbian-Discord> <T​enkawa> oddly some people still use vga
<Armbian-Discord> <T​enkawa> I still get asked locally for it
<Armbian-Discord> <b​albes150> 2240 are quite common for their direction. this is a logical format for the meager PI form factor.
<Armbian-Discord> <b​albes150> The M2 capabilities on the rk3588s are quite sufficient for standard use cases. The transition (availability) of M2 for NVMe\SATA is an important element for switching to standard equipment (without using eMMC), easy replacement in case of breakdown, large volume recovery for the user's current task, etc.
<Armbian-Discord> <b​albes150> One reason is enough - modernization of existing workplaces (firms\ state institutions\ education, etc.). These are millions (potentially) replacement points, keeping the monitor (VGA) and throwing out the old x86 shit (stuffed with hardware Trojans, which it is not possible to block programmatically on the device itself) + switching to an energy-efficient platform to reduce energy costs by several times from
<Armbian-Discord> 200-300 watts (a regular PC system unit) to 10-15 watts (at peak). You can calculate the savings on electricity payments yourself.
<Armbian-Discord> <T​onymac32> I agree with all the points of why to use NVMe, this is why the T4 is one of my favorite boards. In my opinion though, the Pi form factor is more or less a badly misshapen toy with terrible heat dissipation and (usually) poor power distribution/management. 10 watts or less with limited IO needs, sure.
<Armbian-Discord> <T​onymac32> I just wonder what the target audience of such a Pi shaped board are
<Armbian-Discord> <T​enkawa> the Pi "shape"... works fine... keep in mind to keep cost down they don't use both sides of the board in fabrication for connectors in a way that would optimize heat/power
<Armbian-Discord> <T​enkawa> That's the bigger problem.. cost
<Armbian-Discord> <T​enkawa> the Pi form factor isn't
<Armbian-Discord> <T​enkawa> They are trying to reach a much lower price point and keep it there "fixed" for a longer amount of time
<Armbian-Discord> <T​onymac32> Sigh, I design PCB's, and deal with thermal management (automotive EE). The Pi shape has a stupid connector arrangement and a nearly impossible thermal situation if you go past 10 watts. A powered cooler is wonderful until you try to use the 40-pin connector for anything. Or, SoC on the bottom and high-cost custom cases.
<Armbian-Discord> <T​enkawa> Yes and as I just stated... unless you change the "shape" (which costs more)... Thats not going to change
<Armbian-Discord> <T​onymac32> The 3588, even S, is a bit heavy for a Pi shaped board IMHO
<Armbian-Discord> <T​enkawa> which costs more
<Armbian-Discord> <T​onymac32> It will be the cost driver for this design, even using 32 layers on the PCB I bet 😆
<Armbian-Discord> <T​onymac32> (sarcasm)
<Armbian-Discord> <T​enkawa> RPI are "not" going to add cost.. by Foundation mandate
<Armbian-Discord> <T​onymac32> I wouldn't expect them to. I also wouldn't emulate them
<Armbian-Discord> <T​enkawa> agreed
<Armbian-Discord> <T​enkawa> Not for a business... but they "technnically" never started out catering to businesses
<Armbian-Discord> <T​onymac32> That said, of the "S" is at a good price point and the board can be reasonably cooled, it could be a nice gadget
<Armbian-Discord> <T​enkawa> Anyone carrying the S yet?
<Armbian-Discord> <T​enkawa> I can't even find a pre-order for it
<Armbian-Discord> <T​onymac32> I haven't seen, but I think they were made available at the same time, it should just be a packaging/breakout difference
<Armbian-Discord> <T​onymac32> Lol wrong respond to
<Armbian-Discord> <T​heBug> I heard Superman has one on his chest ... but I don't know if you call that carrying it...
<Armbian-Discord> <T​enkawa> lol
<Armbian-Discord> <T​onymac32> Le sigh
<Armbian-Discord> <T​enkawa> thats good
<Armbian-Discord> <T​enkawa> You sure it wasn't 2 crossed claws
<Armbian-Discord> <T​enkawa> Microsoft
<Armbian-Discord> <T​enkawa> er
<Armbian-Discord> <T​enkawa> Microsoft's new Wolverine box
<Armbian-Discord> <T​onymac32> 3A 5V makes me nervous. It's not enough go juice unless you use powered hubs for USB
<Armbian-Discord> <T​onymac32> Which is one of my pet peeves.
<Armbian-Discord> <T​onymac32> Blue USB port = 900mA or don't bother putting it on there
<Armbian-Discord> <T​onymac32> 😆
<Armbian-Discord> <T​enkawa> @Tonymac32 yeah these are pulling more and more ... and in a day where people are already trying to lower the draw
<Armbian-Discord> <T​heBug> You mean like on EspressoBin where it's blue but doesn't even put out 500mA... and nothing USB 3.0 works without a powered hub...
<Armbian-Discord> <T​heBug> Ask me how I figured that one out... (so many hours wasted)
<Armbian-Discord> <T​onymac32> Ooof
<Armbian-Discord> <b​albes150> rk3588s ?
<Armbian-Discord> <T​enkawa> yeah
<Armbian-Discord> <T​enkawa> oh the firefly thats right
<Armbian-Discord> <T​enkawa> pricy
<Armbian-Discord> <T​enkawa> heheh
<Armbian-Discord> <b​albes150> There will be competition - there will be a decrease 🙂 Now there are practically no competitors on the market - only promises and potential orders. By the way, for me now the optimal model is Station P1 pro (not to be confused with the first version of P1), this one has NVMe and all the elements for use as a ready-made device - you bought it and immediately use it (after installing the right system). 🙂
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <T​enkawa> I still am waiting on my regular 3588 (and now my Starfive Vision 2)
tkaiser has quit [Ping timeout: 260 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 252 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <P​ridetoons> Will there be an Armbian build for the Orange Pi 800?
tkaiser has quit [Ping timeout: 264 seconds]
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <W​erner> Check forums balbes posted first alpha images for testing
<Armbian-Discord> <P​ridetoons> Thank you!
<Armbian-Discord> <K​anken> i haven't really thought about it much since i didn't need to use it before, but now that i need to use the MIPI cameras with my RK3399-based orange pi 4 i would be stuck on opi's not-so-great stock OS image. But if i added camera support myself by patching the kernel and building my own image based on armbian maybe i could get the best of both worlds 🤔
<Armbian-Discord> <K​anken> some of the work has been done for other RK3399 based SBCs so i guess it's quite possible https://github.com/initBasti/NanoPC-T4_armbian_configuration/blob/main/userpatches/kernel/rockchip64-dev/0001-media-i2c-OV13850-image-sensor-support.patch
<Armbian-Discord> <K​anken> i need to research how to do this kind of thing more thoroughly first though, i don't really have any experience patching in some driver support or building armbian, so reading the docs comes first X')
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 260 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 260 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 260 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 252 seconds]
tkaiser has joined #armbian-rockchip